On 7/25/05, Al Mulnick <[EMAIL PROTECTED]> wrote: > The biggest one that comes to mind is to write it with the idea that the > person who reads won't be familiar with the company. By that I mean that you > may want to write WHY vs. what because the next person should know the > technical bits else know where to look, but nobody but you can know why it > was set up that way. I see that as the biggest value you can provide. > > Some daily tasks would be helpful as well I'm sure. > > Al
I'd also drump the configs of the systems so that there is some documentation of all the technical bits that people can refer to. Use tools like ADMAP, GPMC for AD etc. For the cisco gear just grabbing the config files should be good. That technical detail along with a simply written explanation document should be a good start for whoever takes over. Don't over commit yourself on the documentation when leaving as I am sure that if you are the only tech there there will be a lot of little things you'll end up doing to clear your plate before you leave. If they don't have any documentation currently then clear, simple and concise documents along the lines of what Al mentioned will be a great start for them. Phil List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
