Profile Manager Variables

Question

sid1992 Author

Level 1

0 points

Profile Manager Variables

Hello

On our Profile Manager under Device Groups we create a payload for the exchange and that's works. Now we had a old device (iPhone) from User1, then we delete the device full and give the device to User2. The Exchange Payload will push to the device, but on the Exchange-Settings we see the old settings from User1 and not the shortname, emailaddress from the new User2.

Why that, we delete the device and see the settings from User1 and not User2?

That's only a problem when the device change the user.

Is it purhaps wrong in the Profile Manager Database, when yes how can change that or have someone a hint how can solve the problem?

Thank you very much

Greeting

Mac mini, OS X Mountain Lion (10.8.2)

Posted on Jan 23, 2013 6:21 AM

Reply

Answer 1

RichB

Level 4

1,584 points

Jan 23, 2013 6:41 PM in response to sid1992

When a user logs into the "MyDevices" web site and then installs the exchange profile it knows the user to use for those settings. You can change the assigned user in ProfileManager by selecting Users, then search for the user and add the device to their name. I don't think that will change how the previously installed profile behaves though. Delete the old profile and have the new user log in and install it for them.

Reply

Answer 2

Feb 7, 2013 12:18 PM in response to sid1992

I just spent a while debugging this myself. Internally, Profile Manager caches the configuration profiles that it sends out per-device (or something like that). It does not reset the cached profile data when you change device users, so you keep getting the older version of the payload. The only way I've found to address this is to go mucking around in the internals of the Profile Manager web app (it's built with Rails) and delete the cached profiles directly. I'm really uncomfortable going into production with that as a workaround.

Note that I'm just beginning to test this, and I rather strongly recommend providing feedback to Apple rather than hacking the guts of this moderately complex system yourself.

Reply