Ritter’s first law of network administration: An administrator at rest tends to stay at rest.
An administrator’s day could easily be consumed with all the little, mundane tasks that are necessary to keep things running smoothly. Backing up servers, reading log files, preparing reports on resource utilization, playing RuneScape—it all really eats into one’s time. That’s why I formulated my first law of network administration. I noted that, as a network admin, when things could pretty much take care of themselves, I could relax and better savor the more fulfilling moments of my job, like reducing a user’s disk quota or reading a user’s more provocative email messages. Here is a short, alliterative list of tips to help you achieve network nirvana:
Locate shared resources that have common security requirements in the same directory structure on your file server. Set access permissions only once on the highest-level directory that these files have in common. Use permission inheritance to ensure consistent security on all the files in the hierarchy.
Don’t assign permissions directly to users. Add users to appropriate groups and assign permissions to the groups. That way, you need only add a user to a group to ensure that all the access they require is properly configured.
Do nothing by hand if possible, because hands can be so error-prone sometimes. Learn a scripting language and write (or download and customize) scripts to perform common, repetitive tasks like reading log files and collecting report data. If you administer a windows network, you must learn PowerShell. It’s available for windows versions from XP onward, and is the “wave of the future.” If you administer a Linux network, you must learn bash. If you manage a mixed environment, I strongly recommend that you learn Python—it’s sufficiently platform-independent and very mature, with a smörgåsbord of cool features built in.
Let your network tell you when there are problems. Install a network monitor system that’s capable of notifying you when your file and email servers run low on disk space, or when your web server stops responding. When you can address an issue before your users even know it’s there, they’ll come to respect your precognitive powers and revere you for the system superhero you really are.
Well, that last one, not really, because they won’t know there was a problem in the first place, right? But hey, we’re geeks: we’re good at fantasy. Now roll a D20 to see whether your invisibility-from-Lumbergh spell worked before he asks for those TPS reports. Again.
Be seeing you.