Moving PAM (Primary Active Manager) using PowerShell

Sometime PAM moves over to a different Server or on a node in DR AD Site, and you wish to move it back to Node in Primary Site, you can follow the below steps to verify the same and then move over the PAM back to a node you wish.
There are different ways to check which node holds the PAM in your DAG, we can check the same using Exchange Management Shell, Failover Cluster Manager, or FailoverClusters Powershell Module.
To check the Same using the Exchange Management Shell run the below command.
Get-DatabaseAvailabilityGroup –Status | FL
Check the Attribute “PrimaryActiveManager” this will show the node holds the PAM role.

The other way is to open the “Failover Cluster Manager”, Once the Cluster Manager is opened, connect to DAG, if you are opening it on the Exchange Sever in the same DAG use the option Cluster on this server.

Node Mentioned on “Current Host Server” is the one Holding the PAM Role.
The Other way is to check it through the Powershell FailoverClusters Module,
Follow the below steps. (Make sure you open Powershell As Administrator)
Import-Module FailoverClusters
You can now run CMD to manage and see the Clusters information.
Run the below CMD to check which Node Holds the  PAM role:
Get-ClusterGroup -Cluster DAG01 | ft –AutoSize
Node Mentioned Under “OwnerNode” for “Cluster Group” is the currently holding the PAM
To Move the PAM to different node run the below CMD.
Move-ClusterGroup -Cluster DAG01 -Node SITEA-MBX2 -Name "Cluster Group"
To check if the move was successful run the below CMD.
Get-ClusterGroup -Cluster DAG01 | ft -AutoSize


  1. Exchange 2019 when setting up DAGs i'm not able to pull the -Cluster name its as if the DAG doesn't exist, is something different in 2019 compared to 2016 when it comes to moving the PAM node?

  2. NutcredOsyngza_Akron William Singleton Crack


Post a Comment