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.
1Scripting in Exchange 2007-
PowerShell in Exchange 2007
The Exchange Management Shell (EMS), which was introduced in Exchange 2007, was built on top of PowerShell and allows admins to manage every aspect of the server from the command line. The EMS can perform any task normally performed in the Exchange Management Console (EMC), including enabling new accounts and configuring properties to automate certain managerial tasks. This section can help admins learn the basics of using EMS as well as helpful commands for common tasks such as controlling search results and generating HTML reports.
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. Continue Reading
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. Continue Reading
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. Continue Reading
With a basic understanding of EMS under their belts, admins can learn how to use the Set command to create a list of blocked mail senders and recipients. Continue Reading
Active Directory (AD) requests can overload domain controllers, but this cmdlet can help lessen workloads and protect DCs from additional stress. This feature explains the parameters that the command can be used in conjunction with to control which DCs Exchange Server uses. Continue Reading
2Scripting in Exchange 2010-
PowerShell 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.
Before migrating to Exchange Server 2010, the AD setup must meet certain prerequisites. These PowerShell cmdlets will help verify that everything is in working order and prepare the AD forest for the move. Continue Reading
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. Continue Reading
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. Continue Reading
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. Continue Reading
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
3Scripting in Exchange 2013-
PowerShell 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.
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. Continue Reading
4Must-know PowerShell terms-
Essential terms for PowerShell in Exchange
To master PowerShell in Exchange, admins must have a firm grasp on more than just the technology surrounding the scripting language -- they must also know the terminology. Here are some of the essential terms admins should know to better understand how PowerShell fits in to Exchange Server.
- Active Directory
- domain controller (DC)
- graphical user interface (GUI)
- Microsoft Exchange Server 2010
- Microsoft Exchange Server 2013