Hi Team,

One of our production server rebooted after patch installed.

I have create the Software update - Suppress reboot deployment for bunch of servers. All the patches are successfully installed in the maintenance windows and rebooted. 

Event Log :

The process C:\Windows\CCM\CcmExec.exe (XXXXX) has initiated the restart of computer XXXXX on behalf of user NT AUTHORITY\SYSTEM for the following reason: No title for this reason could be found
Reason Code: 0x80020001
Shutdown Type: restart

I have verified the windows update setting in control panel - The Automatic windows update is enable.

But my server have no internet. How WUA is initiate the reboot, How to I find in log file (Which Log file)
I have paste my reboot coordinate log file for your reference.

Kindly suggest me and how to over come this issue. 

Entered ScheduleRebootImpl - requested from 'UpdatesDeploymentAgent'. set Rebootby = 1426844181. set NotifyUI = True. set PreferredRebootWindowType = 4 RebootCoordinator 3/20/2015 10:36:21 AM 7076 (0x1BA4)
Scheduled reboot from agent UpdatesDeploymentAgent. Deadline local time: 03/20/2015 10:36:21 AM, PreferredRebootWindowType = 4 RebootCoordinator 3/20/2015 10:36:21 AM 7076 (0x1BA4)
No CCM Identification blob RebootCoordinator 3/20/2015 10:36:21 AM 7076 (0x1BA4)
Not in Maintenance/Service Mode, check ServiceWindowsManager next RebootCoordinator 3/20/2015 10:36:21 AM 7076 (0x1BA4)
ServiceWindowsManager has not allowed us to Reboot RebootCoordinator 3/20/2015 10:36:21 AM 7076 (0x1BA4)
MTC task does not exist. Creating new request. RebootCoordinator 3/20/2015 10:36:21 AM 7076 (0x1BA4)
MTC allowed us to reboot RebootCoordinator 3/20/2015 10:36:21 AM 7076 (0x1BA4)
Raising client SDK event for class NULL, instance NULL, actionType 4l, value 1426844181 900 600, user NULL, session 4294967295l, level 0l, verbosity 30l RebootCoordinator 3/20/2015 10:36:21 AM 7076 (0x1BA4)
Notified UI grace period start with 900 grace seconds and 600 final seconds. RebootCoordinator 3/20/2015 10:36:21 AM 7076 (0x1BA4)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SoftDistRebootPerformedOutsideOfSWEvent
{
ClientID = "GUID:3CF0065C-A5B2-4BFF-B6DE-4B3964DD331B";
DateTime = "20150320093621.863000+000";
MachineName = "PMICHSAPEE47";
ProcessID = 1148;
SiteCode = "A02";
ThreadID = 7076;
};
RebootCoordinator 3/20/2015 10:36:21 AM 7076 (0x1BA4)
Succesfully raised SoftDistRebootPerformedOutsideOfSWEvent event RebootCoordinator 3/20/2015 10:36:21 AM 7076 (0x1BA4)
MTC task for reboot 'aade6ead-c51d-48e5-aaa0-2a2f72cbb9c2'. Checking if it can run now... RebootCoordinator 3/20/2015 10:41:21 AM 3840 (0x0F00)
MTC allowed us to reboot RebootCoordinator 3/20/2015 10:41:21 AM 3840 (0x0F00)
Failed to open namespace 'root\CIMv2\Security\MicrosoftVolumeEncryption' (0x8004100E) RebootCoordinator 3/20/2015 10:41:21 AM 3840 (0x0F00)
Bitlocker is not enabled or PIN protector is not enabled. No need to suspend. RebootCoordinator 3/20/2015 10:41:21 AM 3840 (0x0F00)
System reboot request succeeded. RebootCoordinator 3/20/2015 10:41:21 AM 3840 (0x0F00)
Reboot initiated RebootCoordinator 3/20/2015 10:41:21 AM 3840 (0x0F00)
User logoff notification received RebootCoordinator 3/20/2015 10:51:22 AM 6548 (0x1994)
Retry resuming bit-locker TPM PIN protector. Retry count 1 RebootCoordinator 3/20/2015 10:54:54 AM 4860 (0x12FC)
Didn't suspended bit-locker. Do nothing and return. RebootCoordinator 3/20/2015 10:54:54 AM 4860 (0x12FC)

Hi,

WU agent could be the culprit to initiate a reboot, Jason's blog explained this:

http://blog.configmgrftw.com/software-updates-management-and-group-policy-for-configmgr-cont/

WU agent could be the culprit to initiate a reboot .

Most likely not, because the eventlog says: "The process C:\Windows\CCM\CcmExec.exe (XXXXX) has initiated the restart of computer XXXXX on behalf of user NT AUTHORITY\SYSTEM"