Hello, my new machine won't awaken if I press the keyboard or the mouse, it has happened twice in the last 2 weeks, has anyone else experienced the same problem, I remember Vista had a similar problem if the computer was not used for long durations, or have I got a faulty machine, is there any way of testing this, thank you. John Harrison

It must be a hardware issue. Server don't ussually go in sleep mode.JR

Hi John, This issue can usually be caused by any of the following: 1. Devices or drivers2. Software Please update your BIOS, hardware devices such as video card, sound card, network card drivers to the latest version. In addition, remove unnecessary devices such as external hard drives. Please also try a Clean Boot to test the result. Clean Boot ======== 1. Click Start, type "MSCONFIG" (without the quotations) in the Search Bar and Press "Enter" to start the System Configuration Utility. Note: Please click Continue if the "User Account Control" window pops up. 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 the computer and test the issue. Note: Clean Boot is a troubleshooting step. If some programs have been disabled, we can re-enable them later. If you see the System Configuration Utility, check the box of "Don't show this message" and then click "OK". Please test this issue in the Clean Boot environment. If the issue disappears, we can use a 50/50 approach to quickly narrow down which entry is causing the issue. Please let me know the result. Tim Quan - MSFT

HelloThank you, I will give it a try. John Harrison

Hello TimHopefully, problem solved, I had a Netgear WGT624 Wifi usb adapter installed on my server, I have removed it & everything seems ok, will keep an eye on it, thanks for the advice, I am new to Windows server & will start to read up on the subject, can you recommend any books or training facilities, thak you. John Harrison

Hello John, Thank you for letting me know the cause of the issue has been found. I suggest reading the following Windows Server technical sites: http://technet.microsoft.com/en-us/library/bb625087.aspx Tim Quan - MSFT