Got Me! That's what I get for bein too eager to help that I don't read the whole email! -----Original Message----- From: Petitti, Bruno [mailto:bpetitti@xxxxxx] Sent: Tuesday, September 28, 2004 12:53 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: TSSHUTDN That patch is only intended for a Windows 2000 server not a Windows 2003 server. -----Original Message----- From: Turman, David C. [mailto:david_turman@xxxxxxxxxxxxxxxx] Sent: Tuesday, September 28, 2004 12:47 To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: TSSHUTDN It was a patch. I have the hotfix to repair it kb829395 -----Original Message----- From: Anders Hansen-Øvre [mailto:Anders.Hansen-Ovre@xxxxxxxxx] Sent: Tuesday, September 28, 2004 11:32 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: TSSHUTDN Hi, yeh i've seen this issue with terminalservers that are updated with Windows Update. I think that a M$ patch is causing this issue but haven't had the time to find out which. We use pshutdown from Sysinternals to reboot server with this issue, you can download it from http://www.sysinternals.com <http://www.sysinternals.com> Hope this helps --- mvh/yours Anders Hansen-Øvre, Seniorkonsulent _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Petitti, Bruno Sent: 28. september 2004 16:48 To: thin@xxxxxxxxxxxxx Subject: [THIN] TSSHUTDN Currently, we use the TSSHUTDN /reboot /now command to reboot out servers on a regular bases. We are running this command on a Windows 2003 server with XPa FR3. Frequently, we receive the following error message in the event log. "The attempt by user NT AUTHORITY\SYSTEM to restart/shutdown computer (Server Name) failed" We are unable to connect to the server but if we do another remote reboot the server is fine after it comes back up. Is anyone else experiencing this problem?