Discussion on:
View:
Show:
I firmly believe in documentation. I know it can be a real hassle especially when it can slow you down, but it is CRITICAL. I personally document everything I do. All server installs and the apps that go on them are documented. Related client installs are documented as well. Updates/upgrades, security, procedures, everything is documented. In the long run it can relieve quite a bit of stress!
All leading software development companies are now using documentation as a means to control project scope and change management. Whether you're a certified project manager (PMP) and have been through appropriate project management training or a software engineer using the Rational Unified Process or using the Unified Modeling Language (UML) documentation is the key to the effectiveness of these roles...
I agree with everything mentioned here, Everything on the network should be documented, server hardware software details, software installation notes, troubleshooting tips. Over-documenting is the best way to ensure that you have covered everything.
What I have done is to install IIS on my of our IT Dept server, On here I've published a documentation index. This means that no-one has to search for a particular word, excel or PDF file on the network instead everything is provided via a simpleto use web interface. Also this interface can be used on any PC as long as it is on the network. The next step will be to give users limited access to the trouble-shooting section to help them helpthemselves.
Regards,
--
Gary.
What I have done is to install IIS on my of our IT Dept server, On here I've published a documentation index. This means that no-one has to search for a particular word, excel or PDF file on the network instead everything is provided via a simpleto use web interface. Also this interface can be used on any PC as long as it is on the network. The next step will be to give users limited access to the trouble-shooting section to help them helpthemselves.
Regards,
--
Gary.
Does anyone have a good way to maintain physical layout of equipment and cabling?
Visio is nice, but there's no realistic way to show that there's cable path's and junctions and document that this bundle contains these wires from point a to b, etc.
This has been the biggest hurdle for my documentation project. Right now, we have 4 guys that "remember" where and how wires are run when troubleshooting... yeah, that works...
Chuck
Visio is nice, but there's no realistic way to show that there's cable path's and junctions and document that this bundle contains these wires from point a to b, etc.
This has been the biggest hurdle for my documentation project. Right now, we have 4 guys that "remember" where and how wires are run when troubleshooting... yeah, that works...
Chuck
Useing Network Inspektor from Fluke, you are able to find all network components, which you can export to Visio. But Excel is also very good for makeing drawings ( or any other spreadsheet)
Ian Fudge CCAI
Network Teacher
Ian Fudge CCAI
Network Teacher
Does anyone have any great links that offer documentation templates?
I know I am late
but I found some useful resources in www.ittoolkit.com and open.metocube.com
- Keyboard Shortcuts:
- Prev
- Next
- Toggle

































