-
-
User access documentation must be prepared. Many network administrators ignore network documentation. Reasons? “I don’t have time”, “I know its useful, but I don’t know how to do that”, “Other people should do that”. Practically there are no networks that work flawless. Errors could have different causes and could appear any time. You don’t want to reach the point where you cannot sleep because you don’t understand how to solve a problem and users need to work with no delays.
Remember the following when creating access documentation;
Work out the format. If you want to create yourself a network documentation from scratch you probably understand the necessity and usability. You need to establish the format in which you will store the documentation and other aspects such as people who will work and access and update it. Most organisations have a set format for completing user documents.
Think what information you need to collect in that documentation; suggestions could be: number of physical locations (where your company works), how those locations are connected (wireless, wired), number of routers, switches, firewalls, servers in each location (with passwords, types of operating systems, update management, types of hardware, types of RAID, period of guarantee offered by vendors for hardware and software, rules in firewall), a contact list with people responsible with administration, help desk, a contact list with companies that offers support for hardware and software, documented and tested procedures for disaster / recovery scenarios, places to store backups (on site and off site), procedures for trial restores. You must understand how your network works in order to establish what information you will need to help you when trouble arise.
-
Leave a Reply
You must be logged in to post a comment.