The essential guide to PowerShell in Exchange

Last updated:March 2015

Editor's note

Microsoft PowerShell is one of the most powerful tools Exchange admins can have in their tool belts. By using the command line, admins can automate a number of tasks and exercise greater control over what end users can access within the organization.

This guide will help admins gain a better understanding of PowerShell in Exchange Server and how to harness the scripting language's potential in multiple iterations of the messaging system. Admins will learn some of the basic skills they should have, cmdlets to use for specific tasks, the best way to approach scripting certain management tasks and more.

1PowerShell in Exchange 2010

The EMS appears again in Exchange 2010, but it includes new capabilities and roles, including role-based access control. As in Exchange 2007, admins can only perform certain tasks from the command line, but PowerShell is still a valuable asset for those who want to create and execute a plan for a successful Exchange 2010 migration. Once an admin has a basic understanding of EMS, there are some additional tools to ease Exchange management and help you prepare for and complete a successful migration to Exchange 2010.

2PowerShell in Exchange 2013

A strong PowerShell background is important for admins to effectively manage an Exchange 2013 deployment, especially since they can't perform a number of tasks -- establishing remote sessions and running commands within commands -- through the GUI. In addition, admins have to adjust to the lack of public folder databases.

Despite these changes, admins can still take full advantage of PowerShell to manage roles and perform routine management tasks. This section explores essential techniques for managing Exchange 2013 and walks through the cmdlets to help monitor the health of servers and diagnose problems with ActiveSync.