none
Clinte Restart automatic

    Question

  • How do I restart the client after software update on planned maintenance window?
    Wednesday, July 03, 2013 1:08 PM

All replies

  • If the update requires a reboot (and it is not explicitly suppressed) it will occur automatically during the maintenance window.
    Wednesday, July 03, 2013 1:11 PM
  • Yes, but client don't restarted.. My maintenance windows is 30 min, and User experience checked "commit changes at deadline or during a maintenance windows "
    Wednesday, July 03, 2013 1:17 PM
  • It's not gonna restart in a 30 min maintenance window. I'm suprised it installed updates actually. The client does some calculations and determines if the window is long enough. I think it adds 15 min for a reboot. It's called the turnaround time or something like that.


    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    Wednesday, July 03, 2013 1:42 PM
    Moderator
  • Hum, I had read it now. The updates have been installed and are awaiting the restart, I will test with one hour
    Wednesday, July 03, 2013 1:49 PM
  • I would go a MIN of 2 hours. I always do 4 hours. Service packs will not install in a 1 hour MW.

    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    Wednesday, July 03, 2013 2:51 PM
    Moderator
  • Also note that the other setting you mentioned, "commit changes at deadline or during a maintenance windows", as stated in the dialog box, is for Windows *Embedded* systems only and has no effect on other OSes.

    Jason | http://blog.configmgrftw.com

    Wednesday, July 03, 2013 4:46 PM
    Moderator
  • It's not gonna restart in a 30 min maintenance window. I'm suprised it installed updates actually. The client does some calculations and determines if the window is long enough. I think it adds 15 min for a reboot. It's called the turnaround time or something like that.


    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    Based on John's input I did some further research. Just thought I'd share my findings ...

    It's indeed called System Restart Turnaround Time. The value is stored in the site control file:

    This translates back to 10 minutes.

    There is also the reboot countdown to take into account. This can be configured but by default is 5 minutes.

    So 15 minutes for a reboot is indeed correct in the default scenarios.

    To wrap up I also looked for information on default patch and SP installation times. The defaults are

    - Software updates: 20 minutes
    - Service Packs: is 60 minutes.

    Hope this helps!

    Thursday, July 04, 2013 8:44 AM
  • I added one hour in maintenance windows but machines don't restart, in deployment status "Pending system restart"
    Thursday, July 04, 2013 12:32 PM
  • Just to make sure ... you don't have the suppress checkboxes enabled for the deployment ?

    Thursday, July 04, 2013 1:06 PM
  • I didn't check servers checkbox neither workstations.

    Thursday, July 04, 2013 1:27 PM
  • The client status is pending system restart, I created a new maintenance windows and add this client, but it don't restart and  last enforcement message Time is the older maintenance windows.

    RebootCoordinator.log

    Display warning:

    "No CCM Identification blob"

    Friday, July 05, 2013 12:26 PM
  • In Client setting >  Computer Restart >
    "Display a temporary notification to the user that indicates the interval before the user is logged off or the computer restarts" was 90 min, I changed to 20 min. will now work?
    Please someone?
    Friday, July 05, 2013 7:42 PM
  • The client now restarts but wrong time..

    PLZ SOMEONE?

    Wednesday, July 10, 2013 12:51 PM
  • The client now restarts but wrong time..

    PLZ SOMEONE?


    Can you be more specific?

    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    Wednesday, July 10, 2013 2:12 PM
    Moderator
  • Can you be more specific?

    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    I created a maintenance window to install an update the 02:00 to 03:00 am, but the times from as compliance was to 01:00 am.
    Wednesday, July 10, 2013 3:05 PM
  • Hi,

    Does you computer has the same time as your SCCM Server ? The differencing hour can be due to the fact that systems does not have the same clock settings.

    Regards,


    Régis Lainé | My Blog
    Please mark as helpful/answer if this resolved your post

    Thursday, July 11, 2013 6:37 AM
  • but the times from as compliance was to 01:00 am.

    Where did you see that time? Keep in mind that almost every timestamps at the server (= admin console) are displayed in UTC.

    Torsten Meringer | http://www.mssccmfaq.de

    Thursday, July 11, 2013 7:12 AM
  • Customers have the same time of SCCM, was with UTC in maintenance window scheduled desmarquei them, but the machines are restarted even the wrong day, I saw the log of the machine restarted and said that the process CCMEXEC sent the machine restart.

    Sorry, I used GoogleTranslate =)

    RebootCoordinate.log

    Retry resuming bit-locker TPM PIN protector. Retry count 1    RebootCoordinator    7/1/2013 5:49:58 PM    3048 (0x0BE8)
    Didn't suspended bit-locker. Do nothing and return.    RebootCoordinator    7/1/2013 5:49:58 PM    3048 (0x0BE8)
    Retry resuming bit-locker TPM PIN protector. Retry count 1    RebootCoordinator    7/1/2013 5:51:57 PM    5904 (0x1710)
    Didn't suspended bit-locker. Do nothing and return.    RebootCoordinator    7/1/2013 5:51:57 PM    5904 (0x1710)
    Reboot Coordinator received a SERVICEWINDOWEVENT START Event    RebootCoordinator    7/1/2013 10:00:00 PM    4272 (0x10B0)
    Reboot Coordinator received a MaintenanceEvent Enter Event    RebootCoordinator    7/2/2013 3:21:59 AM    2912 (0x0B60)
    Reboot Coordinator received a SERVICEWINDOWEVENT END Event    RebootCoordinator    7/2/2013 3:25:39 AM    5440 (0x1540)
    Reboot Coordinator received a SERVICEWINDOWEVENT START Event    RebootCoordinator    7/2/2013 3:25:39 AM    5008 (0x1390)
    Reboot Coordinator received a SERVICEWINDOWEVENT END Event    RebootCoordinator    7/2/2013 3:27:27 AM    4044 (0x0FCC)
    Reboot Coordinator received a SERVICEWINDOWEVENT START Event    RebootCoordinator    7/2/2013 3:27:27 AM    2912 (0x0B60)
    Reboot Coordinator received a MaintenanceEvent Exit Event    RebootCoordinator    7/2/2013 4:23:42 AM    5412 (0x1524)
    Reboot Coordinator received a SERVICEWINDOWEVENT END Event    RebootCoordinator    7/2/2013 5:00:00 AM    5668 (0x1624)
    User S-1-5-21-4183147349-3640785585-127349212-1115 is getting pending reboot information...    RebootCoordinator    7/2/2013 10:44:33 AM    972 (0x03CC)
    User logoff notification received    RebootCoordinator    7/2/2013 10:49:58 AM    1356 (0x054C)
    Retry resuming bit-locker TPM PIN protector. Retry count 1    RebootCoordinator    7/2/2013 5:13:00 PM    300 (0x012C)
    Didn't suspended bit-locker. Do nothing and return.    RebootCoordinator    7/2/2013 5:13:00 PM    300 (0x012C)
    User S-1-5-21-4183147349-3640785585-127349212-318021 is getting pending reboot information...    RebootCoordinator    7/2/2013 5:13:33 PM    3476 (0x0D94)
    Reboot Coordinator received a SERVICEWINDOWEVENT START Event    RebootCoordinator    7/2/2013 10:00:00 PM    5912 (0x1718)
    Reboot Coordinator received a MaintenanceEvent Enter Event    RebootCoordinator    7/3/2013 3:11:27 AM    5916 (0x171C)
    Reboot Coordinator received a MaintenanceEvent Exit Event    RebootCoordinator    7/3/2013 4:11:25 AM    5336 (0x14D8)
    Reboot Coordinator received a SERVICEWINDOWEVENT END Event    RebootCoordinator    7/3/2013 5:00:00 AM    4104 (0x1008)
    Reboot Coordinator received a SERVICEWINDOWEVENT START Event    RebootCoordinator    7/3/2013 10:00:00 PM    3056 (0x0BF0)
    Reboot Coordinator received a MaintenanceEvent Enter Event    RebootCoordinator    7/4/2013 3:22:47 AM    4552 (0x11C8)
    Reboot Coordinator received a MaintenanceEvent Exit Event    RebootCoordinator    7/4/2013 4:22:45 AM    5260 (0x148C)
    Reboot Coordinator received a SERVICEWINDOWEVENT END Event    RebootCoordinator    7/4/2013 5:00:00 AM    4680 (0x1248)
    Reboot Coordinator received a SERVICEWINDOWEVENT START Event    RebootCoordinator    7/4/2013 9:00:00 AM    5836 (0x16CC)
    Including grace period 5400 seconds, the system restart turnaround time is 6000 seconds    RebootCoordinator    7/4/2013 9:00:18 AM    2964 (0x0B94)
    Entered ScheduleRebootImpl - requested from 'UpdatesDeploymentAgent'. Rebootby = 1372939244.    RebootCoordinator    7/4/2013 9:00:44 AM    2256 (0x08D0)
    Scheduled reboot from agent UpdatesDeploymentAgent. Deadline local time: 07/04/2013 09:00:44     RebootCoordinator    7/4/2013 9:00:44 AM    2256 (0x08D0)
    No CCM Identification blob    RebootCoordinator    7/4/2013 9:00:44 AM    2256 (0x08D0)
    Not in Service Mode, check ServiceWindowsManager next    RebootCoordinator    7/4/2013 9:00:44 AM    2256 (0x08D0)
    ServiceWindowsManager has not allowed us to Reboot    RebootCoordinator    7/4/2013 9:00:44 AM    2256 (0x08D0)
    Raising event:
    [SMS_CodePage(850), SMS_LocaleID(1046)]
    instance of SoftDistRebootWaitingForServiceWindowEvent
    {
        ClientID = "GUID:94CD6FDF-5687-45DE-9F55-700A4E2F28BD";
        DateTime = "20130704120044.293000+000";
        MachineName = "RHMAIL29";
        ProcessID = 2920;
        SiteCode = "D22";
        ThreadID = 2256;
    };
        RebootCoordinator    7/4/2013 9:00:44 AM    2256 (0x08D0)
    Succesfully raised SoftDistRebootWaitingForServiceWindowEvent event     RebootCoordinator    7/4/2013 9:00:44 AM    2256 (0x08D0)
    ServiceWindowsManager says that we will not be able to Reboot in the future    RebootCoordinator    7/4/2013 9:00:44 AM    2256 (0x08D0)
    We may not Reboot ever. Sending 'System May Never Reboot' Status Message    RebootCoordinator    7/4/2013 9:00:44 AM    2256 (0x08D0)
    Raising event:
    [SMS_CodePage(850), SMS_LocaleID(1046)]
    instance of SoftDistErrorSystemMayNeverRebootEvent
    {
        ClientID = "GUID:94CD6FDF-5687-45DE-9F55-700A4E2F28BD";
        DateTime = "20130704120044.308000+000";
        MachineName = "RHMAIL29";
        ProcessID = 2920;
        SiteCode = "D22";
        ThreadID = 2256;
    };
        RebootCoordinator    7/4/2013 9:00:44 AM    2256 (0x08D0)
    Succesfully raised SoftDistErrorSystemMayNeverRebootEvent event     RebootCoordinator    7/4/2013 9:00:44 AM    2256 (0x08D0)
    Raising client SDK event for class NULL, instance NULL, actionType 3l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l    RebootCoordinator    7/4/2013 9:00:44 AM    2256 (0x08D0)
    User S-1-5-21-4183147349-3640785585-127349212-318021 is getting pending reboot information...    RebootCoordinator    7/4/2013 9:00:44 AM    1040 (0x0410)
    User S-1-5-21-4183147349-3640785585-127349212-318021 is getting pending reboot information...    RebootCoordinator    7/4/2013 9:00:45 AM    1040 (0x0410)
    User S-1-5-21-4183147349-3640785585-127349212-318021 is getting pending reboot information...    RebootCoordinator    7/4/2013 9:00:45 AM    1040 (0x0410)
    Reboot Coordinator received a SERVICEWINDOWEVENT END Event    RebootCoordinator    7/4/2013 9:30:00 AM    4688 (0x1250)
    Reboot Coordinator received a SERVICEWINDOWEVENT DELETE Event    RebootCoordinator    7/4/2013 11:56:52 AM    3776 (0x0EC0)
    No CCM Identification blob    RebootCoordinator    7/4/2013 11:56:52 AM    3776 (0x0EC0)
    Not in Service Mode, check ServiceWindowsManager next    RebootCoordinator    7/4/2013 11:56:52 AM    3776 (0x0EC0)
    ServiceWindowsManager has not allowed us to Reboot    RebootCoordinator    7/4/2013 11:56:52 AM    3776 (0x0EC0)
    Reboot Coordinator received a SERVICEWINDOWEVENT DELETE Event    RebootCoordinator    7/4/2013 12:56:48 PM    4252 (0x109C)
    No CCM Identification blob    RebootCoordinator    7/4/2013 12:56:48 PM    4252 (0x109C)
    Not in Service Mode, check ServiceWindowsManager next    RebootCoordinator    7/4/2013 12:56:48 PM    4252 (0x109C)
    ServiceWindowsManager has not allowed us to Reboot    RebootCoordinator    7/4/2013 12:56:48 PM    4252 (0x109C)
    Reboot Coordinator received a SERVICEWINDOWEVENT START Event    RebootCoordinator    7/4/2013 10:00:00 PM    6128 (0x17F0)
    No CCM Identification blob    RebootCoordinator    7/4/2013 10:00:00 PM    6128 (0x17F0)
    Not in Service Mode, check ServiceWindowsManager next    RebootCoordinator    7/4/2013 10:00:00 PM    6128 (0x17F0)
    ServiceWindowsManager has not allowed us to Reboot    RebootCoordinator    7/4/2013 10:00:00 PM    6128 (0x17F0)
    Reboot Coordinator received a MaintenanceEvent Enter Event    RebootCoordinator    7/5/2013 3:03:31 AM    5116 (0x13FC)
    Reboot Coordinator received a MaintenanceEvent Exit Event    RebootCoordinator    7/5/2013 4:03:29 AM    5192 (0x1448)
    Reboot Coordinator received a SERVICEWINDOWEVENT END Event    RebootCoordinator    7/5/2013 5:00:00 AM    5240 (0x1478)
    Reboot Coordinator received a SERVICEWINDOWEVENT START Event    RebootCoordinator    7/5/2013 10:00:00 PM    980 (0x03D4)
    No CCM Identification blob    RebootCoordinator    7/5/2013 10:00:00 PM    980 (0x03D4)
    Not in Service Mode, check ServiceWindowsManager next    RebootCoordinator    7/5/2013 10:00:00 PM    980 (0x03D4)
    ServiceWindowsManager has not allowed us to Reboot    RebootCoordinator    7/5/2013 10:00:00 PM    980 (0x03D4)
    Reboot Coordinator received a SERVICEWINDOWEVENT END Event    RebootCoordinator    7/6/2013 12:00:00 AM    4244 (0x1094)
    Reboot Coordinator received a SERVICEWINDOWEVENT START Event    RebootCoordinator    7/6/2013 12:00:00 AM    4048 (0x0FD0)
    Reboot Coordinator received a SERVICEWINDOWEVENT END Event    RebootCoordinator    7/6/2013 12:00:00 AM    3384 (0x0D38)
    No CCM Identification blob    RebootCoordinator    7/6/2013 12:00:00 AM    4048 (0x0FD0)
    Not in Service Mode, check ServiceWindowsManager next    RebootCoordinator    7/6/2013 12:00:00 AM    4048 (0x0FD0)
    ServiceWindowsManager has not allowed us to Reboot    RebootCoordinator    7/6/2013 12:00:00 AM    4048 (0x0FD0)
    Reboot Coordinator received a MaintenanceEvent Enter Event    RebootCoordinator    7/6/2013 3:14:43 AM    5024 (0x13A0)
    Reboot Coordinator received a MaintenanceEvent Exit Event    RebootCoordinator    7/6/2013 4:14:41 AM    5436 (0x153C)
    Reboot Coordinator received a SERVICEWINDOWEVENT START Event    RebootCoordinator    7/7/2013 12:00:00 AM    5820 (0x16BC)
    No CCM Identification blob    RebootCoordinator    7/7/2013 12:00:00 AM    5820 (0x16BC)
    Not in Service Mode, check ServiceWindowsManager next    RebootCoordinator    7/7/2013 12:00:00 AM    5820 (0x16BC)
    ServiceWindowsManager has not allowed us to Reboot    RebootCoordinator    7/7/2013 12:00:00 AM    5820 (0x16BC)
    Reboot Coordinator received a MaintenanceEvent Enter Event    RebootCoordinator    7/7/2013 3:10:35 AM    4416 (0x1140)
    Reboot Coordinator received a MaintenanceEvent Exit Event    RebootCoordinator    7/7/2013 4:10:33 AM    3312 (0x0CF0)
    Reboot Coordinator received a SERVICEWINDOWEVENT END Event    RebootCoordinator    7/7/2013 5:00:00 AM    4248 (0x1098)
    Reboot Coordinator received a SERVICEWINDOWEVENT START Event    RebootCoordinator    7/8/2013 3:00:00 AM    3636 (0x0E34)
    No CCM Identification blob    RebootCoordinator    7/8/2013 3:00:00 AM    3636 (0x0E34)
    Not in Service Mode, check ServiceWindowsManager next    RebootCoordinator    7/8/2013 3:00:00 AM    3636 (0x0E34)
    ServiceWindowsManager has allowed us to Reboot    RebootCoordinator    7/8/2013 3:00:00 AM    3636 (0x0E34)
    No CCM Identification blob    RebootCoordinator    7/8/2013 3:00:00 AM    3636 (0x0E34)
    Not in Service Mode, check ServiceWindowsManager next    RebootCoordinator    7/8/2013 3:00:00 AM    3636 (0x0E34)
    ServiceWindowsManager has allowed us to Reboot    RebootCoordinator    7/8/2013 3:00:00 AM    3636 (0x0E34)
    MTC task does not exist. Creating new request.    RebootCoordinator    7/8/2013 3:00:00 AM    3636 (0x0E34)
    MTC allowed us to reboot    RebootCoordinator    7/8/2013 3:00:00 AM    3636 (0x0E34)
    Raising client SDK event for class NULL, instance NULL, actionType 4l, value 1373263200    1200    900, user NULL, session 4294967295l, level 0l, verbosity 30l    RebootCoordinator    7/8/2013 3:00:00 AM    3636 (0x0E34)
    Notified UI grace period start with 1200 grace seconds and 900 final seconds.    RebootCoordinator    7/8/2013 3:00:00 AM    3636 (0x0E34)
    MTC task for reboot '2e0409e3-349a-49ab-aca3-9bb7dc66585e'. Checking if it can run now...    RebootCoordinator    7/8/2013 3:05:00 AM    4880 (0x1310)
    MTC allowed us to reboot    RebootCoordinator    7/8/2013 3:05:00 AM    4880 (0x1310)
    System reboot request succeeded.    RebootCoordinator    7/8/2013 3:05:00 AM    4880 (0x1310)
    Reboot initiated    RebootCoordinator    7/8/2013 3:05:00 AM    4880 (0x1310)
    Reboot Coordinator received a MaintenanceEvent Enter Event    RebootCoordinator    7/8/2013 3:10:50 AM    2912 (0x0B60)
    User logoff notification received    RebootCoordinator    7/8/2013 3:20:04 AM    5508 (0x1584)
    Reboot Coordinator received a MaintenanceEvent Exit Event    RebootCoordinator    7/8/2013 3:20:04 AM    2912 (0x0B60)
    User is not logged on    RebootCoordinator    7/8/2013 3:20:04 AM    2912 (0x0B60)
    MTC task for reboot '2e0409e3-349a-49ab-aca3-9bb7dc66585e'. Checking if it can run now...    RebootCoordinator    7/8/2013 3:20:04 AM    2912 (0x0B60)
    MTC allowed us to reboot    RebootCoordinator    7/8/2013 3:20:04 AM    2912 (0x0B60)
    Shutdown is already in progress    RebootCoordinator    7/8/2013 3:20:04 AM    2912 (0x0B60)
    Failed to remove CCMDB object from global table, error 0x87d00200    RebootCoordinator    7/8/2013 3:20:04 AM    2912 (0x0B60)
    Reboot initiated    RebootCoordinator    7/8/2013 3:20:04 AM    2912 (0x0B60)
    Reboot Coordinator received a SERVICEWINDOWEVENT END Event    RebootCoordinator    7/8/2013 3:23:40 AM    5508 (0x1584)
    Reboot Coordinator received a SERVICEWINDOWEVENT START Event    RebootCoordinator    7/8/2013 3:23:40 AM    4224 (0x1080)
    No CCM Identification blob    RebootCoordinator    7/8/2013 3:23:40 AM    4224 (0x1080)
    Not in Service Mode, check ServiceWindowsManager next    RebootCoordinator    7/8/2013 3:23:40 AM    4224 (0x1080)
    ServiceWindowsManager has allowed us to Reboot    RebootCoordinator    7/8/2013 3:23:40 AM    4224 (0x1080)
    User is not logged on    RebootCoordinator    7/8/2013 3:23:40 AM    4224 (0x1080)
    MTC task for reboot '2e0409e3-349a-49ab-aca3-9bb7dc66585e'. Checking if it can run now...    RebootCoordinator    7/8/2013 3:23:40 AM    4224 (0x1080)
    MTC allowed us to reboot    RebootCoordinator    7/8/2013 3:23:40 AM    4224 (0x1080)
    Agent is still initializing, waiting for it to finish before rebooting...    RebootCoordinator    7/8/2013 3:23:40 AM    4224 (0x1080)
    Retry resuming bit-locker TPM PIN protector. Retry count 1    RebootCoordinator    7/8/2013 3:34:53 AM    2364 (0x093C)
    Didn't suspended bit-locker. Do nothing and return.    RebootCoordinator    7/8/2013 3:34:53 AM    2364 (0x093C)
    Reboot Coordinator received a MaintenanceEvent Enter Event    RebootCoordinator    7/8/2013 3:36:38 AM    1724 (0x06BC)
    Reboot Coordinator received a MaintenanceEvent Exit Event    RebootCoordinator    7/8/2013 4:36:36 AM    4012 (0x0FAC)
    Reboot Coordinator received a SERVICEWINDOWEVENT START Event    RebootCoordinator    7/8/2013 10:00:00 PM    3876 (0x0F24)
    Reboot Coordinator received a MaintenanceEvent Enter Event    RebootCoordinator    7/9/2013 3:02:57 AM    4376 (0x1118)
    Reboot Coordinator received a SERVICEWINDOWEVENT END Event    RebootCoordinator    7/9/2013 3:22:58 AM    1668 (0x0684)
    Reboot Coordinator received a SERVICEWINDOWEVENT START Event    RebootCoordinator    7/9/2013 3:22:58 AM    1668 (0x0684)
    Reboot Coordinator received a MaintenanceEvent Exit Event    RebootCoordinator    7/9/2013 4:04:04 AM    3872 (0x0F20)
    Reboot Coordinator received a SERVICEWINDOWEVENT END Event    RebootCoordinator    7/9/2013 4:22:58 AM    2232 (0x08B8)
    Reboot Coordinator received a SERVICEWINDOWEVENT START Event    RebootCoordinator    7/9/2013 4:22:58 AM    2752 (0x0AC0)
    Reboot Coordinator received a SERVICEWINDOWEVENT END Event    RebootCoordinator    7/9/2013 5:00:00 AM    3336 (0x0D08)
    Reboot Coordinator received a SERVICEWINDOWEVENT START Event    RebootCoordinator    7/9/2013 10:00:00 PM    2496 (0x09C0)
    Reboot Coordinator received a MaintenanceEvent Enter Event    RebootCoordinator    7/10/2013 3:11:55 AM    4092 (0x0FFC)
    Reboot Coordinator received a MaintenanceEvent Exit Event    RebootCoordinator    7/10/2013 4:11:53 AM    4832 (0x12E0)
    Reboot Coordinator received a SERVICEWINDOWEVENT END Event    RebootCoordinator    7/10/2013 5:00:00 AM    3204 (0x0C84)
    Reboot Coordinator received a SERVICEWINDOWEVENT START Event    RebootCoordinator    7/10/2013 10:00:00 PM    4152 (0x1038)
    Reboot Coordinator received a MaintenanceEvent Enter Event    RebootCoordinator    7/11/2013 3:23:21 AM    3668 (0x0E54)
    Reboot Coordinator received a MaintenanceEvent Exit Event    RebootCoordinator    7/11/2013 4:23:19 AM    3888 (0x0F30)
    Reboot Coordinator received a SERVICEWINDOWEVENT END Event    RebootCoordinator    7/11/2013 5:00:00 AM    3888 (0x0F30)
    Reboot Coordinator received a SERVICEWINDOWEVENT START Event    RebootCoordinator    7/11/2013 9:00:00 AM    3488 (0x0DA0)
    System restart turnaround time is 600 seconds.    RebootCoordinator    7/11/2013 9:00:40 AM    3276 (0x0CCC)
    System restart turnaround time is 600 seconds.    RebootCoordinator    7/11/2013 9:03:13 AM    3432 (0x0D68)
    System restart turnaround time is 600 seconds.    RebootCoordinator    7/11/2013 9:05:38 AM    2364 (0x093C)
    System restart turnaround time is 600 seconds.    RebootCoordinator    7/11/2013 9:11:13 AM    5788 (0x169C)
    System restart turnaround time is 600 seconds.    RebootCoordinator    7/11/2013 9:13:02 AM    5380 (0x1504)
    System restart turnaround time is 600 seconds.    RebootCoordinator    7/11/2013 9:13:14 AM    3320 (0x0CF8)
    System restart turnaround time is 600 seconds.    RebootCoordinator    7/11/2013 9:13:24 AM    5840 (0x16D0)
    System restart turnaround time is 600 seconds.    RebootCoordinator    7/11/2013 9:16:47 AM    5124 (0x1404)
    Entered ScheduleRebootImpl - requested from 'UpdatesDeploymentAgent'. Rebootby = 1373545184.    RebootCoordinator    7/11/2013 9:19:44 AM    5124 (0x1404)
    Scheduled reboot from agent UpdatesDeploymentAgent. Deadline local time: 07/11/2013 09:19:44     RebootCoordinator    7/11/2013 9:19:44 AM    5124 (0x1404)
    User is not logged on    RebootCoordinator    7/11/2013 9:19:44 AM    5124 (0x1404)
    No CCM Identification blob    RebootCoordinator    7/11/2013 9:19:44 AM    5124 (0x1404)
    Not in Service Mode, check ServiceWindowsManager next    RebootCoordinator    7/11/2013 9:19:44 AM    5124 (0x1404)
    ServiceWindowsManager has allowed us to Reboot    RebootCo

    Thursday, July 11, 2013 1:26 PM
  • Plz anyone help-me ?

    the maintenance window, had the option of the AM Wednesday 2:00 to 3:00. But the machine restarted AM 9: xx

    WUAHandler.log

    Its a WSUS Update Source type ({B7B46584-C6DE-4B34-A9EB-9E8B5E2BF453}), adding it.	WUAHandler	8/8/2013 2:16:24 AM	2596 (0x0A24)
    Existing WUA Managed server was already set (HTTP://RHCM01.REDEHOST.LOCAL:8530), skipping Group Policy registration.	WUAHandler	8/8/2013 2:16:26 AM	2596 (0x0A24)
    Added Update Source ({B7B46584-C6DE-4B34-A9EB-9E8B5E2BF453}) of content type: 2	WUAHandler	8/8/2013 2:16:26 AM	2596 (0x0A24)
    Scan results will include superseded updates only when they are superseded by service packs and definition updates.	WUAHandler	8/8/2013 2:16:27 AM	2596 (0x0A24)
    Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')	WUAHandler	8/8/2013 2:16:27 AM	2596 (0x0A24)
    Async searching of updates using WUAgent started.	WUAHandler	8/8/2013 2:16:37 AM	2596 (0x0A24)
    Async searching completed.	WUAHandler	8/8/2013 2:18:43 AM	3388 (0x0D3C)
    Successfully completed scan.	WUAHandler	8/8/2013 2:18:45 AM	2596 (0x0A24)
    CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for bundles	WUAHandler	8/8/2013 9:44:40 AM	3288 (0x0CD8)
    Update (1a9808ac-77c0-42e2-9699-9e1c5786d823) has finished the post reboot operation. HResult: 0x00000000.	WUAHandler	8/8/2013 9:44:54 AM	4204 (0x106C)
    Update (4485f552-0451-4646-b224-bec7507523f3) has finished the post reboot operation. HResult: 0x00000000.	WUAHandler	8/8/2013 9:44:54 AM	4204 (0x106C)
    Update (804f6d0c-b10c-4924-b4bc-34d5ec563c30) has finished the post reboot operation. HResult: 0x00000000.	WUAHandler	8/8/2013 9:44:54 AM	4204 (0x106C)
    Update (d1b8a640-d317-43bc-a3e4-dd59066d31ab) has finished the post reboot operation. HResult: 0x00000000.	WUAHandler	8/8/2013 9:44:54 AM	4204 (0x106C)
    Update (ffbb3522-6936-4370-becd-4bcd29ed4929) has finished the post reboot operation. HResult: 0x00000000.	WUAHandler	8/8/2013 9:44:54 AM	4204 (0x106C)
    Update (18a9ac96-977f-42c0-a194-7c9b09e058b0) has finished the post reboot operation. HResult: 0x00000000.	WUAHandler	8/8/2013 9:44:54 AM	4204 (0x106C)
    Update (2d173ad4-7706-4220-a7d1-aa4bb36863b9) has finished the post reboot operation. HResult: 0x00000000.	WUAHandler	8/8/2013 9:44:54 AM	4204 (0x106C)
    Update (3a0bf4ed-9b13-4738-bedb-7343f4aebf45) has finished the post reboot operation. HResult: 0x00000000.	WUAHandler	8/8/2013 9:44:54 AM	4204 (0x106C)
    Update (48e38091-1fbd-4e55-ac2e-a165813ff254) has finished the post reboot operation. HResult: 0x00000000.	WUAHandler	8/8/2013 9:44:54 AM	4204 (0x106C)
    Update (4d9b3b3f-47c4-4766-989b-2a074a8c02d1) has finished the post reboot operation. HResult: 0x00000000.	WUAHandler	8/8/2013 9:44:54 AM	4204 (0x106C)
    Update (4e90a4a2-2e86-49de-bbe8-88bc13a1d89f) has finished the post reboot operation. HResult: 0x00000000.	WUAHandler	8/8/2013 9:44:54 AM	4204 (0x106C)
    Update (69093601-af5b-41e6-a23e-3c4188c6866e) has finished the post reboot operation. HResult: 0x00000000.	WUAHandler	8/8/2013 9:44:54 AM	4204 (0x106C)
    Update (6b9132b1-49a2-41f0-b2ae-1a7edd858963) has finished the post reboot operation. HResult: 0x00000000.	WUAHandler	8/8/2013 9:44:54 AM	4204 (0x106C)
    Update (709f509e-50e7-41fc-b160-be6aff6e012f) has finished the post reboot operation. HResult: 0x00000000.	WUAHandler	8/8/2013 9:44:54 AM	4204 (0x106C)
    Update (b29b8182-2072-495e-a74f-eda734dc7f7f) has finished the post reboot operation. HResult: 0x00000000.	WUAHandler	8/8/2013 9:44:54 AM	4204 (0x106C)
    Update (bec67f2f-7a02-489d-814c-08f385be0e62) has finished the post reboot operation. HResult: 0x00000000.	WUAHandler	8/8/2013 9:44:54 AM	4204 (0x106C)
    Update (d5661a45-cfeb-460f-972a-777c156c626c) has finished the post reboot operation. HResult: 0x00000000.	WUAHandler	8/8/2013 9:44:54 AM	4204 (0x106C)
    Scan results will include superseded updates only when they are superseded by service packs and definition updates.	WUAHandler	8/8/2013 9:44:54 AM	4204 (0x106C)
    Search Criteria is ((DeploymentAction=* AND Type='Software' AND CategoryIDs contains '0FA1201D-4330-4FA8-8AE9-B877473B6441') OR (DeploymentAction=* AND Type='Software' AND CategoryIDs contains 'E6CF1350-C01B-414D-A61F-263D14D133B4'))	WUAHandler	8/8/2013 9:44:54 AM	4204 (0x106C)
    Async searching of updates using WUAgent started.	WUAHandler	8/8/2013 9:44:54 AM	4204 (0x106C)
    Async searching completed.	WUAHandler	8/8/2013 9:47:09 AM	4704 (0x1260)
    Successfully completed scan.	WUAHandler	8/8/2013 9:47:10 AM	3596 (0x0E0C)
    Scan results will include superseded updates only when they are superseded by service packs and definition updates.	WUAHandler	8/8/2013 9:47:18 AM	3388 (0x0D3C)
    Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')	WUAHandler	8/8/2013 9:47:18 AM	3388 (0x0D3C)
    Async searching of updates using WUAgent started.	WUAHandler	8/8/2013 9:47:18 AM	3388 (0x0D3C)
    Async searching completed.	WUAHandler	8/8/2013 9:47:31 AM	3288 (0x0CD8)
    Successfully completed scan.	WUAHandler	8/8/2013 9:47:33 AM	3388 (0x0D3C)
    

    CCMExec.log

    CSensLog2_LogoffFunc failed. (0x80070002)	CCMEXEC	8/8/2013 9:30:22 AM	6272 (0x1880)
    Could not load logging configuration for component CcmTask. Using default values.	CcmExec	8/8/2013 9:44:41 AM	4204 (0x106C)
    System task 'SMSSHA_Startup' returned error code 0x87d0027f.	CcmExec	8/8/2013 9:44:52 AM	3288 (0x0CD8)
    Could not load logging configuration for component FileSystemFile. Using default values.	CcmExec	8/8/2013 9:51:17 AM	3972 (0x0F84)
    

    RebootCoordinator.log

    Reboot Coordinator received a MaintenanceEvent Enter Event	RebootCoordinator	8/8/2013 3:07:56 AM	4988 (0x137C)
    Reboot Coordinator received a MaintenanceEvent Exit Event	RebootCoordinator	8/8/2013 4:07:49 AM	780 (0x030C)
    Reboot Coordinator received a SERVICEWINDOWEVENT END Event	RebootCoordinator	8/8/2013 5:00:00 AM	5544 (0x15A8)
    Reboot Coordinator received a SERVICEWINDOWEVENT START Event	RebootCoordinator	8/8/2013 9:00:00 AM	5684 (0x1634)
    No CCM Identification blob	RebootCoordinator	8/8/2013 9:00:00 AM	5684 (0x1634)
    Not in Service Mode, check ServiceWindowsManager next	RebootCoordinator	8/8/2013 9:00:00 AM	5684 (0x1634)
    ServiceWindowsManager has allowed us to Reboot	RebootCoordinator	8/8/2013 9:00:00 AM	5684 (0x1634)
    No CCM Identification blob	RebootCoordinator	8/8/2013 9:00:00 AM	5684 (0x1634)
    Not in Service Mode, check ServiceWindowsManager next	RebootCoordinator	8/8/2013 9:00:00 AM	5684 (0x1634)
    ServiceWindowsManager has allowed us to Reboot	RebootCoordinator	8/8/2013 9:00:00 AM	5684 (0x1634)
    MTC task does not exist. Creating new request.	RebootCoordinator	8/8/2013 9:00:00 AM	5684 (0x1634)
    MTC allowed us to reboot	RebootCoordinator	8/8/2013 9:00:00 AM	5684 (0x1634)
    Raising client SDK event for class NULL, instance NULL, actionType 4l, value 1375963200	1800	1500, user NULL, session 4294967295l, level 0l, verbosity 30l	RebootCoordinator	8/8/2013 9:00:00 AM	5684 (0x1634)
    Notified UI grace period start with 1800 grace seconds and 1500 final seconds.	RebootCoordinator	8/8/2013 9:00:00 AM	5684 (0x1634)
    MTC task for reboot '451f074a-ad9d-4449-8f12-7a1ef0b76ad2'. Checking if it can run now...	RebootCoordinator	8/8/2013 9:05:00 AM	4416 (0x1140)
    MTC allowed us to reboot	RebootCoordinator	8/8/2013 9:05:00 AM	4416 (0x1140)
    System reboot request succeeded.	RebootCoordinator	8/8/2013 9:05:00 AM	4416 (0x1140)
    Reboot initiated	RebootCoordinator	8/8/2013 9:05:00 AM	4416 (0x1140)
    Reboot Coordinator received a SERVICEWINDOWEVENT END Event	RebootCoordinator	8/8/2013 9:30:00 AM	6272 (0x1880)
    User logoff notification received	RebootCoordinator	8/8/2013 9:30:23 AM	2764 (0x0ACC)
    Retry resuming bit-locker TPM PIN protector. Retry count 1	RebootCoordinator	8/8/2013 9:44:39 AM	4204 (0x106C)
    Didn't suspended bit-locker. Do nothing and return.	RebootCoordinator	8/8/2013 9:44:39 AM	4204 (0x106C)
    User S-1-5-21-4183147349-3640785585-127349212-1115 is getting pending reboot information...	RebootCoordinator	8/8/2013 9:46:20 AM	4516 (0x11A4)
    Reboot Coordinator received a MaintenanceEvent Enter Event	RebootCoordinator	8/8/2013 9:50:27 AM	4256 (0x10A0)
    User logoff notification received	RebootCoordinator	8/8/2013 9:51:55 AM	4072 (0x0FE8)
    

    Can u help ?

    Thursday, August 08, 2013 1:05 PM
  • anyone? plz
    Monday, August 12, 2013 12:31 PM
  • Looks like there is an additional maintenance windows from 09.00 to 09.30 AM. The machine rebooted during that window.

    There is a builtin report called 'Maintenance Windows available to a specific client' which might help identifying why and when your machine(s) reboot.

    Monday, August 12, 2013 1:30 PM
  • thanks.

    all clientes are in a Maintenance Windows called Testm but don't exist in console



    Monday, August 12, 2013 1:48 PM
  • Sorry, I found and removed

    Maintenace Windows 'Test"

    Start: 12:00PM  End: 12:30 PM

    Checked "UTC" ( If cheked maintenance Start in 09:00 AM GMT )

    Working All Thusday

    http://www.timeanddate.com/worldclock/fixedtime.html?hour=12&min=0&sec=0&p1=0

    Thanks



    I will wait this week to see if something will happen
    Monday, August 12, 2013 1:54 PM