For the procedure to install the Configuration Manager client on a modern Windows 10 device by using Azure Active Directory (Azure AD) identity, see Install and assign Configuration Manager Windows 10 clients using Azure AD for authentication. That procedure is for clients on an intranet or the internet. Removing computers from a collection in System Center Configuration Manager 2007 may cause an unexpected reboot. Some computers may reboot unexpectedly after they are removed from a collection in System Center Configuration Manager 2007 (ConfigMgr 2007) when that collection has a maintenance window. From looking at a sample log we can see.
-->Applies to: Configuration Manager (current branch)
Deploying clients across your site takes time and some installations are not successful the first time. The Configuration Manager console provides a way to keep an eye on client deployments within a collection by reporting client deployment status in real time.
Note
The best and most reliable way to monitor client deployment is with the Configuration Manager console (as described in this article). The Client Status section of the Monitoring workspace in the console provides client deployment status accurately and in real time. You can monitor client deployments with other tools, such as Server Manager in Windows Server or System Center Operations Manager, but you may receive alarms from normal client installation activity. Because of how the client installation program (CCMSetup.exe) runs in various environments, these other tools may generate false alarms and warnings that do not accurately reflect the state of client deployments.
In the Monitoring workspace of the console, you can monitor the following statuses for client deployments taking place within a collection that you specify:
- Compliant
- In progress
- Not compliant
- Failed
- UnknownConfiguration Manager reports on deployments for production clients or pre-production clients. The Configuration Manager console also provides a chart of failed client deployments over a specified period of time to help you determine if actions you to take to troubleshoot deployments are improving the deployment success rate over time.
To monitor client deployments
- In the Configuration Manager console, click Monitoring > Client Status.
- Click Production Client Deployment or Pre-production Client Deployment depending on the version of client you want to monitor.
- Review the charts of client deployment status and client deployment failure.
- If you want to change the scope of the report, click Browse... and choose a different collection.To learn more about pre-production client deployments, see How to test client upgrades in a pre-production collection.NoteThe deployment status on computers hosting site system roles in a pre-production collection may be reported as Not compliant even when the client was successfully deployed. When you promote the client to production, the deployment status is reported correctly.To monitor the status of deployed clients, see How to monitor clientsYou can use Configuration Manager reports to find out more information about the status of clients in your site. For more information about how to run reports, see Reporting.
1. The 1st batch of 130 some updates install without error.
2. Then the 1st reboot reboot occurs, and a 2nd set of 40 or so updates (that were dependent
on the 1st batch of updates) installs.
3. Then the 2nd reboot occurs.
4. Next a 3rd set of approximately 22+ updates, tries to install, but those 22+ updates are not
even able to be installed into the CCM Cache because of what appears to be a “Locked
Up SCCM Client Agent”, that thinks another job is still in progress.
The material that we found in the UpdatesDeployment log that is related to this issue can be seen below.
- Request received – InstallTargetedUpdates. UpdatesDeploymentAgent 7/15/2011 1:55:46
PM, 1012 (0x03F4)
- Install not allow as another job is still in progress. UpdatesDeploymentAgent 7/15/2011
1:55:46 PM, 1012 (0x03F4)
- InstallTargetedUpdates failed, error 80040703. UpdatesDeploymentAgent 7/15/2011
1:55:46 PM, 1012 (0x03F4)
The following hotfix was released on June 28th 2011.
- KB2509007 - Software Update for ConfigMgr 2007 SP2 (KB2509007)
However even after applying it and re-attempting to run the updates, the same problem still occurs.
We even eliminated all the updates, as a test, to just try 5 of the updates from the 3rd set along with their required pre-requisite updates, and we still have the problem.
The SCCM Client Agent appears to be locked up in incorrectly thinking that another job is still in progress.
Any ideas?