Hi forgive,
Thank you for your question.
We could refer to the following steps to install Window update on Exchange DAG member:
1) Perform server Switchover so that the server you are installing the updates on is not active: Move-ActiveMailboxDatabase Server ExchangeServerYouAreUpdating
After each switchover perform the following command to make sure the DBs are healthy and see which server is the active server:
Get-MailboxDatabaseCopyStatus *
Note: sometimes after a reboot it can take a few minutes for things to return to a healthy state. The output of Get-MailboxDatabaseCopyStatus may also get index errors.
2) On the Exchange Server that is not active for the databases: Open the yellow-shield Windows Update icon, review the updates, confirm that no Exchange Update Rollups or Exchange patches are selected. If they are, exclude them. Exchange patches should not
be applied through Windows Update on DAG member Exchange servers. Once the updates are applied, reboot the Exchange server.
3) Once the first server is rebooted and back online from the updates and we have checked the db replication health (Get-MailboxDatabaseCopyStatus *), repeat the steps 1 and 2 on the next server.
Note: Avoid having more one exchange server offline at a time.
Do i configure/use cluster aware updating snap-in?
A: if we configure the cluster aware depend on yourself, in my solution, I didnt use CAU.
If i use CAU, does it matter in what order i apply the updates (active copy vs. passive copy)?
A: yes, we should apply the update on passive copy.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim