System Information, Domain/Network Book Layout

Phant0mKn1ght

Reputable
Jun 16, 2014
3
0
4,510
Hello Everyone,

First time posting in the TH forum, so please omit any errors I make.

I am leaving my job in about 2 months and I wanted to leave behind a book of knowledge I have gathered over my time spent here. I am the IT Specialist (I hold that term loosely, I have no formal training, just hobbyist experience and work experience) Before I go, I want to leave a book for the next guy (or girl) explaining the network map, domain logons, all system information, server information etc. What would be the best way to lay this all out? If I were to do a paper form, what should I start with? Should I even do this (I only have 142 terminals)? Have others done this in the past and if so, what do you think of them? The only reason, I really bring this up, is the guy before me, quit overnight and left NO information, so I walked into it blind, and I don't want to do that to the next person.

Let me know!

-Vince
 
Solution
Always diagram your network and systems. Always have up-to-date documentation.

I'd use Visio to diagram out your network infrastructure and keep it in a shared place for those with a need-to-know access. Then I'd use Excel to document all servers with all information you deem relevant.

humangod

Reputable
Jun 17, 2014
63
0
4,660
Always diagram your network and systems. Always have up-to-date documentation.

I'd use Visio to diagram out your network infrastructure and keep it in a shared place for those with a need-to-know access. Then I'd use Excel to document all servers with all information you deem relevant.
 
Solution