As an IT administrator, have you had your server hang? The mouse might move, but the keyboard doesn’t work?
Or you might be at a blue background, or black screen?
You might be able to press the Caps Locks key and NumLocks key where they light up but that is about it?
You might be able to ping the server but not open UNC shares or a remote Computer Management?
Have you ever wondered what you could do to get root cause analysis?
So if you are used to hitting the power button to ‘recover’ from this situation, you could actually gather data of this hung behavior.
We could generate a manual complete (user mode and kernel mode) memory dump.
How do you do that? Just follow the instructions in one of these articles:
For Windows Server 2008 and Windows Server 2008 R2:
969028 How to generate a kernel or a complete memory dump file in Windows Server 2008
For Windows Server 2003:
972110 How to generate a kernel dump file or a complete memory dump file in Windows Server 2003
Once you get the memory dump, what do you do with it?
Zip the c:\windows\memory.dmp file
And open a case with the Microsoft CSS folks for detailed analysis.
The problem is, you have to have performed these steps BEFORE the system BSODs. It would be much handier if this was enabled by default, and the keypress made slightly more complex.