You should install the latest version. Without specific activation credentials for full Mobility management you will have the same options as the plain old free tool of SP2.
1 of 1 people found this helpful
(if for some reason you don't go Franks suggested route... I think I might actually try that)
I still use LDMobility 1.1 go gather mobile inventory from exchange. That is all I want/need it for so it doesn't make sense for us to pay $$$ for a solution that we aren't going to use any of the features.
Basically I just have another core server just for the mobility data, which I then import into ALM. I can't remember if SP3 breaks mobility, or if it's a post SP3 patch. The bottom line is, you can't apply the latest LD patches from LANDesk or mobility WILL BREAK. If you are only using it for gathering device info (like I am), and not using it for any other functionality (like wipe), then just build s dedicated core for it and leave it unpatched.
I was able to setup a test SP2 core with Mobility v1.1 and successfully patched it to LDMS v9 SP3 and to LDMO 9.0.3.
I did run into the problem described in http://community.landesk.com/support/docs/DOC-26628 and the suggested fix didn't seem to work.
However, it ended up not mattering for us because when we pulled the mobile inventory from exchange, we found that it lacked some of the important attributes that we were already getting with our powershell scripts (i.e. UserAgent, etc).
FWIW, if this had fit our needs better, I had planned to do something similar to what Tracy suggested and setup a separate core just for mobility.
Regardless, i appreciate the quick responses!