SOLVED Patch Deployment Reboot Not Taking Place with Some Computers

[TJChan]

Hello!

I have 4 computers in a 26 computer collection (all running various flavors of Windows Server OS) that are not rebooting after patching. For the deployment options I have checked to allow for the computers to reboot even outside of a maintenance window (1 to 4 am).

From the WUAHandler.log I see that the patch goes through, but it will just sit at "pending reboot" on the deployment dashboard.

Logging onto the box, I see yellow text that says Windows updates have been installed and a reboot is needed and that the reboot would happen in 1 day (paraphrased).

Any idea on why this is happening? My desired outcome is simply patch and reboot during the maintenance window. The other 22 computers have reacted in the desired way. It is probably not the OS as Windows 2012 R2 is on both systems that complete the reboot and those that do not.

My SCCM configuration is as follows:

1810
Primary Site Server with 2 DPs...one on it's own and the other on the Primary site server.

Thank you for your help.
-Timothy

 

[TJChan]

Also noted that in RebootCoordinator I am getting:

Reboot Coordinator received a SERVICEWINDOWEVENT START Event    RebootCoordinator    2/18/2020 1:00:00 AM    2116 (0x0844)
Entered ScheduleRebootImpl - requested from 'UpdatesDeploymentAgent'. set Rebootby = 1582010335. set NotifyUI = True. set PreferredRebootWindowType = 4    RebootCoordinator    2/18/2020 1:18:55 AM    4744 (0x1288)
Scheduled reboot from agent UpdatesDeploymentAgent. Deadline local time: 02/18/2020 01:18:55 AM, PreferredRebootWindowType = 4    RebootCoordinator    2/18/2020 1:18:55 AM    4744 (0x1288)
No CCM Identification blob    RebootCoordinator    2/18/2020 1:18:55 AM    4744 (0x1288)
Not in Maintenance/Service Mode, check ServiceWindowsManager next    RebootCoordinator    2/18/2020 1:18:55 AM    4744 (0x1288)

 

[TJChan]

I think I found my culprit under client settings restart...profile enabled for that computer was set for 480 minutes...or equivalent of 8 hours which matches the reboot coordinator log.

So now, I'm thinking, is it because a user is logged on that's why it does that? If a user is not logged on, then the restart should occur? Looking further in the logs, I see [email protected] and [email protected] with timestamps for today. Would that mean that those users are logged in and hence are getting a notification and so it doesn't want to reboot because of an active RD session?

 

[TJChan]

I believed that fixed my problem. I put a custom client profile with the minimum for reboot and today's patches went out fine and without problem.