I'm dealing with an issue where I've got an application deployed to about 2,986 devices, and currently, 967 of them are showing up as 'In Progress' while 775 are stuck on 'Waiting for maintenance window' after five days. It's puzzling because the devices I've checked all have a six-hour maintenance window. The only error I've found in the ServiceWindowManager.log is about failing to initialize the ServiceWindowSchedule instance from a particular schedule string. I've gone through execmgr.log and maintenanceCoordinator.log without finding any other errors.
I searched online but couldn't find any helpful info regarding this error. I'm starting to suspect this might be a Configuration Manager 2503 issue since we manage five different MECM instances, and this problem seems consistent across all of them. Any recommendations on how to troubleshoot this further?
3 Answers
Sounds frustrating to see so many devices stuck. Have you checked the client's WMI to see if there's a maintenance window conflict? Sometimes that's where the issue lies.
If you're looking to check the client's WMI for maintenance window info, you can use either of these methods:
1. **WMIC:** Run this command in the command prompt:
`wmic /namespace:\rootccm path SMS_ClientCallMethods call GetMaintenanceWindow`
2. **PowerShell:** This command can give you the required info:
`Get-WmiObject -Namespace "rootccm" -Class CCM_MaintenanceWindow`
This should show you the schedule applied to the client and help identify if the maintenance window is recognized properly. Also, ensure that the client's local time zone is aligning with the schedule—mismatches can halt the execution. Check the `ClientIDManagerStartup.log` as well to make sure the client received the maintenance window policy.
I ran your PowerShell command, but I got an error about 'Invalid class CCM_MaintenanceWindow'. I did try running another command on different devices that's supposed to pull service windows, and it gave me results, but they were all blank. I’ve confirmed time zones match and the logs seem fine. I doubt there's a scheduling conflict since I only have a few collections that include maintenance windows.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures