Hi, all! Existing environment is Exchange 2013 CU13 DAG, two sites, each hosting their own active mailbox databases. HA is managed right now thru DNS round-robin: mail & autodiscover records in DNS point to a server at both sites. Config works perfectly and has been for years.
I'll be setting up a new Exchange 2013 server for the purpose of hosting inactive (but not ready to be deleted) mailboxes and in-place archive mailboxes for our existing infrastructure. I have a couple questions re: the configuration---
First, the new server should not respond to any autodiscover requests. We won't be adding any static DNS records for mail or autodiscover pointers in our DNS, so presumably that should prevent it, correct?
Second, since some of the mailboxes will still need to be logged into (from local OWA or Outlook), do I need to install our SSL cert on that new server? We don't use wildcard certs, so we'll need to regen it, obviously, if installation is required.
Third, I know I need to prevent the other databases from failing over to this server (it's virtual and doesn't have the juice to operate as an online server hosting our current databases). Are there any other settings I need to change to prevent it from behaving as a "normal" DAG member? It's databases need to be able to fail over to the other onsite Ex2013 server, but the databases hosting our active user base cannot fail over to it.
Thoughts and suggestions welcome!
Steve in Reno