Tip: Download and manually install rollups and service packs via an administrative command line. Soooo many problems can come from updating these via WSUS or automatic updates. Run these first, then reboot if need be and install the remaining patches. This can save you many hours of heartache. Prerequisites
Patch your servers
Run Exchange Management Shell as administrator.
Put the server into maintenance mode (must be run on the server being placed in maintenance mode):
maintenancewrapper –server <servername> –action start
Run one of the following to verify that the server is in maintenance mode and that the PAM and database have been moved:
This script will give you quite a few stats for the cluster and servers:
This command will list the PAM and any servers in maintenance along with the server containing the mounted database:
get-databaseavailabilitygroup <dagname>-status | fl name,primaryactivemanager,serversinmaintenance;get-mailboxdatabase | fl server,name
Once the server is in maintenance mode and the PAM and database are active on the other server, patch and reboot.
Once patches complete run the following to remove the server from maintenance mode, then verify using the checkpam script:
Stop maintenance mode:
maintenancewrapper –server <servername> –action stop
Run checkpam to get health and status of the DAG:
If the server you want to does not take over as cluster manager, run this command:
cluster <dagname> group “cluster group” /moveto:<servername>
If the database does not activate on the server, follow these steps:
Open the management console
Expand ‘Organization Configuration’
Highlight ‘Mailbox Database number’ in the top pane
Right-click the same database name in the bottom pane and select ‘Activate Database Copy’
Choose the default option of ‘NONE’ and click OK
The cluster file share witness will not come back online
Go to Server Manager → Features → Failover Cluster Manager
In the right hand Actions pane, click on More Actions → Configure Cluster Quorum Settings
Click Next and copy the path to the share, then paste it somewhere for later.
Click Previous and choose Node Majority, then Next and finish
The cluster will then be in Node Majority, meaning that if either server goes down, the cluster is dead and so, too, is the Exchange database. So do not reboot.
Once done, go back into Configure Cluster Quorum Settings and choose Node and File Share Majority
Click Next, paste in the path to the share copied in step 4, click Next and finish
Under Cluster Manager, you should now see 2 shares listed. Highlight the file share that has failed. It should have a red X next to it. Remove this resource.
The cluster should now show healthy. Determine this by running checkpam on either server.
Manually move the active database to another server
Mailbox database won’t move to server
move-activemailboxdatabase -identity ‘mailbox database number’ -activateOnServer <servername> -mountdialoverride ‘none’
This can be accomplished through the Exchange Management Console as well via step #9 above