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 4 of 4)   Prev   02 | 03 | 04
Thread display: Collapse - | Expand +

All Comments

Collapse -

Details, Details

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

Dont forget VLAN's , Gateways, ETC.

Collapse -

good point

by aaronpctech In reply to Details, Details

Luckily, we arent using any gateways here.

Collapse -

good point

by aaronpctech In reply to Details, Details

Luckily, we arent using any gateways here.

Collapse -

good stuff here's more

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

there is lots of good advice above.

1. automate as much as possible. manual information is just that... manual and is only as good as the people keeping it up. the more people you have the more this becomes a problem.

2. all the items listed in other posts of things to reocord is great. here are a few more.
a. ports - any ports needed open for communication in or out. this is usually helpfull for the wan engineer.
b. responsible admin - person responsible for this machine on the hardware level and on the app level.
c. end of life - if it is leased you want to make sure the lease end date is recored so you know when to start thinkin of replacing or other alternatives.
d. agents installed - list any agents installed on the machine. like management agents
e. backup info - is it being backed up. what is being backed up.


Along with this information you want to keep a change log for each server. This might be electronic or on paper. we keep a binder with tabs for each server. Record every change made to each server. things like reboots, patches, updates, config changes, everything should be listed here and the date it happned. this is very important for troubleshooting problems later on. make it easy to get to or it won't get used.

Collapse -

If the server is not a pizza box type..

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

On a tower model I always open the server and put an envelope containing hardware / bios settings and some general info on name of server, type of usage ect. then I seal it back up that ways if it ever is replaced or lord forbid password lost Its inside the box. Admiitted I ran a small shop and it may not be useful in a large installation. I also do it on my home network as well.

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

Related Discussions

Related Forums