Exchange Autodiscover Cert Question

Hi,

On Exchange 2010/2013, what's the best way of handling adding additional domains to the server so that certain users can have different primary email addresses.

Specifically the problem I have is that external users using Outlook Anywhere will get a security alert pop-up whenever they open up Outlook that "autodiscover.new2nddomain.com" is not valid or doesn't match the name of the site. You can just click Yes to proceed and it will work. I have a public CNAME record that points the above to the autodiscover domain that is on the SAN Certificate "autodiscover.primarydomain.com".

I know one way of doing it is just add that new domain to the SAN certificate. But that's kind of a nuisance if you have to do that every time you want to add a domain to your exchange environment.

Hosted Exchange Providers (like Intermedia, Godaddy, Office365) must get around this somehow as they have 1000s of domains of their 1000s of users and they just tell you to create a CNAME "autodiscover.domain.com" that points to their specific autodiscover FQDN. Out of the 20 or so companies I have on hosted exchange providers, I've never seen a certificate error, only some initial warning when setting up the account about some redirect and then it never comes up again.

I found some articles about deleting your CNAME for autodiscover and creating an SRV record. This seems plausible. However, hosted providers make you just create that CNAME.

I did an Exchange autodiscover test on one of the hosted providers and it seems to use some sort of HTTP conversion of some sort.

Anyhow, just wondering what other solutions are out there instead of having to add the domain to the SAN cert or creating the Public Service Record?
RFVDBAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Simon Butler (Sembee)ConsultantCommented:
There are three ways to deal with this.

1. Adding the domain to the list of Autodiscover.xxxx on the SSL certificate.
Fine for a small number of domains, but not practical for hosters. Therefore Microsoft added two further methods:

2. SRV records for Autodiscover.
http://semb.ee/srv

3. HTTP redirection method.
http://technet.microsoft.com/en-us/library/cc539052.aspx

The Autodiscover process is discussed in some depth in this article:

http://msdn.microsoft.com/en-us/library/office/ee332364(v=exchg.140).aspx

The CNAME method will be using the HTTP redirection process. This is the usual favourite because it does not require SRV records, which are not supported by all DNS hosts.

Simon.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
RFVDBAuthor Commented:
Super, I was missing the HTTP redirect method. Thanks!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.