Thanks for the detailed post and the FAQ.
After applying the workaround at several customers, two questions kept coming up: Is EpmapSavedContextCap really set on every Exchange server, and was each server rebooted afterwards? And will we notice in time if databases go offline again?
To answer both, I wrote three read-only PowerShell scripts:
- Check-WinOctUpdate.ps1: checks all Exchange servers at once for uptime, the critical 24 to 36 hour window after boot, the EpmapSavedContextCap value, the October update for each Windows Server version (2016 to 2025) and Event 1006 MapiExceptionMdbOffline.
- ExMonitor.ps1: monitors Event 1006, queues, services, database copies and Test-MAPIConnectivity, and sends a mail on problem, on recovery and as a daily heartbeat.
- Register-ExMonitorTask.ps1: sets up ExMonitor as a scheduled task running every 15 minutes as SYSTEM.
The scripts make no changes to the Exchange configuration.
https://github.com/BeatBrunner/PowerShell-Toolbox-Public/tree/main/Exchange/Oct-Win-Update-Check
https://it-blog.bru.ch/2026/10/exchange-nach-den-windows-oktober.html