Exchange 2016 Patching Checklist – AR/ACG Fleet(To minimize risk of Exchange Server failures after applying SU/HU updates)

Exchange 2016 Patching Checklist – AR/ACG Fleet

(To minimize risk of Exchange Server failures after applying SU/HU updates)

A. Pre-Patch Preparations

1. Place the server in HBSS relaxed mode
2. Log in to MB using the shipname.exchange service account to install Exchange Specific updates.
   (Do not use IAADMIN or DOD_ADMIN accounts.)
3. Inform shipboard users to avoid accessing email during the patching window.
4. Verify a successful system and database backup is available.
5. OPTIONAL : Check database integrity to make sure not in dirty shutdown state. If it is, perform soft recovery using ESEUTIL switches.

B. Maintenance & Installation

1. Place the Exchange server into maintenance mode

(FROM EXCH MGMT SHELL)

• Set-ServerComponentState  “SHIP-MB-002”  -Component  HubTransport  -State  Inactive  -Requester Maintenance
  
  
• Set-ServerComponentState  “SHIP-MB-002”  -Component  ServerWideOffline  -State  Inactive  -Requester  Maintenance

# To verify Server is in  Maintenance Mode

• Get-ServerComponentState  “SHIP-MB-002”  |  ft  Component,  State

# Expect most components INACTIVE; ‘Monitoring’ and ‘RecoveryActionsEnabled’ typically remain Active.

2. Apply the KB update using an elevated Command Prompt. (Do NOT launch the installer from Windows File Explorer GUI.

3.First Reboot – Restart the server after patch installation.

C. Post-Patch Validation

1. Take the Exchange server out of maintenance mode.

• Set-ServerComponentState  “SHIP-MB-002”  -Component  ServerWideOffline  -State  Active -Requester Maintenance
  
  
• Set-ServerComponentState  “SHIP-MB-002”  -Component  HubTransport  -State  Active -Requester  Maintenance

# To verify Server has exited from  Maintenance Mode

• Get-ServerComponentState  “SHIP-MB-002”  |  Component,  State

# Expect most components are showing ACTIVE; except couple of then remain InActive.

2. Second Reboot – Perform a clean reboot to confirm stability.

3. Patch Verification  – KB update shows as installed . Exchange build number matches the expected CU/SU version

• Get-ExchangeServer  |  fl  Name,  Edition,  AdminDisplayVersion

4. OP TEST Mail flow check (send/receive internal and external test messages)., OWA/ECP accessibility., Database status check (mounted and healthy)., Event logs review for critical errors.

D. NOTES FOR ACGV3

1. Patch one server at a time.

2. Move the database over to the second MB before patching the first MB. (vice versa)