General discussion

Locked

Best Practice For Documenting a Server

By aaronpctech ·
You guys are so great with helping me out along my way to becoming a great Admin. I have another question tat might seem dumb, but I want to know the right way.

I am in the process of documenting different things on my network and I have came down to the Servers.

What are some key things I should document about these servers. SO far I am thinking the obvious: ipconfig settings, which are domain controllers, what applications are on each....

What else should I look for and/or pay close attention to.

Any and all of your opinions are greatly appreciated.

This conversation is currently closed to new comments.

35 total posts (Page 1 of 4)   01 | 02 | 03 | 04   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

A little note...

by ccthompson In reply to Best Practice For Docume ...

You kind of already said this, but maybe just a deeper dig into it. Applications running on the server, maybe also map out which services are needed for each application, if they are a manual or automatic startup and what they depend on to startup. Usually when i have a problem with exchange server 2003, it turns out to be a service got hung on starting, or didnt start properly. Knowing which services are needed are sometimes critical.

Hope this helps!

Collapse -

A little note...

by ccthompson In reply to Best Practice For Docume ...

You kind of already said this, but maybe just a deeper dig into it. Applications running on the server, maybe also map out which services are needed for each application, if they are a manual or automatic startup and what they depend on to startup. Usually when i have a problem with exchange server 2003, it turns out to be a service got hung on starting, or didnt start properly. Knowing which services are needed are sometimes critical.

Hope this helps!

Collapse -
by gary In reply to Best Practice For Docume ...

Download the PSTools kit (it's free).

This will allow you to list out things like services, Installed software, Patch levels and a whole other bunch of stuff. May not be everything you want for documentation but it goes a long way.

There was also a server documentation template on here somewhere....

Collapse -

Little Bits of Info

by MsIT In reply to http://www.sysinternals.c ...

I have a Server spreadsheet which includes the Mfg, Model#, Serial#, MAC Address, IP Address, Speed,RAM, Function, and OS w/sp. If it's a large organization, the Dept Administrator would also be helpful. Hopes this helps.

Collapse -

Great Great Tips

by aaronpctech In reply to Best Practice For Docume ...

Damn you guys give some good info. I will definitely consider all of these. I would like to try those tools suggested by gary just to get the basics down.

If there are any more tips I am all ears. I will begin your suggestions 1st thing tommorrow morning.

Collapse -

Documentation of Servers

by markguer In reply to Great Great Tips

All of the things listed so far are invaluable to have around when preparing for disaster recovery of a server.

I would recommend creating a manilla folder that you keep OFFSITE for each server on your network.

It woulds contain a printed spreadsheet that outlines ipconfig, share info, RAID controller version and configuration, configuration of hard drive partitions, amt of RAM, OS service pack level, applications installed, tech support numbers of those applications, serial numbers of applications, copies of installation media for the applications installed, copies of installation media for OS, things like SQL, Exchange, etc., cd-rom key codes for apps and OS

Make a list of the things you would need to rebuild the servers from scratch. That is what you should have included in your documentation.

Hope this helps..
--Mark

Collapse -

Great Great Tips

by aaronpctech In reply to Best Practice For Docume ...

Damn you guys give some good info. I will definitely consider all of these. I would like to try those tools suggested by gary just to get the basics down.

If there are any more tips I am all ears. I will begin your suggestions 1st thing tommorrow morning.

Collapse -

Also.....

by gadgetgirl In reply to Best Practice For Docume ...

make note on the paperwork of the date and time of the last patch. Why? So you know (definitively) that that particular server has been patched, and if doing a full restore after the patch has screwed, you know where to stop the restore....

oh, and keep a copy of your server documentation in your DR crashbox along with your installation discs.

Date and time of last patch also makes sure that the server documentation is regularly updated, and not just left to sit and fester for years when you've moved onward and upward....!!

GG

Collapse -

DR Crashbox

by aaronpctech In reply to Also.....

Ok, I feel really stupid right now, but if I dont ask, I wont know. What is a DR crashbox???

Collapse -

sorry, that may be a cultural difference!

by gadgetgirl In reply to DR Crashbox

because I'm in the UK!

A DR Crashbox is a box (obviously!) in which you need to store all the necessities to initiate Disaster Recovery (DR)

I've just redone the list for where I work: it contains the minimum items which should be kept both onsite in the server room, and in the general ICT area. (yes, 2 boxes, but only because there is half a mile difference between those locations!)

As examples: first aid kit (racks cut!) paper, pens, spare cell phone and batteries, with charger, tool kit, spare discs where possible, emergency contact sheet, SERVER CONFIG SHEETS, install discs, spare CD writer, blank discs, spare back up tape drive, spare USB hub and that's only part of it....

I think you'll get the idea now - sorry if I caused any confusion, I keep forgetting the difference in terms!

GG

Back to IT Employment Forum
35 total posts (Page 1 of 4)   01 | 02 | 03 | 04   Next

Related Discussions

Related Forums