Documentation

[clareq]

Well the time has come - I can't put it off any longer. Having built a new domain from scratch, and left the tender hands of RM, I really need to document our network. One day I will leave here, and I can't expect anyone to walk in and just know what I've done to make this all work.

 

So, any tips - any easy way to document AD, or all my GPOs? Yes, I know I should have done it as I was going along, but does anyone really do that?

[ReBoot]

If you school uses Office 365 (free for education) one of the Sharepoint template sites is a Wiki. I've started using this to document my network and also store copies of key documents.

 

For documenting GPOs I think you can some of the reports on policy in html format - might be worth looking into if this could be used.

[clareq]

We have on-site Sharepoint, so I'm using that. No use if the school burns down, I know, so I will probably export a copy somewhere at some point.

[TechMonkey]

If you have access to Visio you can create AD maps, if not then look into one of the open source alternatives.

 

I'm always in two minds on documenting GPOs. One, yes it is good to have a record but on the other hand it can be a real pain to keep up to date and document in a readable fashion.

 

Other than that I would go for:

- a network map on differing scales. So an overview that is just what switches connect to what, then a few others to show important info like where APs are or where servers and storage are attached.

- VLAN map of each switch would be helpful to show which ports are on what VLAN (if you have them).

- a building layout showing where network points are and what numbers they are is invaluable if you are new to a network. It also helps if you are able to colour code them so it is easy to see what cabinet a point goes back to geographically.

- helpful reference lists. I keep a station list, where stations are and whether they are staff or student, means I have numbers easily to hand if anyone asks (always impresses). A list of server IPs with info like the IP ranges, gateways, masks etc is helpful and a good reference. A list of printer information (name, make, model, IP, Printer server, location, colour or B&W) can really help as a reference and again means you have numbers instantly to hand.

 

That is what I would call the useful core, anything beyond that is the cherry on the cake.

 

Ohh and as for how. Currently we have an IT Admin share that contains the various Word and Excel sheets that make this up. I also have a Wiki (using MediaWiki) that I am starting to populate with information.

Edited October 27, 2015 by TechMonkey

[clareq]

I am, mainly, the software person - my colleague manages the switches and VLANS, basically all hardware. I'll pass the documentation over to him once I've done my bit, which is basically how it all works - the software, how and why its installed as it it. I've already got a list of servers, their IPs, and roles. I am in the process of going through all the software, how it's installed (SCCM, in image, central server install etc). I then need to explain SCCM and why I've set it up as I have, AD, GPOs, back up strategy and generally how to do anything that needs a mouse rather than a screwdriver.

[ChrisH]

I use One Note synchronised with an Office 365 account. You can then delegate permissions to other users to access it so I have a local copy and one in the cloud. Sensitive information is stored on an encrypted VHD. Edited October 27, 2015 by ChrisH

[IanT]

Documentation is key, here are some of the documents we produce and split into three major sections:

 

Networking, Servers and Systems..........

Firewall Configs, Visio, Manuals

Switching Configs, Visio, Manuals, Port Allocations

Wireless Configs, Visio, Manuals

Telephony Configs, Visio, Manuals

Password Inventory

Server Build Records

IP Schemas

 

etc

[southhamster]

You may find sydi server handy

http://sydiproject.com/

It tries to produce a nice neat document with everything it can find. We run it daily so in case I get deported/abducted/turned into a zombie* there is a good starting point for southhamster V2 to pick up from where I left off.

*Some may think this has already happened...

[sparkeh]

I use Evernote to document the Network, every note is tagged so that if anyone looking at it fresh needs to know about, say, AV, they can click the AV tag to get all the info. I think it works really well. Sensitive stuff is encrypted.

[Geoff]

If you download Microsoft AD Topology Diagrammer it will spit out several Visio diagrams for you.

 

https://www.microsoft.com/en-gb/download/details.aspx?id=13380