On November 10, 2026, Microsoft released the November 2026 Security Updates (SUs) for Exchange Server Subscription Edition (SE) and Exchange Server 2019—alongside Windows Server fixes addressing OWA sign-in and mail-flow/outbox queue regressions on on-premises servers.
Patching an Exchange Server SE DAG node without properly entering DAG Maintenance Mode risks stalled transport queues, unmounted mailbox databases, and broken hybrid mail flow. This runbook provides the complete pre-flight, maintenance mode, SU installation, and post-patch verification workflow.
Exchange Server SE DAG Patching Workflow
Step 1: Pre-Flight DAG & Queue Health Check
Run the following in the Exchange Management Shell before placing the target node (EXSE-01) into maintenance:
$Server = "EXSE-01"
$Peer = "EXSE-02.lab365.in"
# Verify all DAG database copies and replication are healthy
Test-ReplicationHealth -Server $Server | Format-Table Check, Result, Error -AutoSize
Get-MailboxDatabaseCopyStatus -Server $Server | Format-Table Name, Status, CopyQueueLength, ReplayQueueLength -AutoSize
Step 2: Put the Exchange Server SE Node Into Maintenance Mode
# 1. Drain HubTransport and redirect queued messages to peer node
Set-ServerComponentState $Server -Component HubTransport -State Draining -Requester Maintenance
Redirect-Message -Server $Server -Target $Peer -Confirm:$false
# 2. Suspend cluster node & block database activation
Suspend-ClusterNode -Name $Server
Set-MailboxServer $Server -DatabaseCopyActivationDisabledAndMoveNow $true
Set-MailboxServer $Server -DatabaseCopyAutoActivationPolicy Blocked
# 3. Move any remaining active databases off the node
Move-ActiveMailboxDatabase -Server $Server -Confirm:$false
# 4. Place all server components offline
Set-ServerComponentState $Server -Component ServerWideOffline -State Inactive -Requester Maintenance
# Confirm queues are drained (MessageCount = 0)
Get-Queue -Server $Server | Format-Table Identity, MessageCount, Status -AutoSize
Step 3: Install the November 2026 Security Update (Elevated CMD)
From an elevated Command Prompt (not PowerShell ISE), run the downloaded .msp package quietly and reboot once complete:
msiexec /update "C:\Updates\ExchangeSE-KB50xxxxx-x64-en.msp" /quiet /l*v "C:\Updates\ExchangeSE-Nov2026-SU.log"
Step 4: Exit Maintenance Mode & Verify Health
After the server reboots, bring EXSE-01 back into production:
Set-ServerComponentState $Server -Component ServerWideOffline -State Active -Requester Maintenance
Resume-ClusterNode -Name $Server
Set-MailboxServer $Server -DatabaseCopyAutoActivationPolicy Unrestricted
Set-MailboxServer $Server -DatabaseCopyActivationDisabledAndMoveNow $false
Set-ServerComponentState $Server -Component HubTransport -State Active -Requester Maintenance
# Verify all components are Active and services are running
Get-ServerComponentState $Server | Format-Table Component, State -AutoSize
Test-ServiceHealth -Server $Server | Select-Object Role, RequiredServicesRunning, ServicesNotRunning
For full in-place upgrade planning from Exchange 2019 to Exchange Server SE, see our Exchange Server SE vs 2019 In-Place Upgrade Runbook.