Keeping Records

Keeping Records

A detailed history of changes to the network serves as a tremendous aid in troubleshooting. When a problem occurs, the first thing you want to know is what has changed, and you can gather this information from a configuration management database.

The following list details some items your configuration records should include:

Descriptions of all hardware, including installation dates, repair histories, configuration details (such as interrupts and addresses), and backup records for each server
A map of the network showing locations of hardware and cabling details
Current copies of workstation configuration files, such as CONFIG.SYS and AUTOEXEC.BAT files
Service agreements and important telephone numbers, such as the numbers of vendors, contractors, and software support lines
Software licenses to ensure that your network operates within the bounds of the license terms
A history of past problems and related solutions