If you’ve been following PowerShell, you know that a major pain point has been the pretty lackluster support for AD management. In fact, if it weren’t for Quest’s PowerShell cmdlets, I’d never use the shell for AD management.
But no more! We’ve been informed that the AD team is working on a set of cmdlets for managing AD. And they’re doing it the RIGHT WAY, meaning the cmdlets will expose all of AD’s management functionality (eventually – they’re still in the pretty early stages of development). The AD management GUI that goes with this will be built on top of the PowerShell cmdlets – a la Exchange 2007, System Center Virtual Machine Manager, etc. GOOD JOB AD GUYS!
Now – when do we get it? I dunno. Honestly, everything we see at the MVP Summit is super-secret and covered by nondisclosure agreements; I specifically asked for permission to share this tidbit with you so that you know the AD team "gets it" and is moving forward on the path of righteousness. But they wouldn’t even tell us when this stuff would ship. So, it might be something we get out-of-band, or something we get with the next version of Windows Server whenever that is. Who knows? Nobody knows. Or at least they’re not telling.
But now we know that AD *will* be PowerShell-manageable, and that, folks, is a GREAT thing. Kudos to the AD team for making this investment.
And, BTW, they’ve independently discovered something I think every Microsoft team discovers when they start building on PowerShell: The shell forces them to think like admins. They think about the user experience first: What are the bits I need to manage? What can I do with those things? In other words – what are my nouns, and what are my verbs? This creates a VERY admin-friendly set of cmdlets that align directly to the day-to-day tasks you have to perform in AD.
GOOD JOB, AD TEAM!