Update October 16, 2026: For more information related to installation of October 2026 updates for Windows Server and the possible impact on Exchange Server, please see Exchange servers may become uns...
Updated Oct 16, 2026
Version 7.0
Blog Post
Restarting the MSExchangeHM service I believe also works. I have set up a custom monitor that queries the total RPC lookups and bounces the service when they exceed 400. So far so good.
Hi, May you tell me which counters are you using ?
It's not a performance monitor counter. The October update added two new global variables to RpcEpMap.dll - saved-context cap and saved-context count. Our custom monitor finds RpcEpMap.dll in svchost and reads both values with ReadProcessMemory. Once it hits 400 (the limit is 512 by default), we bounce the MSExchangeHM service which clears the accumulated RPC lookups. All of this is dependent on the OS version and we've built them for 2016, 2019 and 2025. We're an MSP managing many Exchange servers for our clients. This has worked for every one of them. No need to uninstall the October updates nor changing the registry. I'm sure Microsoft will at some point address the Health Manager service.