Moving Primary Active Manager (PAM) using PowerShell

Share this:

In Exchange Server 2013/2010 the Primary Active Manager (PAM) role is the responsible to manage the high availability of Exchange.  When we have a DAG a server can be the PAM (only one per DAG) or SAM (Standby Active Manager). In some situations the administrator may be asked to move the role, and that is the goal for Today’s Tutorial.


The first step is to check the current DAGs that we have within the Exchange Organization, and that can be done easily using the following cmdlet:


In order to identify the PAM (Primary Active Manager), the following cmdlet can be used:

Get-DatabaseAvailabilityGroup –Status | Select Name,Primary*


The process to move is based on the Failover Cluster management tools, and we can use either cluster.exe utility or PowerShell cmdlets. Logged on the server that has the Failover Cluster installed (any member of the DAG), we can right-click on PowerShell and then click on Import System Modules, and that will expose the Failover cmdlets to the administrator.


If you have already open the PowerShell as administrator, we can run the following cmdlet to load all modules, and that will include the Failover cmdlets as well.



Now that we have the cmdlets available, our first step is to identify the current status and who is the owner of the Cluster Group resource.

Get-ClusterGroup | ft –AutoSize


In order to move, we just need to run the following cmdlet:

Move-ClusterGroup –Name “Cluster Group” –Node <any-Mailbox-server-of-the-dag>


Those are the steps to check to identify the current PAM using either Exchange Management Shell and Powershell, and then using PowerShell we move the Cluster Group to another node, and by that we move the PAM.

Written by Anderson Patricio

Anderson Patricio is a Canadian Exchange Server MVP and MCSM (Solutions Master) and he contributes to the Microsoft Community with articles, tutorials, blog posts, forums and book reviews. He is a regular contributor at, and (Portuguese).