Changing ClientIdentifier doesn't update the manfest via MCX

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Set the ClientIdentifier via MCX.
2. Login to a test machine and launch MSC, the manifest of software appears.
3. Log out of the test machine.
4. Change the ClientIdentifier.
5. Log back into the test machine, check in System Profiler (Information) to 
make sure the change has applied.
6. Launch MSC, the old manifest of software is still listed.

What is the expected output? What do you see instead?

- Opening MSC will show the software in the updated ClientIdentifier manifest.

What version of the Munki tools/InstallOSpkg tools are you using? On what 
version of OS X?

- MunkiTools 2.0.0.2118
- Mac OS 10.8.5

Original issue reported on code.google.com by stuartin...@gmail.com on 7 Aug 2014 at 9:15

[GoogleCodeExporter]

Appears when launching MSC it doesn't do an update/check to see if the 
ClientIdentifier has changed?

The Software tab shows the old software manifest, but if you click on the 
Update tab it then loads in the change and the Software tab then reflects this.

Original comment by stuartin...@gmail.com on 7 Aug 2014 at 9:50

[GoogleCodeExporter]

MSC.app won't show updated contact until after an update check is preformed, so 
this is merely a timing issue. Changing Munki's preferences does not trigger an 
update check. You can change the ClientIdentifier, then wait until a background 
check happens (or trigger one): if you then launch MSC.app, you'd see the 
expected content.
Or, when MSC.app is launched, if it's been more than ten minutes since the last 
check, MSC.app itself triggers a new check, which may take a few seconds or a 
few minutes to complete.

The unattractive alternative would be to trigger a check on every launch and 
suppress the view of available software until it was complete. This would lead 
to MSC.app being tedious to use, since in most cases after opening it, you'd 
have to wait a long time to do anything interesting with it.

Since it sounds like it is functioning as designed, I'm going to close this; if 
you have more information, we can revisit this if needed.

Original comment by gregnea...@mac.com on 7 Aug 2014 at 1:08

• Changed state: Invalid