How Outlook 2007 and Windows Mobile 6.1 Use Autodiscover with SBS 2008

How Outlook 2007 and Windows Mobile 6.1 Use Autodiscover with SBS 2008

  • Comments 4
  • Likes

 [Today's post comes to us courtesy of Rituraj Choudhary and Shawn Sullivan]

After the completion of SBS 2008 setup and the Internet Address Management Wizard (IAMW), Exchange 2007 is configured to accept both internal and external Outlook 2007 SP1 and Windows Mobile 6.1 Autodiscover requests. These requests are handled by the Exchange Autodiscover service, which in turn provide the following information to connecting clients:

  1. The user’s display name as read from Active Directory.
  2. Separate connection settings for internal and external connectivity
  3. Location of the user’s mailbox (this is why Outlook 2007 is automatically able to find a mailbox that has been moved to another Mailbox server).
  4. Location information for free/busy, Out of Office assistant, web-distributed Offline Address Book (gives Windows Mobile 6.1 the capability of GAL lookups from the internet), …
  5. Outlook Anywhere (RPC/HTTP) server settings.

This information is combined to automatically configure the user’s profile, requiring no input from them other than their email address.

When configured properly, the Exchange Autodiscover truly is automatic. However, the technology is complex in the fact that its implementation spans several other technologies across multiple locations. In general, the following items need to be in place:

  1. External DNS records (Host A and SRV) must be correct.
  2. The IAMW creates a zone for the external Fully Qualified Domain Name (FQDN) that you choose on internal DNS. It points this name to the internal IP address of the server to service internal connections to the namespace.
  3. Requirement for Outlook 2007 SP1 or Windows Mobile 6.1.
  4. Properly configured Autodiscover virtual directory under the SBS Web Applications site.
  5. Properly configured internal and external URL on the Autodiscover virtual directory in Exchange 2007.
  6. Properly configured service connection point (SCP) in Active Directory for the Client Access (CAS) server.
  7. Properly configured SSL certificate installed in Exchange 2007 and the SBS Web Applications site, with the correct Fully Qualified Domain Name (FQDN). Important: Use the “IAMW” to either create the self-signed certificate or use the “Add a Trusted Certificate” wizard to install a 3rd party trusted certificate.
  8. If you are deploying a self-signed certificate created by the IAMW, you must install the certificate distribution package to your non-domain joined Outlook clients or Mobile 6.1 devices: http://blogs.technet.com/sbs/archive/2008/09/30/how-do-i-distribute-the-sbs-2008-self-signed-ssl-certificate-to-my-users.aspx

Domain-joined Outlook 2007 connections

A service connection point (SCP) object is created in Active Directory during the installation of the Client Access (CAS) role. Domain-joined clients will query this object and read the following attributes:

  1. serviceBindingInformation - Returns the Fully Qualified Domain Name (FQDN) of the CAS server. This will match the public URL that you have chosen in the IAWM. The Autodiscover virtual directory’s internal URL setting must match this value and the SBS server must be able to query the zone for the public domain in its DNS to return the internal IP address of the server.
  2. keywords Returns the Active Directory site which the CAS server belongs to. Exists specifically for when you have multiple CAS servers in different AD sites.

To find its location in ADSIEDIT, go here:

CN=Servername,CN=Autodiscover,CN=Protocols,CN=Servername,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OrganizationName,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=CONTOSO,DC=local

Where Servername is the name of your server, OrganizationName is the name of the Exchange Org and CONTOSO.local is the domain name.

The clients will retrieve the URL from an ldap query for the SCP, and retrieve the IP address from internal DNS. It will then connect to the server through the proper URL to the Autodiscover virtual directory.

Example:
  1. The client belonging to the contoso.local domain queries AD and retrieves https://remote.contoso.com/autodiscover/autodiscover.xml from the serviceBindingInformation attribute on the SCP.
  2. The client resolves remote.contoso.com to the internal IP address of the SBS 2008 server. This is because the IAMW has created a zone for remote.contoso.com in DNS and has pointed it to the internal IP of the server.
  3. A request is sent to https://remote.contoso.com/autodiscover/autodiscover.xml

Note: Non-domain joined clients may not be able to connect internally to the Autodiscover service.

Remote Clients and Windows Mobile 6.1 devices

Remote Outlook 2007 SP1 clients and Windows Mobile 6.1 devices query the DNS SRV record at the DNS registrar to locate the URL for the CAS server, according to the email address that you have specified. This record is either created/maintained automatically (if you choose a partner registrar during the IAMW) or manually (if you choose to maintain the domain yourself in the IAMW).

Service: _autodiscover
Protocol: _tcp
Port Number: 443
Host: FQDN

Important: Outlook 2007 without SP1 does not query for this SRV record, which causes Autodiscover to fail in default SBS 2008 deployments where the domain name has a prefix, like remote.contoso.com.

Example:
  1. User enters an email address of user@contoso.com
  2. The Outlook client or mobile device queries _autodiscover._tcp.contoso.com and remote.contoso.com is returned
  3. The client or device resolves remote.contoso.com to the external IP address of the SBS 2008 server.
  4. The request is sent to https://remote.contoso.com/autodiscover/autodiscover.xml

The auto-discover feature for a user can be checked using the command:

Test-OutlookWebServices -Identity <User Name>

Additional Reference:

For full details on the Exchange 2007 Autodiscover service, please see: http://technet.microsoft.com/en-us/library/bb332063.aspx

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
Comments
  • PingBack from http://diggwow.info/tags/101/200812/dns-server-15.html

  • Hi great post, I like it especially its following information to connecting clients:

      1. The user’s display name as read from Active Directory.

      2. Separate connection settings for internal and external connectivity

      3. Location of the user’s mailbox (this is why Outlook 2007 is automatically able to find a mailbox that has been moved to another Mailbox server).

      4. Location information for free/busy, Out of Office assistant, web-distributed Offline Address Book (gives Windows Mobile 6.1 the capability of GAL lookups from the internet), …

      5. Outlook Anywhere (RPC/HTTP) server settings.

    Cheers!!!

  • I can confirm this does not work internally for anyone that is confused.

  • Hi What I want to do is for example: I market law firms via emails. So I would like

    to send for example 30 emails to 30 different lawyers at same time but have each recipient

    not know that he is  part of a distribution group. so his email address is the only one that shows up on his email and not the other recipients. So he feels the email was only for him.

    PLEASE I beg you help me.

    Also since I grab my clients names at night is there any way to tell outlook to send the email at tomorrows date without showing the recipient that the night before that had I composed the email.