Advertisements don't make it to device after Client upgrade
After installing the client hotfix 977384 on a test client, bringing the version to .2157, advertisements no longer make it to the machine. In advertisement status on console it sits at "sms offer manager successfully processed new advertisement adv. name" and never proceeds any further no matter how many Machine Policy refreshes I do. After fighting with it and going through logs I decided to restart the PC, hoping something would fix itself. That's actually when the version on the client machine changed to .2157 from .2000, however it still read as .2000 in the console. I decided to reinstall the client manually without the hotfix, and the advertisements immediately showed up. Would the fact that the versions were mis-matched have anything to do with this? I know the version would change in the console next time the Heartbeat Discovery ran, but I wouldn't think this had anything to do with it. Hopefully I'm wrong and that's all it would take. I'm afraid to run the upgrade on all my clients and have them no longer receive advertisements! Anyone ever run into this?
July 11th, 2012 3:32pm

Hi, How did you install the hotfix? Any errors in ccmsetup.log? Any errors in the event-log from the installation? If you are installing the update using msiexec you can add logging to see if any errors occur. If you install the hotfix and initiate a "Data discovery cycle" on the client it should send a heartbeat which should change the client version in the sccm console. Regards, Jrgen -- My System Center blog ccmexec.com -- Twitter @ccmexec
Free Windows Admin Tool Kit Click here and download it now
July 11th, 2012 5:11pm

This particular hotfix was installed while testing an automated install of the SCCM console, which requires the hotfix for R3 to be installed I believe. A script installed it using msiexec and I didn't see anything in the log files, but I will pour over them again to check and re-check. I did initiate a data discovery cycle, and oddly it didn't change the version in the console, but I may have jumped the gun when updating the collection membership and refreshing- I did it a few times to double check.
July 11th, 2012 5:58pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics