Sccm 2012 Deployment Waiting For Another Program
Hey Everyone! I have been pulling my hair out over the last couple of days trying to find an answer or fix to this issue, but so far I am not having much luck.
SCCM2012 R2 Software Deployment stuck at “Waiting for Content. Raising client SDK event for class CCM_Program. SCCM 2012 R2 Deployment Questions. Sccm 2012 Deployment Waiting For Another Program To Complete. Sccm 2012 Deployment Waiting For Another Program In Sccm. Software Updates – Waiting for another. Waiting for another. Mgr 2012 R2 configuration manager Configuration Manager 2012 EMS Enterprise Mobility.
Sccm 2012 Deployment Reports
Here's the situation: SCCM 2012 SP1 - Standalone Primary site with 2 remote Distribution Points. One DP is running Server 2008 Standard and the other is running Server 2003. IIS is installed with the default settings.
The issue: I cannot get clients to download content from the 2 remote DPs. The DPs are added to boundary groups in the 'Content Location'. Clients that pull content from the Primary server get their content, fine. The clients that hit either of the two remote DPs sit forever in a status of 'Waiting for Content'.
I can validate the content on the DPs with no issues and I can remove/redistribute the content fine, as well. I also saw the TechNet KB with the new HotFix but that was referencing issues with distributing content between the primary site and a secondary site with a DP. Any help/suggestions are appreciated!
Looking at the compliance reports I see that most of updates are installing ok but some are constantly saying “Waiting for another installation to complete” The updates won’t install and end-users are constantly getting an error saying the another installation process is already running. It’s not another running process causing the problem, so restarting services won’t help. Information is stored in WMI and most likely is caused by an earlier installation that failed. To fix the problem – two solutions The drastic one – Repair WMI. Log on to the client and stop the Windows Management Instrumentation Service – WMI.
Sccm Image Deployment
Rename the Repository folder to RepositoryOLD. The folder is found in%systemroot% system32 WBEM. Restart the Windows Management Instrumentation Service. This will create a new Repository folder and the software update installation will be able to start. Recreating WMI will delete all history information about previous software advertisements and other Configmgr. The solution I prefer.
Remove the affected computer for all software update deployments. Update the machine policy and wait a little while (Coffee time). Add the computer back to the Update deployments. Do you know the underlying cause of this problem? We had many client with this problem on Windows XP pro.
Not seen it yet on Windows 7. On Windows 2008 R2 SP1 we now have the problem on 1/3 of our machines! Some of them are DP so I’m a bit reluctant to delete the WBEM Repository. I have not tried your preferred solution, because we don’t have separate collections for Updates to servers (maybe I should create one). Have Microsoft a more permanent fix for this? Kind regards, Frode Ersland.