Monday, February 11, 2008

Is ignorance worth the bliss?

I currently administer an Active Directory domain, and am learning how to via on-the-job training. This usually works really well for me, but I've discovered group policy objects, organizational units, and login scripts... which all make administering the network much easier.

Imagine.... I can write a GPO to install software that will report back all of the software and hardware settings of each computer within an organizational unit... and I can look in a single window and see a list of all the computers on my network along with a brief description of each.

Unfortunately, this means that when someone decides to purchase non-standard hardware/software, I now know what I'm missing... I know that the new iMac won't identify properly on the network. OS X Leopard did add on an official "Active Directory" feature in the Directory Utility, whose sole purpose in life, apparently, is to prevent the computer from binding to an Active Directory Domain. So the fact that I knew Tiger could bind to AD makes Leopard even worse.

Now, the question I'm presented with is whether or not ignorance is worth the bliss.

Should I stop learning all the amazing things we could do with our resources, knowing that we will slowly be migrating to equipment that lack these features? Would it be better to throw in the towel for everyone, or attempt to manage 2 networks. I would imagine that the "fun" and trendy network with no rules and shiny animations would beat out the boring network that is managed and secure.

On a scale of "Bad=> OK => Best" if "Best" isn't even an option, would it be better to be ignorant of all the "Best" methods and benefits?

This situation brings up a lot of frustration which breeds bitterness. Bitterness is sin. In order to have a positive attitude about it, I only see two options; 1: be ignorant of what we could do and be happy with mediocrity, or 2: find another job.

The next problem is, are there any jobs that don't enforce mediocrity? Previous experience indicates that at most companies the non-technical staff make decisions (in an effort to add cool and useful features) that prevent company-wide coolness and usefulness. Most IT staff will look at that, laugh at the irony, and check their monster.com account for any leads.

I think I'll stick with where I am, and just pray that God will get rid of my bitterness. Now I just need to make sure this feeling of defeat isn't sinful as well.

1 comment:

Anonymous said...

117 - Nangra here.

This post completely summarizes what I've been feeling lately!! It's so frustrating to learn of better ways to run the network, only to be shot down by the leadership or futility.