10 Networking Commandments
And so it came to pass that these Ten Networking Commandments were handed down from generation to generation, to be worn as frontlets between the computer geeks’ eyes (taped on the bridges of their broken glasses) and written upon their doorposts with Sharpie markers. Obey these commandments, and it shall go well with you, with your users, and with your users’ users.
Back up your hard drive religiously
Prayer is a good thing. But when it comes to protecting the data on your network, nothing beats a well-thought-out schedule of backups followed religiously.
Protect your network from threats
One of the recurring characters on M*A*S*H was Colonel Flagg, who hid in trash cans looking for Communists. That’s not necessarily recommended, but on the other hand, you don’t want to ignore the possibility of getting zapped by a virus, your network being invaded by hackers, or your data being compromised by an unscrupulous user. Make sure that your Internet connection is properly secured with a firewall, and don’t allow any Internet access that circumvents your security.
To counter virus threats, use network-aware antivirus software to ensure that every user on your network has up-to-date virus protection. And teach your users so they know how to avoid those virus threats that manage to sneak past your virus protection.
Keep your network drive current and clean up old files
Don’t wait until your 4TB network drive is down to just 1GB of free space before you think about cleaning it up. Set up a routine schedule for disk housekeeping, where you wade through the files and directories on the network disk to remove old junk.
Don’t mess the network configuration unless you know what you’re doing
Networks are finicky things. After yours is up and running, don’t mess with it unless you know what you’re doing. You may be tempted to log on to your firewall router to see whether you can tweak some of its settings to squeeze another ounce of performance out of it. But unless you know what you’re doing, be careful! (Be especially careful if you think you know what you’re doing. It’s the people who think they know what they’re doing who get themselves into trouble!)
Don’t envy the networks of others
Network envy is a common malady among network managers. If your network users are happy with Windows 8.1, resist the urge to upgrade to Windows 10 unless you have a really good reason. And if you run Windows Server 2012 R2, fantasizing about Windows Server 2016 is a venial sin.
You’re especially susceptible to network envy if you’re a gadget freak. There’s always a better switch to be had or some fancy network-protocol gizmo to lust after. Don’t give in to these base urges! Resist the devil, and he will flee!
Schedule downtime before you begin working on your network
As a courtesy, try to give your users plenty of advance notice before you take down the network to work on it. Obviously, you can’t predict when random problems strike. But if you know you’re going to patch the server on Thursday morning, you earn points if you tell everyone about the inconvenience two days before rather than two minutes before. (You’ll earn even more points if you patch the server Saturday morning.)
Keep an adequate supply of spare parts
There’s no reason that your network should be down for two days just because a cable breaks. Always make sure that you have at least a minimal supply of network spare parts on hand.
Don’t use a program without a license
How would you like it if Inspector Clouseau (from the Pink Panther movies) barged into your office, looked over your shoulder as you ran Excel from a network server, and asked, “Do you have a liesaunce?”
“A liesaunce?” you reply, puzzled.
“Yes. of course, a liesaunce! The law specifically prohibits the playing of a computer program on a network without a proper liesaunce.”
You don’t want to get in trouble with Inspector Clouseau, do you? Then make sure you have the correct licenses for the applications you run on your network.
Train your users to use your network
Don’t blame the users if they don’t know how to use the network. It’s not their fault. If you’re the network administrator, your job is to provide training so the network users know how to use the network.
Keep documentation for your network
Network documentation should be written down. If you cross the River Jordan, who else will know diddly-squat about the network if you don’t write it down somewhere? Write down everything, put it in an official binder labeled Network Bible, and protect the binder as if it were sacred.
Your hope should be that 2,000 years from now, when archeologists are exploring caves in your area, they find your network documentation hidden in a jar and marvel at how meticulously the people of our time recorded their network configurations.