The logs were reporting that the content was being REMOVED from the DP, not added to, and then, that it was removing the DP from the date sources. On investigating the logs we found something odd. We did this a few times, both the individual DP’s as well as DP groups, each time we re-open the content locations tab on the boot package properties, it showed no DP’s. When we went to re-add them, the distribution status kept informing us that there were no distribution points targeted. We had removed the package from the distribution points, as we didn’t think we would need them….turns out we did. One scenario that was a little interesting was when we were trying to re-distribute the built in boot images to some distribution points. Regsvr32 /s %systemroot%\system32\userenv.dllįor /f %%s in (‘dir /b /s *.dll’) do regsvr32 /s %%sįor /f %%s in (‘dir /b *.mof’) do mofcomp %%sįor /f %%s in (‘dir /b *.mfl’) do mofcomp %%s Regsvr32 /s %systemroot%\system32\scecli.dll
#Microsoft software center client software#
#4 Just re-add the content as a new package, distribute to DPs, test the Software Center.Ĭmd /c sc create - binPath= “cmd /c start c:\windows\system32\bitsadmin.exe /reset /allusers” type= own & net start - & sc delete. #3 Clear local ccmcache using the Control Panel CM Applet. Make sure this folder’s content is the same at other locations: SCCM_Drive:\SCCMContentLib #2 Verify all content is sync’d up between sites (specifically the package you’re having issues with). You must restore the content, and add an exception to the SCCMContentLib folder. And, let me tell you, SCCM hates missing content, especially if it’s only partially missing. I have found SCCM package content in the quarantine area. #2 – Remove Apps that are having issues using their ADV ID’sįoreach($i in gwmi -Namespace root/ccm/policy/machine/actualconfig -Class ccm_softwaredistribution -Filter “ADV_AdvertisementID=’ ABC20183′“)” /NOINTERACTIVEįour other things you can try if you’re still having issues: Gwmi -Namespace root/ccm/policy/machine/actualconfig -Class ccm_softwaredistribution | out-file readme.txt | notepad.exe readme.txt
* 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.
#Microsoft software center client code#
When running published applications from the Software Center, you may notice the apps get stuck at Downloading or Installing (return code 0x80091007 (-2146889721). From time to time, SCCM just isn’t going to cooperate with you.
0 kommentar(er)
