So some of the folks who have read my Exchange 2007/2010 Load Balancing articles here on the site have asked why I don’t include the steps for configuring the internal and external URL for the Autodiscover virtual directory. Shouldn’t these point to the load balancer FQDN as well?
Actually, there’s a very simple reason why they aren’t included. No silly not because I forgot all about them, but because they really aren’t use for anything. This is also why you don’t see them point to the server FQDN on a default installation (see screenshot above).
When it comes to Autodiscover and the service connection point (SCP), you use the “Set-ClientAccessServer” cmdlet with the “AutoDiscoverServiceInternalUri” parameter to define the FQDN that should be used to look up Autodiscover information when using an internal domain joined and connected Outlook MAPI client.
Listing the Autodiscover Internal URI using the Exchange Management Shell:
Looking at the Autodiscover Internal URI using ADSI Edit:
Remember for external Outlook Anywhere clients and Mobile devices that support Autodiscover, we rely on the Autodiscover record in external DNS (or one of the 3 other methods that can be used. For details see the Autodiscover whitepaper).
Technology Architect/Writer/MS Vendor
MCM: Exchange 2007 | MVP: Exchange Architecture