Introduction

Microsoft introduced some radical architectural changes in Exchange 2007, including a brand new set of management tools. PowerShell v1, along with an additional set of exchange-specific cmdlets, finally gave administrators an interface that could be used to manage the entire product from a command line shell. This was an interesting move, and at that time the entire graphical management console was built on top of this technology.

The same architecture still existed with Exchange 2010, and PowerShell was even more tightly integrated with this product. Exchange 2010 used PowerShell v2, which relied heavily on its new remoting infrastructure. This provides seamless administrative capabilities from a single seat with Exchange Management Tools, whether your servers are on-premises or in the cloud.

With Exchange 2013, PowerShell v3 is being used and of course, there are many new cmdlets, core functionality changes, and even more integrations with the cloud services. Approximately 150...