Mike's Tech Head Blog

What’s a Tech-Head? Well, hard to explain, but they do use technology where ever it is possible, even if it is not very smart or even needed…

Google Ads

On My Twitter now...

Loading...

News

Tags

Community

Recent Posts

Archives

Recommended Links

Email Notifications

Outlook 2007 Auto discover feature and SBS2008 & EBS2008

The auto discover feature is really cool but it will give you this error

image

Why?, Simple, the FQDN is in the certificate that is installed by default. So if you want this to work without any errors you need to replace the certificate with a certificate that also have that name.

In the default certificate Microsoft includes the following name by default, externaldomain.com, remote.externaldomain.com and server.internaldomain.local and we need to put the back in again plus the new name autodiscover.externaldomain.com

So this is how you do

  • On the SBS server run MMC.EXE and add the snap-in for Certificates and for certificate templates.
  • Change the permission on the “Web Server” certificate template and allow the SBS server to “Enroll”
  • image
  • Click on Certificates (Local Computer) and open “Personal – Certificates”
  • Right click “All Tasks – Request New Certificate”
  • Select “Web Server”
  • image
  • Select Subject Name: as Common name with the value of the external name (remote.externaldomain.com)
  • Select Alternative name: as DNS and add all the names you would like to have.
    externaldomain.com
    remote.externaldomain.com
    internaldomain.local
    autodiscover.externaldomain.com
    plus others if you would like to have…
  • Hit OK and select Enroll

Now you can open IIS Admin, open the SBS Web Application site, and change the certificate by opening “Bindings” and look for 443. Select Edit and change the certificate. You will se at least two certificates with the same name. With the view function you can see the names in the certificates.

Note. This will not destroy or delete your existing certificate, if you want you can always switch back.

There is of course one other way to fix this issue and that is to change in the external DNS. The SBS Diva has a really nice post about this if you prefer to do it in DNS instead

Mikael Nystrom
MCT, MVP Windows Server – Setup/Deployment

Comments

Amy Babinchak said:

Mikael - Thanks for the tip. In addition to the steps as outlined above we also have a need to mark the key as exportable. This option is found on the Private Key tab under Key Options. Simply check the box Make private key exportable.

Now however, after doing this we have an Exchange error occuring in the event log. Doesn't seem to be hurting us, but here it is.

"Microsoft Exchange couldn't find a certificate that contains the domain name remote.domain.net in the personal store on the local computer. Therefore, it is unable to support the STARTTLS SMTP verb for the connector Windows SBS Internet Send SERVER with a FQDN parameter of remote.domain.net. If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure that there is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the Microsoft Exchange Transport service has access to the certificate key."

I tried running this command in the Exchange shell:

enable-exchangecertificate -thumbprint F5765SF6G7F5G76FSF8G69AC54CS -services SMTP

But I got an error : the certificate with thumbprint blahblahbiglongnumber was found but is not valid for use with Exchange Server. Reason PrivateKeyNotAccessible

# February 23, 2009 7:58 PM

Ralph Hartwigsen said:

Hello,

thanks for the instructions.

It solved the problem... in the first place. I did exact the same steps you mentioned above and everything was fine.

But after 7 days without any of those messages it started again. I controlled the settings I've made and there where no changes, so it suddenly stopped working. I can't find a solution and I don't understand why it worked for 7 days.

The created certificate is valid until the year 2011, so thats not the problem.

Any suggestions?

Thanks in advance.

# April 23, 2009 8:53 AM

Dennis said:

After generating the new cert how would we deploy this to our users?  

# April 30, 2009 10:50 PM