How Do You Handle Your Enterprise Documentation?
An anonymous reader wonders: "I'm curious as to what tools Slashdot readers use to inventory and document their networks? What got me thinking about this is the part VMWare has been taking in data centers. You've got your SAN, various physical and logical networks, various VMs, and so forth. It just adds a new layer of complexity in terms of documentation. I'm curious as to what people have been using as for doing things like documenting how their backups work, LAN settings, FW settings, where and what runs what services, and so forth. How do you blueprint your entire IT infrastructure so that someone brand new could start and figure out what does what?"
Word+visio.
Of course the person creating the drawings and documents must be proficient in technical writing (aka not an idiot), because no matter what tools you have, if you don't know how to explain things, they'll be useless. Try to get your documentation peer reviewed to make sure it makes sense.
Another deficiency is that MediaWiki doesn't support image map. Sometimes the best way to find info is to click on the picture....
"The most sensible request of government we make is not, "Do something!" But "Quit it!"
http://www.80-20.com/products/document_records_man agement.asp
Its very much enterprise level.
The inane comments here make my wonder if any of you have a job at all.