Windows Server 2003 provides a wealth of options that enable administrators the flexibility necessary to manage servers in a distributed IT environment through remote administration tools and techniques. Although some tools are really just enhancements of technologies introduced in earlier operating systems, there are many new features that make Windows Server 2003 a compelling alternative and worthwhile investment in terms of both manageability and security. Administrators can now remotely attach to servers without a network connection, keyboard, mouse, or video adapter to troubleshoot and bring the server back online without making expensive and
Chapter 9. Maintenance Practices and Procedures
In this Chapter
After the network operating system is installed and users are able to use the network on a daily basis, the job of the network administrator is not over. Although Windows 2003 is a very stable and resilient operating system, it won't perform ongoing maintenance and ongoing support on its own. To maintain a reliable network system, proper maintenance must be
This chapter will explore best practices in system maintenance and provide step-by-step recommendations what can be done to implement an effectively
Maintenance is not as Interesting as Implementing New Technology
Although maintaining a network is not as interesting as implementing new technologies, finding out that the Active Directory is corrupted and that
What to Do Every Day
IT professionals know better than
Ensuring that Maintenance Tasks are Completed Regularly
Ensuring that maintenance tasks are completed regularly is critical to the stability of a network. When possible, distribute maintenance tasks throughout your IT staff in the areas of their expertise. This way there are qualified personnel doing the maintenance tasks and they don't feel as though their entire job is maintenance. Ensure that the people performing the maintenance tasks are following the written procedures to the letter. Have them sign off on the task on a checklist so that both employee and management can be sure the task was completed.
Read the Logs
The Event Viewer is the first thing you should monitor and review. The event logs keep track of critical events that can be telltale signs of system problems, and you should be in the habit of checking the event logs each and every day. This is
Checking on System Resources
Being aware of the available resources on all systems serves several purposes. Not only can reviewing resources
Any Event in the Event Viewer
For any event in the Event Viewer there will be a link that often leads to further insight on the issue and possibly a specific resolution.
For more information, go to the Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Other helpful locations include Microsoft TechNet support at http://www.microsoft.com/technet, or Microsoft Support at http://support.microsoft.com.
Another resource for information on events is to perform a search on the Event ID on a search engine and possibly find useful information from someone who has
Although it might seem redundant to check multiple resources for information, commonly the problem resolution is noted in one site that is not noted in another site. So using multiple resources can frequently identify problems that might
If You See That Something Is Amiss
If you see that something is amiss with system resources, don't just take it at face value. Although it is easy to look at a drive that holds the logs and determine that the drive is full and just delete files, you might want to investigate why the tape backup software is not deleting log files after a successful backup. If the backup software is supposed to be clearing log files after the system is successfully backed up, could the system possibly not be