We've released a new article that talks about some of the improvements and changes to the Exchange Management Shell in Exchange 2010. Introduced in Exchange 2007, the Shell, which is based on Windo...
Updated Jul 01, 2019
Version 2.0
Blog Post
If you think from an admin point of view that Microsoft is devolving by over-emphasizing PowerHell, then try spending some time in an ISV's shoes that supports an application that has to integrate with Exchange. 5.5 was hard, but not impossible. 2000/2003 had an interface through CDOEXM that could be used to create mailboxes and such and you could extend AD with documented interfaces for context menus and property sheets, which is why you could create one property sheet for a user object in ADU&C. With Exchange 2007, Microsoft ripped the entire guts out of any property sheet integration in AD, plus removed the only API to create or delete a mailbox.
I think the idea of having a general purpose scripting tool is great, IF you want to use it. But have an underlying interface that the scripting tool is using and let developers create applications that can make it better. The end result is better options for customers. I'm one ISV that wonders why I am a 'partner' with Microsoft at all. And I have to pay for this privilege.
I think the idea of having a general purpose scripting tool is great, IF you want to use it. But have an underlying interface that the scripting tool is using and let developers create applications that can make it better. The end result is better options for customers. I'm one ISV that wonders why I am a 'partner' with Microsoft at all. And I have to pay for this privilege.