Is your network documented ?

[kestrel1]

@kestrel1: As they say... it's the thought that counts

This is very true. However, I have actually started to document some of the things that could be useful, IP addresses etc, on the task management system that I recently setup. Only started today though, so could take a while to complete. I will probably do a hard copy when I get five minutes (hmmm, let me think, when was the last time I had five minutes) Oh well, it will get done some time.

I wish I had a larger team here, well one technician would help I suppose, especially when the sixth form extension is completed.

I have nightmares now, god knows what it will be like with another 80 or so machines on the network.

Hay ho, get on with it & stop complaining.

[Minkus]

I think the best thing to do if you've got nothing is to start NOW. If you're installing a new server, document how and why you did it.

 

Then next time you start fiddling with something slightly older, make part of the job documenting what's there already.

 

Try to fill in the gaps in spare time at the end of the day & odd moments (like if you're waiting for a large file to download, or for someone to ring you back).

 

I find documentation is best done 'on the job' - if you try to do it all in one go, it just becomes a mammoth task that never gets completed.

[kestrel1]

Yes, totally agree. So I will be doing it in small chunks. I think I have just got lazy in my old age & when you don't have enough time things tend to slip.

[blackcat]

Absolutely right. The job's not done until the paperwork is complete. Well that's what I was told. Things just happen so fast in IT, that to document every change is very onerous. Personally, it's not my job, but when I've asked what a setting should be, I've got three different answers.

[DSapseid]

After reading this yesterday i started it yesterday afternoon and even took my laptop home to do some more on it. I have so far done about a third of what i want to include in it, but im sure i will add more as i write it. Its currently on 17 pages!

 

I am going to just do a hour or so a day until its done, ive got the technician fielding all the stupid requests about passwords and printers and i just do the major probs or when im bored i will take one of the small ones up the other end of the school for a break.

[plexer]

On top of this maybe the wiki when it returns or as part of this topic we could put together a list of the information that we all deem to be crtitical to document.

 

Sort of a template for use really.

 

Ben

[kestrel1]

On top of this maybe the wiki when it returns or as part of this topic we could put together a list of the information that we all deem to be crtitical to document.

 

Sort of a template for use really.

 

Ben

 

The list of information could be very useful. There is so much that could be documented, but where do you stop?

[OutLawTorn]

I work for a company that gets contracted in to multiple schools. I am one of ~6-7 technicians varying between "1st" and "2nd" level roles, however the documentation at some of the schools is lacking yet others is really thorough. As each school uses an intranet system that our company has developed, part of that is an IT support section (manage job request queue, etc) that has a section for documentation. We are slowly working at developing a standard school outline, with all the basics (servers, network, ip addresses, id card printing processes, etc). Generally the same technicians are at the same schools, but we are working to a point where any one of us can walk into a school and know what is where relatively effortlessly.

 

Its ASP based. If anyone is interested, i can send them the documentation templates that we've got so far. We're still working on it, and there are some sections that are a bit more school-specific than others but most of its pretty general.

[GrumbleDook]

This sounds good. The wiki is live if you want to access to add the templates there. Please pm Ric_ for more info on access to the wiki.

[Pottsey]

“What if you are off ill long-term, or (heaven forbid) get hit by a bus? The school would need adequate documentation to be able to continue working.”

My IT Co-ordination has all the major passwords; my PDA contains all the minor passwords. One reason I never did a full documentation is we are a small school and it’s pretty easy for anyone to figure out the network. We have 1 server, 1 cabinet, 1 domain.

 

I figure any decent IT tech with the passwords could figure out how our system works. We do have a document on IP range and how it works. But no map of network switch’s e.c.t

 

It all comes down to the size of the school. If it’s a massive secondary school I can see the need to map out the network. The smaller the school the less need of a map.

[blackcat]

I suppose desktop images and laptop images would need recording too. I did this as a simple (yeh right) document and it makes support so much easier, especially if a piece of software is installed in one part of the school/college but not everywhere and you didn't know. It's easier for new members of a team to see how it all hangs together too. I look forward to any templates being posted.

[projector1]

this morning i had to print off the passwords doc just in case the server went down. Placed a copy in the safe!

Documenting does help make life easier, this morning i was carrying out a wifi scan and as it reports mac addresses, i can tally them up with the access point inventory (which has all the mac addresses recorded too)