I've 3 windows server 2008one is Domain controller (64bit)one installed exchange 2010 (64bit)the last one installed MSSQL (32bit)both server will reboot after a press the log off tag.patches in both servers are up to datei have use differnet antivirus software to ensure there are no infectedi checked log there are no event about the reboot issue

Hi, I understand your Windows Server 2008 will reboot after pressing Log off. Currently, please first test if the problem exists in Safe Mode. If not, try clean boot to disable third party service and application to monitor if the issue can be fixed. 1. Click "Start", go to "Run", and type "msconfig" in the open box to start the System Configuration Utility. 2. Click the "Services" tab, check the "Hide All Microsoft Services" box and click Disable All (if it is not gray). 3. Click the "Startup" tab, click "Disable All" and click "OK". 4. Restart your computer. When the "System Configuration Utility" window appears, please check the box and click "OK". Check if the problem exists now. Regards, Bruce

Hi This is strange behavior and is not reported by any of the users world wide. Pressing logoff should not trigger shutdown.exe which is strange and checking in safe mode as bruce suggested would prove us if there is any 3rd party applicaiton which is calling the shutdown.exe

I have the same issue on 3 different SBS 2008 x64 servers Seems to be related to windows update. I havent found anything yet but looks like if server needs a reboot and your credentials are high enough it will trigger a needed reboot on log off

We are getting exactly the same behaviour here. We have 10virtual servers running on the hyper V server. Updates are set to automatically install however I dont expect the server to restart when I log off when updates have been installed. This should only happen when you explicitly tell the server to restart? It wont be hard to replicate this functionality if any MS people are reading this. Simply install some updates (automatically to replicated our problem) and then simply click start, Logoff. Interestingly instead of seeing my log off event in the system log I see this instead. The process C:\Windows\system32\svchost.exe (OBUKTAM01HYP01) has initiated the restart of computer OBUKTAM01HYP01 on behalf of user NT AUTHORITY\SYSTEM for the following reason: Operating System: Recovery (Planned) Reason Code: 0x80020002 Shutdown Type: restart Comment: - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="USER32" /> <EventID Qualifiers="32768">1074</EventID> <Level>4</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2010-02-23T08:34:09.000000000Z" /> <EventRecordID>20399</EventRecordID> <Channel>System</Channel> <Computer>OBUKTAM01HYP01.obnet.local</Computer> <Security UserID="S-1-5-18" /> </System> - <EventData> <Data>C:\Windows\system32\svchost.exe (OBUKTAM01HYP01)</Data> <Data>OBUKTAM01HYP01</Data> <Data>Operating System: Recovery (Planned)</Data> <Data>0x80020002</Data> <Data>restart</Data> <Data /> <Data>NT AUTHORITY\SYSTEM</Data> <Binary>02000280000000000000000000000000000000000000000000000000000000000000000000000000</Binary> </EventData> </Event>

Yep, same exact issue here. And it is related to WU. Whenever I have a pending restart per WU, if I logout (domain admin) the machine will restart!!! Not cool!!!!! Any answers to this issue? Please fix MS! Windows Storage Server 2008 Std SP2 x64 Domain: Windows 2000 native ...for some still antiquated machines :/ -Nic

OK, I think this will stop your servers from Auto-Restarting when you log off. Set up a Group Policy rule and disable the following setting. You should then set a policy setting to auto install and reboot when you can (like 1am saturday mornings for example) and only if your happy to install all updates sent to the servers. Computer ConfigurationPoliciesAdministrative Templates Windows Components/Windows UpdateNo auto-restart with logged on users for scheduled automatic updates installations - Disabled this. Explanation of Policy.... Specifies that to complete a scheduled installation, Automatic Updates will wait for the computer to be restarted by any user who is logged on, instead of causing the computer to restart automatically.If the status is set to Enabled, Automatic Updates will not restart a computer automatically during a scheduled installation if a user is logged in to the computer. Instead, Automatic Updates will notify the user to restart the computer.Be aware that the computer needs to be restarted for the updates to take effect.If the status is set to Disabled or Not Configured, Automatic Updates will notify the user that the computer will automatically restart in 5 minutes to complete the installation.Note: This policy applies only when Automatic Updates is configured to perform scheduled installations of updates. If the "Configure Automatic Updates" policy is disabled, this policy has no effect.

I just had this occur on three of our cluster nodes. Nodes had updates installed pending a restart, and a domain admin hit Start, Logoff, then the node restarted. This also happened to a second and third node before we realised what had happened. Needless to say, this brought down the majority of our Hyper-V production environment right in the middle of peak work for our entire company. Please note that we already have the no-restart GP set as part of our WSUS configuration for updates on servers so that wouldn't solve the issue for people having this exact same problem. The cluster nodes we have are Windows 2008 R2 Enterprise Edition. Here is the event viewer entry: Event ID: 1074 Source: USER32 The process C:\Windows\system32\svchost.exe (MSQVMHOST2) has initiated the restart of computer MSQVMHOST2 on behalf of user NT AUTHORITY\SYSTEM for the following reason: Operating System: Recovery (Planned) Reason Code: 0x80020002 Shutdown Type: restart

I too have just had the same problem on Windows Server 2008 R2 with Exchange 2010 installed. The event logs are showing the same errors as Caillin

This issue was resolved from me once I began managing the GPO's from a Windows 7 machine (Vista or 2008 will work too). Apparently it seems the WU GPO's were not being handled correctly by the Win 2008 file server on my 2003 domain. This is likely because of the new ADMX format. http://forums.techarena.in/active-directory/1087610.htm http://technet.microsoft.com/en-us/library/cc709647%28WS.10%29.aspx Hope this helps.

Check your automatic update settings. Ensure that they are not set to install automatically.