I believe that is expected behavior as there are special protections around session 0 prior to the Vista/Longhorn era when console users stopped getting session 0.
From: Jeff Bunting [mailto:[email protected]] Sent: Wednesday, April 01, 2009 10:54 AM To: NT System Admin Issues Subject: Re: Strange VM problem; CTRL-ALT-DEL doesn't work Thanks for the suggestion. The console is locked now, so I used psexec to attach to the system: C:\WINDOWS\system32>logoff 0 Could not logoff session ID 0, Error code 31 Error [31]:A device attached to the system is not functioning. It look awhile (20 seconds or so) before it came back with the error. On Wed, Apr 1, 2009 at 12:46 PM, Don Kuhlman <[email protected]> wrote: Well, not sure about that one right now Jeff, but can you use the cmd line option "logoff" to sign off while you're working on the issue? Don K ________________________________ From: Jeff Bunting <[email protected]> To: NT System Admin Issues <[email protected]> Sent: Wednesday, April 1, 2009 11:27:36 AM Subject: Strange VM problem; CTRL-ALT-DEL doesn't work Windows 2003 SP1 VM on ESX 3.5 won't respond to CTRL-ALT-DEL command from either VMware client or Dameware. I clicked on the "Help" link on the logon screen and it gave me the logon prompt. Was able to logon as local admin OK, but now can't logoff. All services appear to be OK, tried stopping/restarting dameware and vmtools services to no effect. Any ideas besides rebooting? (production system of course) just tried Windows-L to lock console, which worked. now I can't unlock.... Thanks, Jeff ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
