I have a Windows Server 2008 with Hyper-V test machine. It was a full install -- not just core. I have a KVM switch for the keyboard, monitor, mouse, microphone and speakers. Every now and then whent the Server 2008 is running without the user interface items connected it seems to go intoa headless mode. That is, when I switch to it the monitor goes blank and moving the mouse or pressing the arrow keys do not seem to have any effect. I have remote access setup and I can connect to the machine via remote desktop and it is still alive -- just ignoring the physical monitor attached via the switch.I don't think it is the switch as most of the time it works fine. It seems to happen if the physical devices are switched away for a day or two.

hi saberman,can you try without the kvm switch ?, also can you open device manager and check if you see any "?" symbols, also we would like to get the event id from system and application ( errors / warnings ) sainath Windows Driver Development

Hi,I guess the issue is related to the KVM switch, you may consider Sainath's suggestions to have a check.Best regards,Vincent Hu

The server has been running for a number of months connected to the switch. It also appears that the system is shutting itself down. I think the connection via Remote Desktop was a timing fluke as it no longer works when the system appears to stop.The only event logentry I could find that appeared appropriate is listed below. It was generated when I restarted the system after powering it down and up again. Aside from this entry all of the others are informational. The last entry before the unexpected shutdown was at 12:43: 37 AM a little under five minutes earlier and all it said was: "A worker process with process id of '4072' serving application pool 'DefaultAppPool' was shutdown due to inactivity. Application Pool timeout configuration was set to 20 minutes. A new worker process will be started when needed."The system is using the default settings for the Balanced power plan.As you can tell from the time span between the unexpected shutdown and the time I rebooted the server is not used for extended periods of time. Is there anywhere else I can look for what is causing the shutdown.Log Name: SystemSource: EventLogDate: 4/28/2009 5:20:17 PMEvent ID: 6008Task Category: NoneLevel: ErrorKeywords: ClassicUser: N/AComputer: NYSABS0010Description:The previous system shutdown at 12:48:16 AM on 4/27/2009 was unexpected.Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="EventLog" /> <EventID Qualifiers="32768">6008</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2009-04-28T21:20:17.000Z" /> <EventRecordID>42513</EventRecordID> <Channel>System</Channel> <Computer>NYSABS0010</Computer> <Security /> </System> <EventData> <Data>12:48:16 AM</Data> <Data>4/27/2009</Data> <Data> </Data> <Data> </Data> <Data>7613</Data> <Data> </Data> <Data> </Data> <Binary>D907040001001B000000300010001A02D907040001001B000400300010001A023C0000003C000000000000000000000000000000000000000100000002000000</Binary> </EventData></Event>

Hi Saberman, How did you power the server down? From the start menu---Shut down or push the power button on the machine? I suggestion that you connect the monitor to this server directly and keep some days to have a monitoring. Then we can do the further research. Best regards, Vincent Hu

I usually hit the reset button as I cannot shut the machine down normally as I don't have access to a working console. On startup I get the screen with the message that Windows did not shutdown normally and select normal startup.One additonal item:When the machine stops responding to the hardware on the switch I try a remote desktop connection from another machine. It doesn't time out -- just continues to try until I cancel it. However, I can map drives on the server from another machine so the machine is alive -- just refusing to talk.I don't have a spare monitor that I can dedicate to the server.I think I will just wait another week and do a fresh build using Windows Server 2008 R2 RTM.