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
Paul,
It should work fine. You can test prior to this with your own CA if you want. Internal OL uses the SCP to get the URL, external clients will use the SMTP address of the user to 'guess' the URL so as long as your SMTP address is user@mydomain.com then it should
work fine. The SCP address will probably fail or generate a prompt so you may want to change that value in AD for internal users. You can see what it's set to by using this command in the shell:
get-clientaccessserver | fl autodiscoverserviceinternaluri
I imagine you'll get your .local namespace returned. You can change it by doing this:
set-clientaccessserver <servername> -autodiscoverserviceinternaluri: https://autodiscover.mydomain.com/autodiscover/autodiscover.xml
https://autodiscover.mydomain.com/autodiscover/autodiscover.xml
That way internal clients that are able to use the SCP and external clients will resolve to the same name that the cert was issued to.
Loren,
Yes,thereisatypointhatthereshouldbeaspacewhereyouindicated. And yes, I typoed the name in the command for .local and should have entered .com. I think it still makes the point though. I would blame Chris for that but he's not here to defend himself today
:-)
Thanks,
Jim