Network Administrator
By Tony Woodall
Part II: Typical Day
Each day starts by checking for new reports of problems or requests from users. These new issues are balanced against existing problems and required tasks to determine a tentative schedule for the day. All issues are prioritized according to their severity. The most critical problems will be addressed first. Simple or quick solutions can be performed as time permits throughout the day or up front if nothing else is urgent.
Much of the day will center on the correcting of the problems experienced by users. New issues will have to be evaluated and merged into the schedule as they arise. However, some tasks must be performed at the start of each day regardless of the problems that are waiting. The previous nightly backup will be examined to determine if it completed successfully. A new backup will be scheduled for tonight. The network hardware and software will be quickly reviewed for proper operation.
Diagnostic lights on hardware can identify a current or potential problem. Monitoring software can be used to provide alerts of actual or potential issues with the network.
Performing some common end user functions on the network can identify proper operation. Sometimes new issues reported by users will be the first indicators of a problem. However, insuring the proper operation of the network will preempt many problems before the users notice them.
As problems are addressed, the solutions will be documented and the users updated. Keeping an open dialogue between the administrator and users is critical to efficiently resolving issues. Follow-up calls will be made to users with recent or reoccurring problems.
The remainder of time in the day will be used to accomplish several items. Periodic changes such as adding or modifying users and network hardware will be scheduled as needed. Time will be set aside for learning about new and existing technologies. Current and future needs of the end users will be identified and goals set to meet these needs.