
If you’re looking for a complete SCCM installation guide, see our which covers it all. It’s now time to upgrade your environment! This post is a complete step-by-step SCCM 1706 upgrade guide. Gwmi -Namespace root/ccm/policy/machine/actualconfig -Class ccm_softwaredistribution | out-file readme.txt | notepad.exe readme.Consulting Services Need help to upgrade or migrate your site? Consult our to see our rates! * if you’d like to output to notepad for easier reading: Gwmi -Namespace root/ccm/policy/machine/actualconfig -Class ccm_softwaredistribution #1 – Return Published Applications – Note the ADV ID’s of apps having problems Make sure you also review Notes at the bottom. Do the following to resolve the issue and prevent it from happening again. The Root/ccm/clientsdk:ccm_program class has not completely updated, resulting in your application falling into limbo. This happens because the machine rebooted before the SCCM agent can finish updating all the WMI classes (or something has happened to WMI or the content), but after the actual advertisement is completed. When running published applications from the Software Center, you may notice the apps get stuck at Downloading or Installing (return code 0x80091007 (-2146889721).

In my lab setup I noticed SCCM update stuck in downloading state. Observation – If the SCCM update shows downloading, is it actually downloading the update? On the site server if you go to Program Files Microsoft Configuration Manager EasySetupPayload, you should see what actually is downloaded.

1 – Configuration Manager 2 – File Rename 3 – Configuration Manager, File Rename 4 – Windows Update 5 – Configuration Manager, Windows Update 6 – File Rename, Windows Update 7 – Configuration Manager, File Rename, Windows Update 8 – Add or Remove Feature. Following are the list of applicable states you get with client pending reboot. Recent updates to this article: Date Update JRebranded for McAfee Enterprise. McAfee Drive Encryption (DE) 7.2.x For details of DE supported environments, see KB-79422.
