You can find these options under Install/Repair. I did this again with Client Center for Config Mgr 2012. Given all my troubleshooting above, my last steps to resolve the issue were to delete the CCM WMI repository and repair the client. I am not sure if this is an accurate state as this is from CCM_SoftwareUpdate, not CCM_Program but it definitely tells me the state is incorrect. According to the MSDN article this is ciJobStateWaitServiceWindow. Note that the task sequence that is stuck has an evaluation state of 14. This appears to list all deployments, and I put a filter to only show any that were not in the state 1 or ‘Available’. Get-wmiobject – namespace root \ ccm \ clientsdk – class ccm_program | select packageid, fullname, evaluationstate | where I got in there and browsed around with PowerShell and came up with the following command:
But this gave me enough info to start playing around. I found the class for CCM_Program but the MSDN article doesnt have any info around the evaluation state, only the CCM_SoftwareUpdate article does. Reset WMI repository using Client Center for Configuration Manager 2012Īfter a little more research I started researching the WMI classes on the client for the evaluation state.Uninstalled ConfigMgr client and reinstalled.Deleted the client DDR in the console to remove the deployment.I have not seen it yet with packages or applications but a few times now with deploying task sequences inside the OS.īasically the deployment downloads, installs, and reports back success but when you open up Software Center on the client it still shows ‘Installing’.Īt first, I attempted a handful of fixes to no avail: Today I am posting about an issue that I have started to see crop up with ConfigMgr 2012 SP1 (no CUs).
My first official post with actual content! Thanks to MikePalmer for a quick PowerShell script to add the dependency! Try it out everyone and see if it works for you! Our SEE will be filing a bug to be fixed in a later version. Microsoft has confirmed this is a bug! We have tested on over a dozen machines and setting the dependency of CCMexec on SMSTSMgr has fixed every single one! Basically the CCMExec service has to start before the SMSTSMgr service can. Edit: The issue has actually been resolved for us! Check the TechNet post below.
0 kommentar(er)
