Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I had to take over the server maintenance, and my first job is documenting the servers especially the ISP, could you guys give me the best practices and guidelines for this task?

And could you suggest a propper way of communicating whit the servers? Right now I have a remote desktop connection with them. Most servers are Windows Server Standard and Window Web Server.

share|improve this question
up vote 2 down vote accepted

Have a look here:

You need to document (in short):

  • Non-Network Information (vendors,authorizers,purpose statement)
  • Network Globals
  • Network Infrastructure
  • Devices
  • Peripherals
  • Software
  • Administrative
  • SLA
  • Diagrams
share|improve this answer

A basic CMDb (Configuration Management Database) should contain at least:

  1. Technical information:

    • Each network interface (IP address, subnet mask, gateway and an uplink/ISP/switchlayer reference)
    • Details about it's software, roles and responsibilities
    • Any special configuration needs (for easier disaster recovery)*
    • Passwords (stored in encrypted fields, and not too easily accessible)
  2. Ownership information:

    • Who owns and ultimately decides the fate of the server
    • Who has the technical responsibility
    • Licensing information
  3. Relationships:

    • References to directly linked network appliance (what switch is it connected to?)
    • Network Diagrams
    • Physical Locations
    • Authentication Hub (Active Directory/RADIUS server/token service/Local SAM)

(*) Get in the habit of thinking in, and describing, best practices for configuring servers and network equipment (and stick to them). That way, all you need to document on a per-server basis is any deviation from these standards

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.