Database Availability Group Maintenance tasks

In Exchange 2010, we used to use scripts, such as StartDagServerMaintenance.ps1 and StopDagServerMaintenance.ps1, to put a server and get it out of the maintenance mode. In essence, these scripts are used to move all the active databases to another DAG member and mark this server as unavailable.

In Exchange 2013 and 2016, putting a server in maintenance mode will even tell other components, such as Transport or Unified Messaging Call Router, and more, not to send request to that particular server while performing maintenance. This includes moving all the active databases from that server and ensuring that the database doesn't failback during the maintenance. Also, if that server is working as a Primary Active Manager, you need to move the role off the server as well.

Let's understand the role of Active manager before we go any further. On Exchange servers that are members of a DAG, there are two Active Manager Roles Primary Active Manager (PAM...