-
❌ Unsupported Exchange Server Recovery Methods
Most Exchange server restore attempts “work” only by luck — but they are never supported. This post explains why snapshot-based, image-based, offline VM, or storage-level restores create state divergence between the recovered server and Active Directory, why this leads to silent corruption (Search, Cluster, IIS, Transport, CUs), and why Setup.exe /RecoverServer is the only supported…
-
🔍 When Search Works “But Doesn’t” in Exchange 2016 DAG
Search reported “Healthy,” but wasn’t working on a DAG node restored from a VM-level backup. The server had been recovered using an unsupported method, which left the Ceres Search Engine in an inconsistent state. The post explains how the issue manifested, why the correct recovery approach is Setup /RecoverServer, and how the customer temporarily repaired…
-
🔐 Why You Cannot “Switch Exchange to LDAPS (636)” — and Why You Don’t Need To
Why Exchange cannot use LDAPS (636) — and why it doesn’t need to. Auditors often require “LDAPS everywhere,” but Exchange relies on LDAP over SASL (Kerberos/NTLM), which already provides encryption and integrity via signing/sealing on ports 389/3268. No plaintext data is ever transmitted. This post explains the architectural reasons, shows packet captures, and provides a…
-
📨 SMTPUTF8 in Mixed Exchange Environments (2019 ⇄ 2016): Why Your Go (gomail) App Fails — and How to Fix It
Mixed Exchange 2019↔2016 can break SMTP submissions from Go/gomail when FE 2019 advertises SMTPUTF8 and the session is proxied to BE 2016 that doesn’t support it. The fix: disable SMTPUTF8 on the 2019 connector, adjust the client, or finish migrating to 2019.
-
🔍 Granting Cross-Forest Mailbox Access: Linked Mailbox or Full Access?
Two forests, one mailbox. Should you just assign Full Access or go with a Linked Mailbox? Here’s the difference, a real-world error we hit, and why linked mailboxes often win for long-term stability.
Available categories:
EWS Free Area 