exchange se
40 TopicsExchange SE Extended Protection
Hello Exchange On Prem admins. As we laugh in the face of service level outages I would like to share some tips and tricks to running Exchange SE in extended protection mode. The most critical component of enabling extended protection on IIS is the DNS namespace and the corresponding SAN that is attached to the certificate therein. Exchange is not entirely namespace aware, so what your clients connect to is not what it uses for internal operations such as eDiscovery through ECP and the Proxy healthset. Here are some tweaks that have made my environment run without errors : When using eDiscovery through the ECP your IIS cert must have the server FQDN in the SAN. When observing the proxy test monitor health sets, they use HTTPS://LocalHost, so localhost must be in the SAN. When configuring IP lock down the Exchange CSS script does not capture all of the applicable IPs that backend IIS operations operate on : Calls are made from the replication network, the user facing interfaces and the hidden 169.254.X.X DAG network. If you are multihomed and using IP restriction in IIS, make sure you include all of these networks, as it seems to choose at random. Stay secure, and stay on prem.37Views0likes0Comments