Exchange 2010 - AutodiscoverServiceExternalURI

[timlineuk]

Hi All,

 

Bear with me, i've only just taken over this network and have been left with very limited information!

 

Our clients are getting an exchange certificate name error relating to autodiscover.domain...

 

If i enter the command "get-clientaccessserver | select Name, AutodiscoverServiceInternalURI" it returns https://mail.domain/Autodiscover/Autodiscover.xml

Now, the server name "mail" doesn't exist so should the URI be changed to our exchange server (https://exch1.domain/Autodiscover/Autodiscover.xml)?

 

Any assistance would be very much appreciated

 

Thanks

[free780]

Depends what domain name is on the SSL cert.

[timlineuk]

The certificates on exchange are webmail. and .

[win]

It would be easier if you bought a public wildcard certificate so you don't have to worry about names

[featured_spectre]

It would be easier if you bought a public wildcard certificate so you don't have to worry about names

 

some places don't even want to contemplate this. We looked at it, and yes whilst its only a few hundred per year, its just too much for some.

[ITGURU]

I always get the certificate error when installing a new exchange server. To resolve this I have

1. Imported the SSL certificate containing our external URL i.e https://webmail.domain.co.uk

2. Run Powershell commands to set both the internal and external URLs to the same domain as above.

 

Never used the internal domain name on anything.

[timlineuk]

OK, so i'm still being frustrated by this.

Internal and external are set to our external url and the DNS appears to be set correctly;

We've got a CName set for and alias name of autodiscover, FQDN is set to autodiscover. and FQDN for target host is set to our exchange server FQDN (exch1.).

There's also an A record for webmail. resolving to our exchange server.

 

We've got two certificates issued by our internal CA of "webmail." and "exch1." listed in IIS

 

I've been through various sites now and as far as i can tell I've set everything correctly (although obviously i'm missing something!).

I've done the various powershell commands to set the internal and external URL/URI but also had to change the outlook web app settings under client access which i believed was the same thing the powershell commands were doing...

 

None of the site i've looked at state that anything needs to be reset (apart from IIS on a couple of minimal changes)...

 

Any clue's or suggestions would great

 

Thanks

[timlineuk]

All sorted - the bindings in IIS were incorrectly set!