|
Document It Please!
|
|
|
|
Monday, 10 December 2007 04:03
|
Hello everyone, sorry I haven't blogged in a while, I've still been busy with a couple other sites and my new job. Seems all the servers at my new job are mostly Active Directory Machines with Exchange Servers. Being an Open Source guy I've had to once again kind of switch over my thinking and troubleshooting techniques. Although it seems Windows Issues are lot easier to solve but boy are there a lot! From little technical issues with email's and spam filters, to cpu crashing and blue screens. Most of the issues are network related issues and a simple reboot can fix almost all of them. But what's the most frustrating is coming into a situation with absolutely no documentation. Documentation is hard to find for the majority of the networks I work on, and it's starting to get annoying.
In many cases this is both the fault of the customer and the vendor / consultant who designed and implemented the network. The vendor either never gets around to it and the customer does not request it. In some cases, technology consultants do not feel it's important enough or want to lock the customer into having to call "them" if something goes wrong or a configuration needs to be changed.
What happens in case of an emergency? Is there a Disaster Recovery Plan for a Weather Emergency? How about if Mr. Trusty Server takes a crap and you need a set of codes to turn off an alarm or access a server room? These are very important questions and need to addressed and ready in every business or orginization with any type of I.T. Infrastructure.
Here's some rules of thumb I go by.
5. It's a necessary component of a proper site survey
Site surveys are fundamental tools for those who deploy networks. The ultimate goal of a site survey is to provide enough information to determine the number and placement of access points, routers, switches, etc. that afford sufficient coverage throughout the building. Before a proper site survey can be performed however, some type of floor plan is necessary. This may come from a set of building blueprints or, if no blueprints are available, a floor plan drawing that depicts the location of walls, walkways, and other relevant information. At a minimum, the planned location of network equipment should be documented on the floor plan or building blueprint. By doing this, you ensure that you have completed a thorough site survey and have taken the first step to documenting your configuration.
4. The Core of Change Management
There is an old axiom that states that you must know where you are before you can know where you are going. Transferring this notion to the topic of wireless networks, it tells us that before changes are made, the current configuration should be documented. This is very important considering that change is inevitable in our field, and within the wireless arena, the field is changing even faster. Yesterday it was 802.11b, today 802.11g, and, tomorrow, who knows? If it's not the access points that are changing, it's the security level and configuration. The initial documentation you created during your wireless site survey can serve as a reference point or baseline for the changes sure to come along.
3. Aids in Transfer of Knowledge
How many times have you come to a new organization, as either a new IT employee or a consultant, and found that there was not sufficient documentation to get you up to speed on what you needed to know concerning the existing configuration? If you have been on the receiving end of this exchange then you understand the importance of having proper documentation. Some hesitate documenting their configuration, thinking that possessing the knowledge in their head will make it harder to replace them. On the contrary, documenting your network can actually make you more "promotable" by ensuring that decision-makers know an easy hand-off can be made in the event someone has to take over your old position.
2. One of your Best Troubleshooting Tools
Probably one of the most obvious reasons to document your network is to aid in troubleshooting. Having information readily accessible in the event of problems about access point types and locations, IP addresses, WEP settings, client configuration, channels, etc., can't be over emphasized. In the event that you have to get others involved to help with the real sticky problems, the benefit of an easier transfer of knowledge applies here as well. If permanent changes are made to your wireless network because of the ensuing corrective action, do not forget about change management, and document the modifications.
1. Shows your are an I.T. Professional
The top reason to document your network is not a technical one. Webster defines professionalism as "the standing, practice, or methods of a professional, as distinguished from those of an amateur." By following the practice of documenting your network, you are showing that you are indeed an IT Professional.
Don't forget that, as it is in most situations, the key to documentation is to do it early, often, and precisely. Now that you have been reminded of the importance of documenting your network, it is up to you to ensure that the job gets done.
If these simple steps are taken into an account with every one of your clients and or workplaces, then you will have no problem taking care of issues quickly and efficiently.
|
|
|
Claimed my Prize At Alledia.com
|
|
|
|
Thursday, 11 October 2007 14:58
|
 SO I've just claimed my prize over at Alledia.com. They have a great book that I've just won called the Joomla SEO eBook. I can't wait to get it and give it a read. These guys have pimped out a lot of sites and are very creative. Give a look at their site and join the syndicate if you can!
|
|
New Theme coming to NoNeck
|
|
|
|
Monday, 08 October 2007 09:14
|
|
While this blog is still new I'm still playing with templates. Some say not to mess to your site too much and I try not to, but as my blog grows there's changes that need to occur. If I have extra time I will try and make this blog more readable and more aesthetic. I've been working on a new template and am going to put it up sooner or later today, probably after my Bitnami post. Anyway, let me know what you think about the new theme in your comments.
|
|
Microsoft Surface Parody
|
|
|
|
Friday, 05 October 2007 16:20
|
|
Check out this parody video of the Microsoft Surface
|
|
Married in Vegas!
|
|
|
|
Friday, 28 September 2007 20:30
|
 I know it's been a week since my last post, but I got Married in Vegas! So many things to talk about, I don't actually have the energy to talk about. The ceremony was beautiful, yet the overall trip lacked some organization (my bad) and some cooperation (family's bad). I must forget the bad stuff, it is my Wedding and nothing else needs to be remembered, except for the fact that the ceremony was awesome and most of the family was together in the same room. Thank you all who attended, and get ready for the Anniversary next year! I will posting pictures into a gallery that I'll have up towards the middle of the month, lot's to work on! Chat at ya later!
|
|
|
<< Start < Prev 1 2 Next > End >>
|
|
Page 1 of 2
|
Home 