-
⚙️ Exchange monitoring and performance troubleshooting: where to start and why it is difficult
Exchange monitoring is much more than checking CPU, memory, or whether port 443 responds. In this post, we discuss practical monitoring approaches we repeatedly encounter during real-world troubleshooting: baselines, client experience counters, transport signals, dependency monitoring, Managed Availability, and why early weak signals often matter more than obvious outages.
-
🌐 Monitoring Exchange publication through WAP and ADFS: why simple health checks are often insufficient
Monitoring Exchange publication through WAP and ADFS is significantly more complicated than simply checking whether port 443 responds. In this post, we discuss why WAP servers may appear healthy while Exchange publication is already broken, how claims-based authentication complicates health checks, and what should actually be monitored in complex WAP + ADFS publishing scenarios.
-
🔐 Exchange STARTTLS certificate selection: how a new certificate can break SMTP before it is even enabled
During a routine certificate renewal, Exchange may unexpectedly select the new certificate for STARTTLS – even if it hasn’t been assigned to the SMTP service yet. This article explains why it happens and how to avoid TLS negotiation failed with error InvalidHandle.
-
🔐 Exchange STARTTLS certificate selection: why a self-signed certificate may appear unexpectedly
Exchange transport automatically selects certificates for inbound STARTTLS connections — and in some scenarios, a self-signed certificate may be returned unexpectedly instead of a public wildcard certificate. In this post, we discuss how Exchange chooses SMTP certificates, why exact FQDN matches matter, and when explicitly configuring `TlsCertificateName` on Receive Connectors may be the best approach.
Available categories:
EWS Free Area 