I use a client setting, for testing purposes, deployed to my test VM's, set at priority 1, with the Computer Restart configured with the following configuration;
Display a temporary Notification... = 2 minutes
Display a dialog box that user cannot close... = 1 minute
It's deployed to my VM's and my VMs are receiving the policy however I am getting two different results. My x86 VM see a pending reboot and performs a reboot in the 2 minute time frame however my x64 VM does not. The VM's are as identical as possible as far as the SCCM & OS configuration is concerned, but I can not figure out why my x64 VM will not auto reboot. Below is my RebootCoordinator.log and I see it says "...Reboot cannot be been initiated now..." and I do not know why. Any thoughts?
User S-1-5-21-1177238915-57989841-1801674531-13618 is getting pending reboot information... RebootCoordinator 4/22/2014 9:39:57 AM 2908 (0x0B5C) User S-1-5-21-1177238915-57989841-1801674531-13618 is getting pending reboot information... RebootCoordinator 4/22/2014 9:39:58 AM 2908 (0x0B5C) User S-1-5-21-1177238915-57989841-1801674531-13618 is getting pending reboot information... RebootCoordinator 4/22/2014 9:40:12 AM 2908 (0x0B5C) User S-1-5-21-1177238915-57989841-1801674531-13618 is getting pending reboot information... RebootCoordinator 4/22/2014 9:40:13 AM 2908 (0x0B5C) User S-1-5-21-1177238915-57989841-1801674531-13618 is getting pending reboot information... RebootCoordinator 4/22/2014 9:40:22 AM 2908 (0x0B5C) User S-1-5-21-1177238915-57989841-1801674531-13618 is getting pending reboot information... RebootCoordinator 4/22/2014 9:41:05 AM 2908 (0x0B5C) Reboot Coordinator received a SERVICEWINDOWEVENT MODIFY Event RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) No CCM Identification blob RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) Not in Service Mode, check ServiceWindowsManager next RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) ServiceWindowsManager has allowed us to Reboot RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) No CCM Identification blob RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) Not in Service Mode, check ServiceWindowsManager next RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) ServiceWindowsManager has allowed us to Reboot RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) MTC task for reboot 'a5553b9c-870e-42aa-9b8d-b914a7c2689b'. Checking if it can run now... RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) Reboot cannot be been initiated now. Skip this request. RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) Reboot Coordinator received a SERVICEWINDOWEVENT MODIFY Event RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) No CCM Identification blob RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) Not in Service Mode, check ServiceWindowsManager next RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) ServiceWindowsManager has allowed us to Reboot RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) No CCM Identification blob RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) Not in Service Mode, check ServiceWindowsManager next RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) ServiceWindowsManager has allowed us to Reboot RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) MTC task for reboot 'a5553b9c-870e-42aa-9b8d-b914a7c2689b'. Checking if it can run now... RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) Reboot cannot be been initiated now. Skip this request. RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) Reboot Coordinator received a SERVICEWINDOWEVENT MODIFY Event RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) No CCM Identification blob RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) Not in Service Mode, check ServiceWindowsManager next RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) ServiceWindowsManager has allowed us to Reboot RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) No CCM Identification blob RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) Not in Service Mode, check ServiceWindowsManager next RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) ServiceWindowsManager has allowed us to Reboot RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) MTC task for reboot 'a5553b9c-870e-42aa-9b8d-b914a7c2689b'. Checking if it can run now... RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) Reboot cannot be been initiated now. Skip this request. RebootCoordinator 4/22/2014 9:41:40 AM 1904 (0x0770) Reboot Coordinator received a SERVICEWINDOWEVENT MODIFY Event RebootCoordinator 4/22/2014 9:41:40 AM 640 (0x0280) No CCM Identification blob RebootCoordinator 4/22/2014 9:41:40 AM 640 (0x0280) Not in Service Mode, check ServiceWindowsManager next RebootCoordinator 4/22/2014 9:41:40 AM 640 (0x0280) ServiceWindowsManager has allowed us to Reboot RebootCoordinator 4/22/2014 9:41:40 AM 640 (0x0280) Reboot Coordinator received a SERVICEWINDOWEVENT MODIFY Event RebootCoordinator 4/22/2014 9:41:40 AM 2092 (0x082C) No CCM Identification blob RebootCoordinator 4/22/2014 9:41:41 AM 640 (0x0280) Not in Service Mode, check ServiceWindowsManager next RebootCoordinator 4/22/2014 9:41:41 AM 640 (0x0280) ServiceWindowsManager has allowed us to Reboot RebootCoordinator 4/22/2014 9:41:41 AM 640 (0x0280) MTC task for reboot 'a5553b9c-870e-42aa-9b8d-b914a7c2689b'. Checking if it can run now... RebootCoordinator 4/22/2014 9:41:41 AM 640 (0x0280) Reboot cannot be been initiated now. Skip this request. RebootCoordinator 4/22/2014 9:41:41 AM 640 (0x0280) No CCM Identification blob RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) Not in Service Mode, check ServiceWindowsManager next RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) ServiceWindowsManager has allowed us to Reboot RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) No CCM Identification blob RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) Not in Service Mode, check ServiceWindowsManager next RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) ServiceWindowsManager has allowed us to Reboot RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) MTC task for reboot 'a5553b9c-870e-42aa-9b8d-b914a7c2689b'. Checking if it can run now... RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) Reboot cannot be been initiated now. Skip this request. RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) Reboot Coordinator received a SERVICEWINDOWEVENT MODIFY Event RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) No CCM Identification blob RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) Not in Service Mode, check ServiceWindowsManager next RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) ServiceWindowsManager has allowed us to Reboot RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) No CCM Identification blob RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) Not in Service Mode, check ServiceWindowsManager next RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) ServiceWindowsManager has allowed us to Reboot RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) MTC task for reboot 'a5553b9c-870e-42aa-9b8d-b914a7c2689b'. Checking if it can run now... RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) Reboot cannot be been initiated now. Skip this request. RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) Reboot Coordinator received a SERVICEWINDOWEVENT MODIFY Event RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) No CCM Identification blob RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) Not in Service Mode, check ServiceWindowsManager next RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) ServiceWindowsManager has allowed us to Reboot RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) No CCM Identification blob RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) Not in Service Mode, check ServiceWindowsManager next RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) ServiceWindowsManager has allowed us to Reboot RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) MTC task for reboot 'a5553b9c-870e-42aa-9b8d-b914a7c2689b'. Checking if it can run now... RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) Reboot cannot be been initiated now. Skip this request. RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) Reboot Coordinator received a SERVICEWINDOWEVENT MODIFY Event RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) No CCM Identification blob RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) Not in Service Mode, check ServiceWindowsManager next RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) ServiceWindowsManager has allowed us to Reboot RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) No CCM Identification blob RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) Not in Service Mode, check ServiceWindowsManager next RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) ServiceWindowsManager has allowed us to Reboot RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) MTC task for reboot 'a5553b9c-870e-42aa-9b8d-b914a7c2689b'. Checking if it can run now... RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C) Reboot cannot be been initiated now. Skip this request. RebootCoordinator 4/22/2014 9:41:41 AM 2092 (0x082C)