Every system designed and developed will have an administrator. What is his job? Well, simply put, it is to administer service. To make sure that the systems is running well from every point that he can handle. These include ensuring the users are activated, resources are available, services are running as it should and problems are detected and solved.
System admin is not a magician who can make everything be good and well. If your network is down, that is the Network Admin, the System Admin can’t help you (most times he wont – unless he is also the Network Admin). If you lost your mouse, the System Admin can’t help you.
Who you gonna call?
You forgot your password: contact the system admin.
You can’t access last months sales reports: contact the system admin.
You can’t seem to connect the system server: contact the system admin.
You lost your printed copy of last month’s report: don’t contact the system admin
You lost your cat (it went after the mouse): don’t contact the system admin
Some misconceptions during FYP:
The system admin is not your boss, though he answers to your boss. So it is highly inadvisable to put the boss as the system admin.
The clerical staff cannot be the system admin either (unless they have the required knowledge, though then they may not be the clerical staff in the first place).
System admin’s job scope and capabilities goes beyond just adding and removing users.
MyEndNote: Share your thoughts on this, drop me a line. Always open for conversation (and coffee).
Aside:
Here is a sample of a System Admin job description from a job advertisement for your viewing. Sample: Systems Administrator Job Description
