• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 290
  • Last Modified:

Autodiscover certificate problem on hosted Exchange 2010 when using OOO and othe features

I am hosting a few customers on Exchange 2010 and would like to have more. I have ran into a problem when user whants to use out of office.
I am configurering the customers outlook to use Outlook anywhere pointing the server to my domain eg. mail.mydomain.dk.
I have bought a certificate for this hostname, so everything seems to work with no problems, the user can receive mails and send etc. with no problems and without having any problems with certificate.
The user then wants to use Out Of Office, if he do so the server cannot be found, I concluded that when you press OOO it automaticly goes for autodiscover.customerdomain.dk instead of the external url that I have set as mail.mydomain.dk.
I remember to have made an external url for the default EWS, but why is this not pushed trough the entire hosting organization?

Can I change so the hosted domains are pointing to the shared hostnname (mail.mydomain.dk) which has  the valid certificate or how can I solve this? I have tried to make som redirection on the IIS, with no luck yet. I believe it is pretty expensive to purchase a certificate that can cover "all" my customers mail hostnames.

0
Mrbonn
Asked:
Mrbonn
1 Solution
 
RadweldCommented:
At the very least, your certificates need to be unified coms or San certificates with the main subject being your domain and subject alternate names need to include autodiscover. You also need to register in public dns an autodiscover record.

This is because outlook anywhere uses autodiscover features and Im sure OOO is dependent.
0
 
Alan HardistyCommented:
When hosting, your additional domains will look for autodiscover.hosteddomain.com and if that doesn't resolve to anything in your SSL certificate, it will fail and OOF will therefore fail.

To resolve this without buying a gazillion name SSL certificate, use SRV records for the additional domains, pointing to a name that IS included in your SSL certificate and then Autodiscover will work happily.

Please have a read of the following MS article for details of how to setup the SRV record:

http://support.microsoft.com/kb/940881

As an example, if you have www.yourdomain.com in the SSL certificate, then use www.yourdomain.com as the pointer in the SRV record.

Create the SRV record in each additional domains External DNS records.
0
 
MrbonnAuthor Commented:
Works like a charm.
Added this SRV record _autodiscover._tcp.hosteddomain.dk Port 443 pointing to the server with certificata that I have eg. mail.mydomain.dk
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now