Not that I've had extensive experience with Windows 2003 Server, I noticed the logging function to specify a reason for a reboot. Let me just say that the ability to say what category a reboot falls in and a description for details is a definite plus. Don't get me wrong, best practices say to log what changes you make to a server and when you make them, but this simplifies some of the process (especially if you have many people doing the work).
At any rate, I'm curious how fully functional the logging is. For example, if I run windows update to apply a security patch, does the prommpt for reboot automatically log this data? If so, VERY cool function. If not, you could still use it by saying no at the prompt then rebooting through normal means. Not as cool, but still useful.
[FIXED] GE Profile Dishwasher Third Rack Not Extending
-
The third rack stopped fully extending in our GE Profile Dishwasher. Learn
the cheap, easy, and sustainable fix!
The post [FIXED] GE Profile Dishwasher T...
2 years ago
1 comment:
It appears the Event log does contain all restart requests. In addition, the updates applied by Windows Update are also logged. The only thing I haven't yet verified is what happens for non-planned restart events. From what I gather, the first person to log in after an unplanned restart is prompted to enter the reason for the restart. My assumption is that the reason is then logged in the Event log. The primary question is how I would tie the fatal error event to the reason I later entered since they could potentially be hours or days apart.
Post a Comment