Hyptohetical - Possible Redundancy...

[Sparky]

Just document it but in saying that it doesn’t really matter.

The amount of networks I have taken on with no documentation whatsoever is a joke. There is a few weeks of pain but after that I can get to a decent level that I can actually start supporting the network before handing it onto the support guys.

[jimmy_2k]

The thought of taking over someone elses network fills me with dread because you never know what little "surprises" your going to uncover!

I have had experiences of this myself so in the end I spent my time researching our systems and creating help guides on our Sharepoint Server. Now we use Wiki which is much better, sadly as I never managed to get off my fixed term contract i'm being made redundant!

[Shinigami]

The way I see it, you should have already made these documents a long time ago. If they're not there, you're a liability to the company.

[Luddym]

Originally Posted by Shinigami

The way I see it, you should have already made these documents a long time ago. If they're not there, you're a liability to the company.

You may have the qualifications, but does that give you the right to say such a sweeping statement without knowing any proper background?

I personally document EVERYTHING in easy to follow instructions, (delusions of being an Author ) as you never know when you aren't going to be around, and vica versa.

By the way, the above quote was mine.

[Shinigami]

I saw your comment mate, my reply was just more pudding on the cake, i.e. if you're employed in an IT position and your job is to design, build and maintain systems, then you would have already made those documents when you initially setup the systems.

The point I was trying to make was that if you haven't done the documents "back then", then most employers should (not necessarily "would") see you as a dangerous asset to their team.

I wasn't talking about you precisely as you have done your work proper, and that's a good thing. Most people however don't realise that by telling themselves they can leave the documentation for a later time, they'll eventually keep pushing it off pretty much for ever (I've seen instances of this on numerous occasions). These type of people are a danger to the company as they alone know some tweak or method by which the system runs. All it takes is an accident (car, household, whatever), and this guy is dead leaving the company with no support and no documentation.

Perhaps my wording was not very clear as I did make a pretty short and blunt initial sentence.

[onoski]

I have recently been asked by my line manager and team leader to document our vpn process in an idiot guide step by step. This also includes steps on creating and sysprep a new image from start to finish all with screen short.

To be honest it didn't bother me too much as I get paid for my time and if they want to get rid of me they can. The bottom line documenting is good practice and professional and does not really matter as no one is indispensable regardless of your years of experience. I'd say get on with it