Philip writes "Three years ago I was prepared as a network manager to a barely working MS-based network. Since then I've managed to get it up and running — even
flourishing — but have been guilty of being too busy with the doing of it to pages the changes and systems that were put in place. Now as I look back, I'm worried that I am the only one who will ever know how this network works. If I get hit by a bus or throw in the towel for any reason, I'd be leaving behind a network that requires some vivid expertise to run. Ultimately, this won't be a good feeler for me if they are trying to work out reflex details for years to come. It looks like I'm going to have to credential the network with all sorts of details that outside consultants could conceive too (no, I don't want to be the outside consultant), especially since it's likely that my surrogate will have less specialized expertise (read 'cheaper'). Are there any good templates out there for documenting networks? Is anyone who has done it before willing to share some experiences? What did you wish your predecessor had written down about a network that you inherited?"

Read more of this story at Slashdot.

More: - Brought to my attention by

Mark