https_443 health monitor incorrectly detects node down

Hi Adam, assuming the monitor send and receive strings have not changed, I would take a packet capture between the BIG-IP and the Exchange server. If you have access to the SSL certificate used on the server, you can use Wireshark to decrypt the monitor traffic and find out what response the server is sending that is causing the monitor to fail.