Slashdot Mirror
Documenting a Network?
Philip writes "Three years ago I was appointed as a network manager to a barely functioning MS-based network. Since then I've managed to get it up and running — even thriving — but have been guilty of being too busy with the doing of it to document 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 significant expertise to run. Ultimately, this won't be a good reference for me if they are trying to work out technical details for years to come. It looks like I'm going to have to document the network with all sorts of details that outside consultants could understand too (no, I don't want to be the outside consultant), especially since it's likely that my replacement will have less technical 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?"
That's completely redundant. If it's not the shitty network stack back in the day, it's the malware-ridden security nightmare of the present. Either way, there's no need to waste so many words.
I find your mother to be a good fuck.
Wow. You mean you work for a company that would *pay* you to do that on *their* time without any results seen *immediately*?
The only way I could have possibly initiated such a scramble was to turn in 30 days notice to my employer. Within that 30 days they wanted me to find, hire, and train my successor. Oh, and document everything I ever knew, which they were not willing to pay to have me document before.
Then they started treating me like a slave on my day off about 3 days later. Their documentation read something like "I quit you selfish assholes"
I'm sure the next admin to come in benefited GREATLY from that.