We’re coming up on two years into our migration off eDirectoy to Active Directory. It was my decision to push UC’s early adoption. We were spending too much money on Novell licenses for the OS and a dedicated GroupWise mailbox, not to mention the hardware.
Now the problem is governance. The campus has a tight small group of dedicated experts working as the technical gods. They’re extremely good forest admins. UC is luck y that we have a guy who is just as good, if not better. Now the campus group knows it. Our guy has been pushing enough on the tech side, and I’ve been gripping enough about protocol and policy that they’ve asked our guy to join their little team. It’s a good move for our guy and great gain for them.
In the coming weeks I plan to put governance back on the AD team’s radar. It’s too important to decentralize in a university as dysfunctional as ours. The way I see it we have to focus on 1) systematizing compliance, 2) centralizing policy vetting and object packaging, 3) developing a reproducible core skill sets for sit admins, and 4) defining a clear path for ongoing management, maintenance and development.
That’s what I’m going to propose. Lofty? Not really. When you consider the consequences of doing nothing (and the path we’re headed down now), they seem like fairly pragmatic and necessary goals.
No comments:
Post a Comment