EDIT 10/4/2007: Since this post has been published, we have updated the Exchange 2007 Autodiscover Service whitepaper to include this information. Please consult the whitepaper for most up-to-date ...
Updated Jul 01, 2019
Version 2.0
Blog Post
I am thinking of implementing Alternative 2 for Autodiscover. It states in the help file "Do not use the Certificate Manager snap-in to import the certificates for any service on an Exchange server. Using the Certificate Manager snap-in to import certificates on Exchange servers will fail. Therefore, TLS or other Exchange certificate services will not work". However, your article states: "Right click, "Web Sites", choose "Web Site", make the description AutoDiscover, assign a new dedicated IP to this web site, use the default port of 80, don't enter a host header, for the Path, point to the same directory as your default web site
c:inetpubwwwroot
Also accept the default permissions.
Right click this web site, get properties, and go to Directory Security. Assign the autodiscover.contoso.com cert here.
"
Is there a downside to importing the Cert outside of the EMS?
c:inetpubwwwroot
Also accept the default permissions.
Right click this web site, get properties, and go to Directory Security. Assign the autodiscover.contoso.com cert here.
"
Is there a downside to importing the Cert outside of the EMS?