SOLVED Inconsistent SCCM client reboot behaviour

[cw255]

Hi all, hoping someone can help me. Got some test devices a collection, collection has a MW, client settings deployed allow reboot, reboot not suppressed in ADR. There were two client both waiting for a reboot after patching, client 1 just goes ahead and does it claiming "ServiceWindowsManager has allowed us to Reboot", client 2 waits "ServiceWindowsManager says that we will Reboot in the future"

Client 1 -reboot coordinator
Not in Maintenance/Service Mode, check ServiceWindowsManager next RebootCoordinator 29/11/2022 10:16:26 14252 (0x37AC)
CheckRebootWindow: Service Windows found for type:4 RebootCoordinator 29/11/2022 10:16:26 14252 (0x37AC)
ServiceWindowsManager has allowed us to Reboot RebootCoordinator 29/11/2022 10:16:26 14252 (0x37AC)
MTC task for reboot 'af8fd1f6-8d40-49c5-8708-418f78db8369'. Checking if it can run now... RebootCoordinator 29/11/2022 10:16:26 14252 (0x37AC)
MTC allowed us to reboot RebootCoordinator 29/11/2022 10:16:26 14252 (0x37AC)

Client 1 - servicewindowmanager

OnIsServiceWindowAvailable called with: Runtime:600, Type:4 ServiceWindowManager 29/11/2022 10:16:26 14252 (0x37AC)
No Restricting Service Windows exist. It can therefore run... ServiceWindowManager 29/11/2022 10:16:26 14252 (0x37AC)
CServiceWindowManager::OnPolicyChange- Policy __InstanceCreationEvent notification received ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
New Service Window Policy notification received. ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
CCM::ServiceWindowManager::CServiceWindowHandler::OnPolicyCreated - A policy change has occurred. New policy has been created. ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
Populating instance of ServiceWindow with ID={BED9301F-889F-400F-94DE-38CB713B0C81}, ScheduleString=025CBD0018100008, Type=1 ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
StartTime is 11/29/2022 6:00:00 PM ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
Duration for the Service Window is Total days: 0, hours: 03, mins: 00, secs: 00 ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
Refreshing Service Window with ID={BED9301F-889F-400F-94DE-38CB713B0C81} ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
Service window not currently active and need not be activated ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
Checking Service Windows to find Next Event..... ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
Next Event Time is at 11/29/2022 6:00:00 PM. Service Window with ID:{BED9301F-889F-400F-94DE-38CB713B0C81}. Is the next event the beginning of the window? Yes ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
Inactive Service Windows List has 9 windows ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
Service Window with ID = 7cb56688-692f-4fae-b398-0e3ff4413adb having Starttime=1/1/2038 12:00:00 AM ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
Duration is 0 days, 00 hours, 00 mins, 00 secs ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
Service Window with ID = 49fd80be-ac4b-4877-974d-ecd09958926d having Starttime=11/29/2022 10:00:00 PM ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
Duration is 0 days, 07 hours, 00 mins, 00 secs ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
Service Window with ID = 45dca355-3249-4845-b8aa-72d0e604548e having Starttime=11/30/2022 10:00:00 PM ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
Duration is 0 days, 07 hours, 00 mins, 00 secs ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
Service Window with ID = 87e4759c-2884-45e6-9261-c33ba53f596c having Starttime=12/1/2022 10:00:00 PM ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
Duration is 0 days, 07 hours, 00 mins, 00 secs ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
Service Window with ID = 36da6950-3d1e-4027-be0e-7b16a4daee7e having Starttime=12/2/2022 10:00:00 PM ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
Duration is 0 days, 02 hours, 00 mins, 00 secs ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
Service Window with ID = 028bfbc0-7120-4081-a268-0e664a92ac4a having Starttime=12/3/2022 12:00:00 AM ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
Duration is 1 days, 00 hours, 00 mins, 00 secs ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
Service Window with ID = 90a5f436-364c-48c7-8dc7-c5014abcbea8 having Starttime=12/4/2022 12:00:00 AM ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
Duration is 1 days, 05 hours, 00 mins, 00 secs ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
Service Window with ID = ad27b0ca-8c74-43c7-8200-1f601880bd75 having Starttime=12/5/2022 10:00:00 PM ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
Duration is 0 days, 07 hours, 00 mins, 00 secs ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
Service Window with ID = {BED9301F-889F-400F-94DE-38CB713B0C81} having Starttime=11/29/2022 6:00:00 PM ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
Duration is 0 days, 03 hours, 00 mins, 00 secs ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)
Active Service Windows List has 0 windows ServiceWindowManager 29/11/2022 10:16:26 19040 (0x4A60)


Client 2

Not in Maintenance/Service Mode, check ServiceWindowsManager next RebootCoordinator 29/11/2022 09:58:10 10624 (0x2980)
ServiceWindowsManager has not allowed us to Reboot RebootCoordinator 29/11/2022 09:58:10 10624 (0x2980)
Succesfully raised SoftDistRebootWaitingForServiceWindowEvent event RebootCoordinator 29/11/2022 09:58:10 10624 (0x2980)
CheckRebootWindow: Service Windows found for type:4 RebootCoordinator 29/11/2022 09:58:10 10624 (0x2980)
ServiceWindowsManager says that we will Reboot in the future RebootCoordinator 29/11/2022 09:58:10 10624 (0x2980)
We will eventually reboot. Just waiting for the Service Window to come along. RebootCoordinator 29/11/2022 09:58:10 10624 (0x2980)


The MW's assigned to both clients are identical

Occurs every 1 weeks on Sunday effective 07/11/2022 01:00 duration 180

Occurs every 1 days effective 28/11/2022 18:00 duration 180

I don't understand the difference so I'm reluctant to roll this out to the other 50 machines which are somewhat business critical, is this a bug or what?

 

[MJ-Tech]

Run this batch file with administrator privileges and manually restart the device. observe the results,

net stop bits
net stop wuauserv
net stop cryptSvc
net stop msiserver

rd C:\Windows\SoftwareDistribution /q /s
rd C:\Windows\System32\catroot2 /q /s
Del C:\Windows\System32\GroupPolicy\Machine\Registry.pol /F

net start bits
net start wuauserv
net start cryptSvc
net start msiserver

SC config wuauserv start= auto

SC config bits start= auto

SC config cryptsvc start= auto
SC config trustedinstaller start= auto


Run the Windows update manually and restart the device if the problem still exists.