BACKGROUND IMAGE: iSTOCK/GETTY IMAGES
The essential guide to PowerShell in Exchange
-
Article
Exchange Management Shell basics
Although most administrative tasks can be completed through Exchange's graphical user interface (GUI), the EMS lets admins perform tasks that cannot be completed through the EMC. This feature breaks down the basic syntax of EMS and how to perform common commands. Read Now
-
Article
Using the EMS Filter command to control search results
Commands in EMS can return thousands of search results, making it difficult for admins to find the right information. The Filter command controls the results that are displayed. Read Now
-
Article
Dig deeper into search results with the Format command
The Filter command may not return the exact data admins want. But when used in conjunction with a specific symbol, the Format command adds more control to what information is displayed when a query is executed. Read Now
-
Article
Testing and previewing EMS commands
A single command in the EMS can make drastic changes to an entire Exchange deployment, so admins need to be comfortable using commands. This feature explores how to test and preview EMS commands before executing them. Read Now
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.
-
Article
Complete your Exchange 2010 migration with PowerShell
The next step after prepping the AD for Exchange 2010 is to move public folders, PST data and mailboxes over to the new servers. It's easier to complete these steps using EMS commands rather than the GUI because admins can perform bulk moves with a single line of code. Read Now
-
Article
Establish remote EMS connections with WinRM and PowerShell
Microsoft built EMS on top of PowerShell 2.0 and WinRM in Exchange 2010, allowing admins to perform tasks on remote servers without having to install Exchange tools on local systems. Read Now
-
Article
Set execution policies to protect servers
PowerShell scripts can expose servers to malware, but Exchange 2010 uses execution policies to control whether scripts are allowed to run. Admins can view their execution policy with one simple EMS command. Read Now
-
Article
Is throttling PowerShell in Exchange 2010 a good idea?
Throttling PowerShell can help admins achieve more control over usage and avoid performance problems end users may cause when establishing multiple sessions with the Exchange 2010 server. Read Now
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.
-
Article
Use PowerShell for Exchange 2013 RBAC permissions
RBAC's Management Scopes are useful to admins because they simplify how admins can set up a number of management tasks while also allowing admins to set limits on the kinds of cmdlets end users can access. Read Now
-
Article
PowerShell management techniques for Exchange 2013
Proficiency in PowerShell is important for admins since many management tasks in Exchange 2013 can't be performed through the GUI. This tip looks at the five techniques every admin should have in their toolbox. Read Now
-
Article
New PowerShell cmdlets for Exchange 2013
Of the 187 new PowerShell cmdlets in Exchange 2013, these 10 cmdlets are the ones admins should pay the most attention to. Admins should also be aware that several legacy cmdlets have been retired. Read Now