White Paper: Exchange 2007 Autodiscover Service

Page 1 of 41

©2010 Microsoft Corporation. All rights reserved.

White Paper: Exchange 2007 Autodiscover Service
Topic Last Modified: 2009-12-23 Joey Masterson, Technical Writer, Microsoft Exchange Server; Joe Turick, Support Engineer, Microsoft Enterprise Messaging Support; and Ross Smith IV, Technology Architect, Microsoft Exchange Server. November 2007

Summary
This white paper provides detailed information about the Microsoft Exchange Autodiscover service. It also includes information about how to configure this service in various deployment scenarios. Use the conceptual information and procedures in this white paper to help you deploy the Autodiscover service.
Note:

To print this white paper, click Printer Friendly Version in your Web browser.

Applies To
Microsoft Exchange Server 2007 Table of Contents Introduction How the Autodiscover Service Works with Clients How Outlook 2007 and Autodiscover Interoperate Autodiscover and Certificates Understanding the Exchange Setup Self-Signed Certificate Supported Scenarios for Connecting to the Autodiscover Service from the Internet Scenario 1: Using a Certificate That Supports Multiple DNS Names Scenario 2: Using One Single-Name Certificate Scenario 3: Using Two Single-Name Certificates Scenario 4: Using the Autodiscover Service with Redirection Summary of Supported Scenarios for Connecting to the Autodiscover Service from the Internet How to Configure the Autodiscover Service for Internet Access Scenario 1: How to Use a Certificate That Supports Multiple DNS Names Scenario 2: How to Use One Single-Name Certificate Scenario 3: How to Use Two Single-Name Certificates Scenario 4: How to Use a Single SSL Certificate and the Autodiscover Redirect Web Site Optional Deployment Information for a Large-Scale Hosted Environment Additional Deployment Scenarios and Considerations for the Autodiscover Service Configuring the Autodiscover Service to Use Site Affinity for Internal Communication How to Configure the Autodiscover Service to Use Site Affinity Configuring the Autodiscover Service for Multiple Forests How to Configure the Autodiscover Service When You Use Multiple Forests

http://technet.microsoft.com/en-us/library/bb332063(EXCHG.80,printer).aspx

3/2/2010

White Paper: Exchange 2007 Autodiscover Service

Page 2 of 41

Managing the Autodiscover Service How to Configure the Autodiscover Service for Cross Forest Moves How to Configure Exchange Services for the Autodiscover Service Autodiscover and ISA Server 2006 Conclusion

Introduction
Microsoft Exchange Server 2007 includes a new Microsoft Exchange service named the Autodiscover service. The Autodiscover service configures and maintains server settings for client computers that are running Microsoft Office Outlook 2007. The Autodiscover service can also configure supported mobile devices. An important function of the Autodiscover service is to provide access to Microsoft Exchange features for Outlook 2007 clients that are connected to your Microsoft Exchange messaging environment. These features include the Web-based offline address book (OAB), the Availability service, and Unified Messaging (UM). The Autodiscover service must be deployed and configured correctly for Outlook 2007 clients to automatically connect to Microsoft Exchange features. For more information about how to configure Exchange features, see How to Configure Exchange Services for the Autodiscover Service later in this white paper.

How the Autodiscover Service Works with Clients
When you install the Client Access server role on a computer that is running Exchange 2007, a new virtual directory named Autodiscover is created under the Default Web Site in Internet Information Services (IIS). This virtual directory handles Autodiscover service requests from Outlook 2007 clients in the following circumstances: When a new Outlook profile is configured or updated When a client periodically checks for changes to the Exchange Web Services URLs When underlying network connection changes occur in your Exchange messaging environment Additionally, a new service connection point (SCP) Active Directory object is created for each server where the Client Access server role is installed. The SCP object is used by domain-connected clients to locate the Autodiscover service. The SCP object contains two pieces of information, the serviceBindingInformation attribute and the keywords attribute. The serviceBindingInformation attribute has the Fully Qualified Domain Name (FQDN) of the Client Access server in the form of https://cas01.contoso.com/autodiscover/autodiscover.xml, where cas01.contoso.com is the fully qualified domain name (FQDN) for the Client Access server. The keywords attribute specifies the Active Directory sites to which this SCP record is associated. By default, this attribute specifies the Active Directory site to which the Client Access server belongs. When a domain-connected client connects to the Active Directory directory service, the Exchange 2007 client authenticates to Active Directory and tries to locate the Autodiscover SCP objects that were created during Setup by using the user's credentials. In deployments that include multiple Client Access servers, an Autodiscover SCP record is created for each Client Access server. By using the user credentials, the Outlook 2007 client authenticates to Active Directory and searches for the Autodiscover SCP objects. After the client obtains and enumerates the instances of the Autodiscover service, the client connects to the first Client Access server in the enumerated and sorted list and obtains the profile information in the form of XML data that is needed to connect to the user's mailbox and available Microsoft Exchange features. An Outlook 2007 client connects to the Autodiscover service as follows: 1. Outlook 2007 sends a Lightweight Directory Access Protocol (LDAP) query to Active Directory looking for all available SCP objects. Specifically, Outlook initializes the LDAP connection using the ldap_init() function and passes a NULL value for the hostname. When a particular global catalog server name (or domain name) is not specified, the operation searches for a global catalog server in the domain, based on the membership of the computer that is initializing the operation. 2. .Outlook 2007 sorts and enumerates the returned results based on the client's Active Directory site by using the keyword attribute of the SCP record. One of two lists is created, an in-site list or an out-of-site list. The in-site list provides the SCP records that have AutodiscoverSiteScope information. AutodiscoverSiteScope is a parameter that is set on the Client Access server by using the Set-ClientAccessServer cmdlet. The parameter specifies the site for which the Autodiscover

http://technet.microsoft.com/en-us/library/bb332063(EXCHG.80,printer).aspx

3/2/2010

White Paper: Exchange 2007 Autodiscover Service

Page 3 of 41

service is authoritative. The AutodiscoverSiteScope information contained in the SCP records for the in-site list matches the Active Directory site for the Outlook client. If there are no in-site records, an out-of-site SCP record list will be generated. The list is not sorted in any particular order. Therefore, the list is approximately in the order of oldest SCP records (based on creation date) first.
Note:

In environments where Outlook 2007 is deployed in remote sites that do not have Exchange 2007 Mailbox and Client Access servers, you can use site affinity to configure the SCP objects for Outlook 2007 clients to use SCP objects that are physically closer. For more information, see How to Configure the Autodiscover Service to Use Site Affinity later in this white paper.
3. Outlook first tries to connect to each Autodiscover URL that it had previously generated from either an in-site list or an out-of-site list. If that doesn't work, Outlook will try to connect to the predefined URLs (for example, https://autodiscover.contoso.com/autodiscover/autodiscover.xml) by using DNS. If that fails also, Outlook will try the HTTP redirect method and, failing that, Outlook will try to use the SRV record lookup method. If all lookup methods fail, Outlook will be unable to obtain Outlook Anywhere configuration and URL settings. 4. The Autodiscover service queries Active Directory to obtain the connection settings and URLs for the Exchange services that have been configured. 5. The Autodiscover service returns an HTTPS response with an XML file that includes the connection settings and URLs for the available Exchange services. 6. Outlook uses the appropriate configuration information and connection settings to connect to your Exchange messaging environment. For more information about SCP objects, see Publishing with Service Connection Points [ http://go.microsoft.com/fwlink/?LinkId=72744 ] . The following figure illustrates how a client connects to a Client Access server the first time from inside the Exchange messaging organization. The Autodiscover service process for internal access

When Outlook 2007 is started on a client that is not domain-connected, it first tries to locate the Autodiscover service by looking up the SCP object in Active Directory. Because the client is unable to contact Active Directory, it tries to locate the Autodiscover service by using Domain Name System (DNS). In this scenario, the client will determine right side of the user’s e-mail address, that is, contoso.com, and check DNS by using two predefined URLs. For example, if your SMTP domain is contoso.com, Outlook will try the following two URLs to try to connect to the Autodiscover service: https://contoso.com/autodiscover/autodiscover.xml https://autodiscover.contoso.com/autodiscover/autodiscover.xml

http://technet.microsoft.com/en-us/library/bb332063(EXCHG.80,printer).aspx

3/2/2010

White Paper: Exchange 2007 Autodiscover Service

Page 4 of 41

Important:

For Outlook to be able to locate the Autodiscover service by using DNS, there must be a host record in DNS for the Autodiscover service that maps the entry point, or public IP address, to the Client Access server where the Autodiscover service is hosted.
The following figure illustrates a simple topology with a client connecting from the Internet. The Autodiscover service process for external access

Another option related to DNS is made possible with an Outlook 2007 software update. When this software update is applied, Outlook 2007 clients will perform an additional check for a DNS SRV record to locate the Autodiscover service which does not require multiple Web sites and IP addresses or a new Unified Communications Secure Sockets Layer (SSL) certificate. Although this still requires that you add a DNS record in DNS for the Autodiscover service, you do not have to use a certificate that supports multiple DNS names and or have to administer a second Web site. For more information about this software update for Outlook 2007, see Microsoft Knowledge Base article 940881, A new feature is available that enables Outlook 2007 to use DNS Service Location (SRV) records to locate the Exchange Autodiscover service [ http://go.microsoft.com/fwlink/? linkid=3052&kbid=940881 ] . To obtain this update, see Microsoft Knowledge Base article 939184, Description of the update rollup for Outlook 2007: June 27, 2007 [ http://go.microsoft.com/fwlink/? linkid=3052&kbid=939184 ] . Return to top

How Outlook 2007 and Autodiscover Interoperate
The Autodiscover service makes it easier to configure and manage Outlook 2007. Earlier versions of Microsoft Exchange and Outlook required that you configure all user profiles manually to access Exchange. Extra work was required to manage these profiles if changes occurred to the messaging environment. Otherwise, the Outlook clients could stop functioning correctly. The Autodiscover service uses a user's e-mail address and domain account to automatically configure the user's profile. By using the e-mail address and domain account, the Autodiscover service can provide the following information to the client: The user’s display name Separate connection settings for internal and external connectivity The location of the user’s Mailbox server

http://technet.microsoft.com/en-us/library/bb332063(EXCHG.80,printer).aspx

3/2/2010

aspx 3/2/2010 . The setting for the Time to Live is 60 minutes or whenever an error occurs when Outlook 2007 tries to contact an Exchange 2007 server.microsoft. How the Autodiscover Service Provides Settings to Outlook 2007 The connection settings that the Outlook client uses are translated into MAPI properties. If Outlook does not connect to the Autodiscover service. the Out of Office Assistant. the MAPI layer also connects to the Autodiscover service if the user creates a new Outlook profile. Depending on the type of failure. For example. This HTTP response contains the relevant values in XML. the data is passed to the Autodiscover service. This setting includes port settings and the internal URLs for the Exchange services that you have enabled. the Outlook layer will reconnect every 5 minutes because the URLs for the available Exchange services are cached in memory on the local computer. the user cannot use the available Exchange services until the specified URLs are obtained. The first failure detected by the MAPI layer results in an initial Autodiscover service request. as follows: The WEB setting contains the best URL for Outlook Web Access for the user to use. and the Web-based offline address book Outlook Anywhere server settings To start to communicate with the Exchange messaging infrastructure. the MAPI layer connects to the Autodiscover service when there are errors connecting to the Exchange server by using the MAPI protocol. which returns the information to the client in an HTTP response. The EXPR setting references the Exchange HTTP protocol that is used by Outlook Anywhere. which are known as layers. After the values have been returned. this request may result in changes to the user's profile. http://technet. If no other failures occur after the first failure. This information is created and stored in Active Directory both during Exchange 2007 Setup and when you configure your Exchange features by using the Exchange Management Shell or the Exchange Management Console. There are three Outlook provider settings. which are used by clients that access Exchange from the Internet. This setting is not required for Exchange 2007.White Paper: Exchange 2007 Autodiscover Service Page 5 of 41 The URLs for various Outlook features that govern such functionality as Availability (free/busy) information. These properties are stored in the user's profile located in the registry on their local computer. Outlook 2007 sends an HTTP POST command to the Autodiscover service. This command includes XML data that requests the connection settings and URLs for the Exchange services that are associated with the Outlook provider.80. The Outlook layer begins operating when you open Outlook 2007 to retrieve the user profile settings. However. The EXCH setting references the Exchange RPC protocol that is used internally. This setting includes the external URLs for the Exchange services that you have enabled. The Autodiscover Service and the Outlook Provider The Autodiscover service sends the request to the Outlook provider. This initial Autodiscover service request is known as the free Autodiscover service request. Unified Messaging. Outlook 2007 automatically connects to the Autodiscover service under the following conditions: Every time that the application starts At intervals on a background thread Any time that the client's connection to an Exchange server fails There are two parts. Additionally.com/en-us/library/bb332063(EXCHG. If the client cannot connect to the Autodiscover service. By contrast. which then uses the Services Discovery API to retrieve the values in Active Directory. of Outlook 2007 that use the Autodiscover service: the Outlook layer and the MAPI layer.printer). this occurs when the user is using a lowbandwidth network connection or when the user tries to open their mailbox after a mailbox move. the MAPI layer will perform an Autodiscover service request every 6 hours to update the user's profile settings. the URLs for the available Exchange services are cached in the memory of the local computer. These settings are refreshed every time that the Time to Live (TTL) period is specified.

Exchange setup will create a self-signed SSL certificate in Internet Information Services (IIS) that meets validity tests for domain-connected clients. For this communication to occur without failing. In Outlook 2007. in addition to communication between the Outlook client and Exchange services. on the E-mail tab. The administrator is surprised to see that the Autodiscover service did not create the connection settings in the Outlook profile. Exchange 2007 setup determines whether an SSL certificate has already been installed on the server. This enables domain- http://technet. In this example. it must meet the following criteria for the Autodiscover service: The client can follow the certificate chain up to the trusted root. Outlook provides a method to force this update to occur. Open Outlook 2007. and then click Account Settings.80. click Tools.printer). Understanding the Exchange Setup Self-Signed Certificate When you install the Client Access server role. The self-signed certificate has a common name that maps to the NetBIOS name of the server. Return to top Autodiscover and Certificates One of the most important aspects of a successful Exchange messaging deployment is how you configure your SSL certificates for securing client communication to your Exchange infrastructure. there are instances when it may appear that the Autodiscover service is not functioning correctly. the Outlook 2007 client successfully connects to the Mailbox server by using TCP/IP.White Paper: Exchange 2007 Autodiscover Service Page 6 of 41 Forcing Outlook 2007 to Update the User Profile Settings Under most circumstances. Because no failure was detected. you must have a valid SSL certificate installed.microsoft. However. If an SSL certificate is not found. The administrator would also like to deploy Outlook Anywhere so that users can access their Exchange information and services from the Internet. After enabling Outlook Anywhere. Outlook uses the initial Autodiscover "free" request that is performed at six-hour intervals. the administrator configures and enables Outlook Anywhere for Exchange 2007. 2. 3. The certificate is current and has not expired. the administrator checks the Outlook profile settings on an Outlook 2007 client and notices that the RPC over HTTPS settings were not received by the client. the IT administrator for Contoso upgrades the users to Outlook 2007. To manually force the Autodiscover service to update the user's profile settings 1. The following procedure describes how to force Outlook to update the user profile settings by using the Autodiscover service. This design enables Outlook 2007 to function without any certificate warnings when Outlook uses the self-signed certificate that is installed by Exchange 2007 Setup. Outlook 2007 and the Autodiscover service are intended to provide a seamless experience for users. To do this. Note: For domain-connected clients. This scenario occurs when the user's Outlook client runs continually. The administrator then runs the test for the Autodiscover service by using the Test E-Mail AutoConfiguration feature in Outlook 2007.com/en-us/library/bb332063(EXCHG. click Repair. Outlook 2007 is designed to ignore the first validity check in the previous list. Because this scenario is possible. The following scenario is an example of when this might occur: After you deploy Exchange Server 2007 in the messaging environment of the Contoso company. the Autodiscover service does not try to re-create the Outlook profile settings. This is because all communication between Outlook clients and the Autodiscover service endpoint. 4. Follow the steps in the Repair E-mail Account wizard. The name matches the URL that the client is trying to communicate with. On the E-mail Accounts page. The self-signed certificate also includes the FQDN of the server as an additional DNS name that is stored in the certificate’s Subject Alternative Name field.aspx 3/2/2010 . For a certificate to be considered valid. occurs over an SSL channel.

Supported Scenarios for Connecting to the Autodiscover Service from the Internet If you are providing external access to Microsoft Exchange by using Outlook Anywhere (formerly known as RPC over HTTP) you must install a valid SSL certificate on the Client Access server by using one of the following four scenarios. These scenarios and solutions are discussed in the following sections. before the Autodiscover service can provide the correct external URLs to clients.com/en-us/library/bb332063(EXCHG.xml https://autodiscover. in addition to other externally published Exchange features such as Outlook Web Access or Exchange ActiveSync which might reference a different DNS namespace. such as the Availability service.509 v. the Autodiscover service should be located at either https://contoso.xml or https://autodiscover.microsoft.com. for the Autodiscover service to function correctly. autodiscover.<smtp-address-domain>/autodiscover/autodiscover.com/autodiscover/autodiscover.contoso. These types of certificates are known as Unified Communications certificates. the self-signed certificate allows domain-connected Outlook 2007 clients to work immediately after Exchange setup as completed and without any security warnings. Although using a certificate that supports Subject Alternative Names is a recommended solution. When the client tries to connect to your Microsoft Exchange messaging environment.aspx 3/2/2010 .com. Outlook Anywhere clients and mobile device users who connect by using Exchange ActiveSync will be unable to connect when referencing a certificate whose common name is the NetBIOS name of the server. Outlook 2007 clients must be able to resolve the DNS namespace.contoso. Note: The Subject Alternative Name field is a special field that is available in X. To summarize.printer).contoso. the client locates the Autodiscover service on the Internet by using the right side of the user's e-mail address that was entered. Which method that you choose should be decided after you weigh the advantages and disadvantages associated with the following methods. Instead. if the user's e-mail address is kwekua@contoso.White Paper: Exchange 2007 Autodiscover Service Page 7 of 41 connected clients to successfully connect to the Autodiscover service without receiving any certificate warnings if the certificate has not expired and the FQDN of the server you are connecting to is stored in the Subject Alternative Name of the certificate. you must correctly configure your Exchange services.com/autodiscover/autodiscover. Because Outlook 2007 clients connect to the Autodiscover service by using SSL. The Autodiscover service URL will be either of the following URLs: https://<smtp-address-domain>/autodiscover/autodiscover. Although the client is unable to validate the self-signed certificate up to the trusted root. mail.80.xml.xml.com. Additionally.contoso. we do not recommend long-term use of this self-signed certificate because it was primarily intended to ease the urgency of obtaining a correct certificate so that Outlook 2007 clients can immediately start to use Exchange 2007 features. for example.com. Note: We recommend that you immediately replace the self-signed certificate with a commercially available Internet trusted certificate or a trusted internal public key infrastructure (PKI)-issued certificate. this must be the user's primary SMTP address. this is the one validity test that is allowed when domain-connected clients connect to the Autodiscover service by using the self-signed certificate. this introduces a new challenge. the common name of the certificate must be in the form of a FQDN that maps to the external DNS namespace those clients will be connecting to. for example. There are several methods for configuring your Client Access server to support connections to the Autodiscover service from the Internet. However. For example. This can all be done by using an SSL certificate that supports Subject Alternative Names. starting with the implementation of a Unified Communications certificate. such as mail. there are other solutions you can implement if you cannot deploy a certificate that supports Subject Alternative Names. This means that you must add a host record for the Autodiscover service to your external DNS zone. However.3 certificates that lets you add multiple DNS names to a single certificate. http://technet. Notice that.

using a Unified Communications certificate may increase the cost.microsoft. Unified Communications Certificate Partners for Exchange 2007 and for Communications Server 2007 [ http://go. A new feature is available that enables Outlook 2007 to use DNS Service Location (SRV) records to locate the Exchange Autodiscover service [ http://go. Although this may be the least expensive approach at first. this solution is the simplest and least expensive way to deploy Outlook Anywhere in hosted and non-hosted Exchange 2007 environments. For more information.microsoft. This warning message.com/en-us/library/bb332063(EXCHG. Note: There are special considerations when you use Unified Communications certificates with Internet Security and Acceleration (ISA) Server 2004 and ISA Server 2006. However. and Microsoft Knowledge Base article 939184. 2007 [ http://go.White Paper: Exchange 2007 Autodiscover Service Page 8 of 41 Return to top Scenario 1: Using a Certificate That Supports Multiple DNS Names We recommend that you provide all the necessary DNS names in the same certificate by using a Unified Communications certificate that supports the Subject Alternative Name field. Using a Unified Communications certificate reduces the complexity of configuring and managing the Autodiscover service and Exchange services URLs.microsoft.com/fwlink/?LinkID=100584 ] Obtaining a Unified Communications Certificate A list of third-party certification authorities (CAs) that currently support Subject Alternative Names is documented in Microsoft Knowledge Base article 929395. you must update the Autodiscover URL in the SCP object in Active Directory and the internal URLs for the Exchange services so that Outlook clients do not receive the following error: The name of the security certificate is invalid or does not match the name of the site. see the following articles: ISA Server team blog article: Certificates with Multiple SAN Entries May Break ISA Server Web Publishing [ http://go.com/fwlink/?linkid=3052&kbid=939184 ] . Important: In this scenario. you will incur the additional administrative overhead of distributing and maintaining the root certificates to your users so that clients that are not domain-connected can follow the certificate chain up to the trusted root certificate store.com/fwlink/?linkid=3052&kbid=940881 ] . is documented in Microsoft Knowledge Base article 940726. they are not required.aspx 3/2/2010 .80. see Microsoft Knowledge Base article 940881. For more information. Description of the update rollup for Outlook 2007: June 27.microsoft. and how to correct it. Warning message when you start Outlook 2007 and then connect to a mailbox that is hosted on an Exchange 2007-based server: "The name of the security certificate is invalid or does not match the name of the site" [ http://go. http://technet. Another recommended solution is to use one single-name certificate installed on the Default Web Site. Return to top Scenario 2: Using One Single-Name Certificate and the Autodiscover SRV Record Although certificates that support Subject Alternative Names are highly recommended. you could install Windows Certificate Services and create and install your own SSL certificate that includes multiple DNS names.com/fwlink/? linkid=3052&kbid=929395 ] .microsoft. your Outlook Anywhere users must manually install the root certificate on their remote workstations and Exchange ActiveSync users must manually install the root certificate on their mobile devices.microsoft.printer). Or. as this kind of certificate can be more expensive than the single name certificates which you already may own. If your DNS provider supports SRV records. Additionally.com/fwlink/?linkid=3052&kbid=940726 ] .

Return to top Scenario 4: Using the Autodiscover Service with Redirection Until the release of the update rollup for Outlook 2007. In this case. One option is to obtain a second certificate and install it on a second Web site which will be specifically used for Autodiscover.com. this solution also requires a second public IP address which must be assigned to the second Web site.printer). Return to top Summary of Supported Scenarios for Connecting to the Autodiscover Service from the Internet All the previous scenarios are supported by Microsoft but vary in complexity. For example. Domain-connected clients continue to locate the Autodiscover service by using the SCP object and will not receive any security warnings as long as the URL for connecting to the Autodiscover service which is stored in the SCP object has been changed to refer to the FQDN of the certificate installed on the Default Web Site. the ideal solution to use in situations such as a hosted Exchange 2007 environment. or if you have already purchased a new single-name certificate before fully understanding the certificate requirements for the Autodiscover service for Exchange 2007. This option requires two separate Web sites and public IP addresses.aspx 3/2/2010 .com/en-us/library/bb332063(EXCHG. and may still be. Note: Similar to using two single-name certificates. In this scenario.contoso.com. for example autodiscover. However. Using the Autodiscover service with redirection may be the ideal solution because some DNS providers do not support SRV records. this may occur if you want to replace the self-signed certificate with a preexisting certificate exported from an earlier version of Exchange. they will see a dismissible warning messaging asking them to verify that they are being redirected to a trusted URL. this kind of deployment scenario was. one certificate is issued with the common name that is used as the entry point for clients that connect from the Internet. you install a single-name certificate on the Default Web Site and create another Web site that contains no certificate. Clients that connect from the Internet will at first be unable to find Autodiscover by using DNS. When these Internetbased Outlook clients connect to this redirection site. If this describes your situation. Outlook will try an additional method to connect to the Autodiscover URL by using HTTP (instead of HTTPS) and connect to the Autodiscover Web site and then be redirected to the Autodiscover service hosted under the Default Web Site. there are alternative solutions you can implement to address these types of scenarios which will ultimately give you the same level of functionality.microsoft. described in Microsoft Knowledge Base article 939184 and referred to in Scenario 2: Using One Single-Name Certificate earlier in this white paper. The following table illustrates the pros and cons associated with each solution. for example. you must advise your users to accept this warning message and allow Outlook to connect to this trusted URL. this kind of deployment can also be used for organizations that are not hosting multiple domains. mail.contoso. With this option. Scenario Single certificate that supports Pros Easy to implement Cons Higher cost certificate type (Unified Communications certificate) http://technet. before failing to connect to the Autodiscover service. The Default Web Site will host your primary Exchange features and services such as Outlook Web Access and Exchange ActiveSync while the second Web site will be used to host the Autodiscover service.80. The second certificate has a common name that references the FQDN for the Autodiscover service. However. The effort involved in implementing and managing each solution over the long term may result in increased the total cost of ownership depending on your environment.White Paper: Exchange 2007 Autodiscover Service Page 9 of 41 Return to top Scenario 3: Using Two Single-Name Certificates Sometimes you cannot use a certificate that supports multiple DNS names. as described in How the Autodiscover Service Works earlier in this white paper.

described in Microsoft Knowledge Base article 939184 Description of the update rollup for Outlook 2007: June 27.80. Warning message when you start Outlook 2007 and then connect to a mailbox that is hosted on an http://technet. 2007 [ http://go.microsoft.White Paper: Exchange 2007 Autodiscover Service Page 10 of 41 multiple DNS names Supports all client connections Microsoftrecommended best practice Easy to implement Supports all client connections Least expensive Ideal for hosters if DNS provider supports SRV records Requires additional configuration if used together with either ISA Server 2004 or ISA Server 2006 One singlename certificate and Web site Requires modification of SCP object and Exchange services URLs Requires Outlook 2007 update rollup. see Microsoft Knowledge Base article 940726.microsoft. your internal Outlook 2007 users may report that they receive the following security warning when they start Outlook: The name of the security certificate is invalid or does not match the name of the site.com/fwlink/? linkid=3052&kbid=939184 ] .com/en-us/library/bb332063(EXCHG. For more information about this security warning.printer). to support Autodiscover SRV record if also deploying Outlook Anywhere DNS provider may not support Autodiscover SRV record Requires an additional public IP address Complex to set up and maintain Two singlename certificates and Web sites Lower cost than using Unified Communications certificate Both sites are secured with SSL Can be done by using your existing certificate No additional cost Ideal for hosters if DNS provider does not support SRV records Smallest upfront costs Supports all client connections Single certificate with Redirect Requires an additional public IP address Somewhat complex to set up Single certificate generated by using Windows Certificate Services Highest total cost of ownership for administrators and end users Note: Whichever solution you implement to replace the default self-signed certificate.aspx 3/2/2010 .

The following procedures describe how to create a certificate request for submission to a third-party CA and when to use your own internal PKI by using Windows Certificate Services.com/en-us/library/bb332063(EXCHG.contoso.microsoft. We recommend that you use a Unified Communications certificate that supports Subject Alternative Names.80. Step 1: Create the Certificate Request http://technet. for example.com. Return to top How to Configure the Autodiscover Service for Internet Access This section describes how to configure the Autodiscover service in the following four scenarios: Scenario Scenario Scenario Scenario 1: 2: 3: 4: Using Using Using Using a certificate that supports multiple DNS names one single-name certificate two single-name certificates the Autodiscover service with redirection The following table outlines the various requirements for each scenario.printer). ** Must resolve to the FQDN for the Autodiscover service.com/fwlink/? linkid=3052&kbid=929395 ] .microsoft.microsoft. autodiscover.contoso.White Paper: Exchange 2007 Autodiscover Service Page 11 of 41 Exchange 2007-based server: "The name of the security certificate is invalid or does not match the name of the site" [ http://go.com. mail. Return to top Scenario 1: How to Use a Certificate That Supports Multiple DNS Names This section discusses how to configure the Autodiscover service that uses either a Unified Communications certificate or a certificate created internally by using Windows Certificate Services. Unified Communications Certificate Partners for Exchange 2007 and for Communications Server 2007 [ http://go.aspx 3/2/2010 . The list of third-party certification authorities (CAs) that currently support Subject Alternative Names is documented in Microsoft Knowledge Base article 929395. Requirements Scenario 1 Yes No Yes Scenario 2 Yes No Yes Scenario 3 Yes Yes Yes Scenario 4 Yes Yes Yes Primary IP address Secondary IP address Primary public IP resolving to Default Web Site* Secondary public IP resolving to Autodiscover Web site** # of certificates Modification of SCP object Modification of Web services URLs No No Yes Yes 1 No No 1 Yes Yes 2 Yes Yes 1 Yes Yes * Must resolve to the host name that users use to connect to Exchange services. for example.com/fwlink/?linkid=3052&kbid=940726 ] .

For example.microsoft.contoso.contoso.contoso.com" -Path c:\certrequest. server01. To create a certificate request internally by using Windows Certificate Services http://technet. you will want to add more DNS names to the DomainNames parameter.microsoft.printer).com. open Exchange Management Shell and enter the following: Copy Code New-ExchangeCertificate -GenerateRequest -DomainName mail. autodiscover.80.aspx 3/2/2010 . CN=server01.local.com/fwlink/? LinkId=21763 ] Best Practices for Implementing a Microsoft Windows Server 2003 Public Key Infrastructure [ http://go. Important: Make sure to include the PrivateKeyExportable parameter and set the value to $true if you plan to use the certificate on additional Client Access servers and ISA Servers computers.contoso.com.microsoft.contoso. you might enter something similar to the following: Copy Code New-ExchangeCertificate -GenerateRequest -DomainName mail. On the Client Access server.com" -Path c:\certrequest. For additional details about how to manage your own Public Key Infrastructure for Windows Server 2003.txt Important: If your internal DNS namespace differs from your external namespace.com/fwlink/?LinkId=17800 ] The following procedure describes how to install Windows Certificate Services and request an SSL certificate.com -FriendlyName contosoinc -KeySize 1024 PrivateKeyExportable:$True -SubjectName "c=US o=contoso inc.contoso. After you request the certificate. Step 1a (Optional) Install Windows Certificate Services and Request a Certificate You can use Windows Certificate Services to create and manage your own SSL certificates. Confirm the required parameters and necessary information with the CA vendor. see the following resources: Public Key Infrastructure for Windows Server 2003 [ http://go.contoso. CN=server01. autodiscover. server01 -FriendlyName contosoinc -KeySize 1024 -PrivateKeyExportable:$True -SubjectName "c=US o=contoso inc.White Paper: Exchange 2007 Autodiscover Service Page 12 of 41 To create a certificate request for a third-party certification authority Create the certificate request for submission to your third-party certification authority (CA).com. see "Step 2: Install the Certificate" later in this section.com/en-us/library/bb332063(EXCHG.txt Note: You may be asked to include additional parameters or may be confused about what to enter for the SubjectName.

com. Note: http://technet. Be certain that you enter the FQDN that users will use to connect to services including Outlook Web Access. Select Web Server under Certificate Template. 5. Click Request a certificate. 2. http://CAS01/certsrv or https://CAS01/certsrv. 3. that is.80.contoso. and then save the CER file to Drive C. and then select Submit a certificate request by using a base-64-encoded CMC or PKCS #10 file. Note: If your internal DNS namespace differs from your external namespace. and Outlook Anywhere. you will want to add more DNS names to the DomainNames parameter.local PrivateKeyExportable:$True -Path c:\certreq. click Advanced certificate request. 7.com -PrivateKeyExportable:$True -Path c:\certreq.txt 4. autodiscover.microsoft. Copy the contents of the certreq.contoso.cer. on the Client Access server.White Paper: Exchange 2007 Autodiscover Service Page 13 of 41 1. you will be prompted to select the type of CA to install.com. For example.contoso. open Add/Remove Windows Components and install Certificate Services. Click Download certificate. autodiscover. c:\certnew. open Internet Explorer and enter the URL to connect to the Certificate Services administration Web page that is hosted on the server where you installed Certificate Services. machinename. Step 2: Install the Certificate The following procedure describes how to import and enable a third-party certificate or one that you created internally by using Windows Certificate Services. Exchange ActiveSync. you might enter something similar to the following: Copy Code New-ExchangeCertificate -GenerateRequest -DomainName mail.txt Important: The first DNS name following the DomainName parameter will automatically become the common name associated with the certificate. On your Client Access server. The process is the same for each. install Windows Certificate Services on a server that is running Windows Server 2003 in your messaging infrastructure. 8. 9.contoso. Click Submit. 6. If you have not already done this.com/en-us/library/bb332063(EXCHG. To create the certificate request. Note: During installation of Certificate Services. machinename. For example. On a server that is running Windows Server 2003.txt file that you saved in step 3 in the Saved Request field.com. Select the option to install an Enterprise CA and complete the wizard. open the Exchange Management Shell and enter the following: Copy Code New-ExchangeCertificate -GenerateRequest -DomainName mail.aspx 3/2/2010 .printer).contoso.

80. If you are running Windows XP. Double-click the root certificate. an FTP site. 3. 6. In the Certificate dialog box.White Paper: Exchange 2007 Autodiscover Service Page 14 of 41 The Import-ExchangeCertificate cmdlet installs the certificate in the Personal certificate store on the server and the Enable-ExchangeCertificate cmdlet installs the certificate on the Web site. If domain-connected clients cannot automatically install the root certificate. Important: Installing a root certificate on a mobile device requires that you connect the device with your Windows operating system. In the Select Certificate Store window.com/en-us/library/bb332063(EXCHG. 2. open the Exchange Management Shell on the Client Access server and run the following command: Copy Code Import-ExchangeCertificate -Path <full path to cert file> | EnableExchangeCertificate -Services iis Step 3: (Optional) Administering and Using Root Certificates for End Users Notice that domain-connected clients will typically obtain the root certificate automatically by using a Group Policy. and then select Download a CA certificate option. certificate chain or CRL option. 3.aspx 3/2/2010 . on the General tab. Copy the root certificate to the desktop. Save the .printer).cer. To install the SSL certificate on your Outlook 2007 clients 1. click Next. Distribute the CER file to your remote users by using e-mail.com/fwlink/?LinkId=100605 ] . or other method. In the Certificate Import wizard. 7. click Install Certificate. However.cer file root. 5. and then click Finish. Click Next. select Trusted Root Certification Authorities. there are circumstances when this may not work correctly. 4. To install and enable the SSL certificate by using the Exchange Management Shell To install and enable an SSL certificate.microsoft. you can manually configure a group to distribute certificates that will be trusted by all member computers of the domain. Select Place all certificates in the following store.microsoft. you must install the latest version of the desktop ActiveSync application. To obtain the root certificate from Certificate Services 1. see Add a trusted root certification authority to a Group Policy object [ http://go. Select the Download a CA certificate. and then enter the URL to connect to the Certificate Services administration Web page. you can use the integrated Windows Mobile Device Center in Control Panel but you must first download the Windows Mobile Device Center application. For more information about how to add a trusted root CA to a Group Policy object. To install a certificate on a Windows Mobile device http://technet. If you are running Windows Vista. Open Internet Explorer on a domain-connected computer. 2.cer file to the desktop and name the . and then click Browse. and then click OK. 4.

7. and then click Copy. close Windows Explorer.printer). The second option describes how to use a new third-party certificate. Important: You will not receive a message to let you know that the installation was successful. you will already have a host record in external DNS for the host name that your users will be using to connect to your Exchange messaging infrastructure by using Outlook Web Access. both domain-connected and non-domain-connected clients will be able to successfully connect to the Autodiscover service without receiving security warnings that result from mismatched names. the domain-connected clients will reference the internal URLs for the Exchange services that were automatically set when the Client Access server role was installed. open File Explorer and then locate the folder where you copied the root certificate. you must configure your Exchange services for external access. 5.com. If your certificate includes all the necessary DNS names. mail.80. 4. For more information.White Paper: Exchange 2007 Autodiscover Service Page 15 of 41 1. Double-click the Mobile Device icon to the view the folders on your device. Clients that are not domain-connected will connect by using the External URLs that you entered as part of this procedure. Exchange ActiveSync or Outlook Anywhere.cer file on the local computer. Right-click the folder where you want to copy the root certificate. Summary of Scenario 1 After you configure Exchange to use an SSL certificate that supports multiple DNS names and modify the Exchange services URLs as needed. The host record you create should map to the public IP address that will be used as the entry point to your Client Access server. Step 5: Configure the Exchange Services URLs Now that you have configured SSL for your Autodiscover service deployment scenario. Open Windows Explorer. The first option describes how to use a preexisting certificate that you would export from an existing Exchange server that runs an earlier version of Exchange. clients that are not domain connected will not locate the SCP object and will fail over to using DNS. and then click Paste. and then locate My Computer. Conversely. you must add an additional host record so that Outlook 2007 clients can locate and connect to the Autodiscover service when they use the Outlook Anywhere feature from the Internet.com/en-us/library/bb332063(EXCHG.contoso. for example. http://technet. On your device. Step 1: Install a Certificate on the Default Web Site The procedures in the following section assume that you already have obtained a valid third-party SSL certificate that uses the common name your users will be using to connect to your Exchange Messaging infrastructure. When you are prompted to install the certificate. Domain-connected clients will locate the Autodiscover service by referencing the SCP object. click Yes.microsoft. Return to top Scenario 2: How to Use One Single-Name Certificate This section describes how to use one single-name certificate where the common name of the certificate references the host name users will use to connect to Exchange from the Internet. Step 4: Create the Necessary Host Records in DNS In most cases. For the Autodiscover service to function correctly. For example. 6. 3. see How to Configure Exchange Services for the Autodiscover Service later in this white paper. 2. Right-click the root certificate .contoso.aspx 3/2/2010 . When the root certificate has been copied to the device. mail.com. 8. Select the root certificate.

Right-click Personal. Click Next and then click Finish. and then click the Directory Security tab. 2. e. Locate the certificate that you just imported. b. On the Web Server Certificate Wizard. d.microsoft. and then save it to a location that you will use later. copy the certificate’s thumbprint. and then run the following command: Copy Code Enable-ExchangeCertificate -Thumbprint <thumbprint_of_new_certificate> Services iis Option 2: Using a New Single-Name Certificate Use the Exchange Management Shell on your Client Access server to install and enable your new thirdparty certificate.pfx file option. select the Export the current certificate to a . select Personal Certificate Store. click Properties. expand the top-level Certificates (Local Computer). c. 7. Option 1: Using an Existing SSL Certificate The following procedures describe how to use an existing SSL certificate which you have already implemented for an earlier version of Exchange. 3. Enter the password that you applied to the . Enter a password.printer). export the existing certificate in PFX format by following these steps. see "Step 2: Install the Certificate" in the Scenario 1: How to Use a Certificate That Supports Multiple DNS Names section earlier in this white paper. Click Finish. 4. In the Certificates snap-in for MMC. and then click Next.80. 8.com/en-us/library/bb332063(EXCHG. locate the .pfx file. 6. 5.aspx 3/2/2010 . Select Place all certificates in the following store. right-click Default Web Site. and then click Next. and then select the check box next to Mark this Key as Exportable. Determine the Thumbprint attribute of the imported certificate. f. Click Server Certificate. To use the Exchange Management Shell to install and enable a new third-party SSL certificate http://technet.White Paper: Exchange 2007 Autodiscover Service Page 16 of 41 If you must create a certificate request. and then click Next. and then click Next. To use an existing SSL certificate from an earlier versions version of Exchange 1. In the Certificate Import Wizard. open the Exchange Management Shell and run the following command: Copy Code Get-ExchangeCertificate | fl 9. Name the file. To do this.pfx file that you copied to the Client Access server. Using IIS Manager on your existing earlier version of Exchange. and then click Import. click Browse. In IIS Manager. Import the certificate to the Personal Store by following these steps: a. click All Tasks.

printer). Although this still requires you to add a DNS record in DNS for the Autodiscover service. you must configure your Exchange services for external and internal access. A new feature is available that enables Outlook 2007 to use DNS Service Location (SRV) records to locate the Exchange Autodiscover service [ http://go.xml Step 3: Configure the Exchange Services URLs Now that you have configured SSL for your Autodiscover service deployment scenario. You will use the Set-ClientAccessServer cmdlet to modify this URL so that it points to the new location (FQDN) for the Autodiscover service.contoso. you can address this issue with an Outlook 2007 software update. For more information. When this software update is applied.aspx 3/2/2010 . see How to Configure Exchange Services for the Autodiscover Service later in this white paper. This solution required that you modify the SCP and the internal URLs of the Exchange http://technet.White Paper: Exchange 2007 Autodiscover Service Page 17 of 41 On the Client Access server. Description of the update rollup for Outlook 2007: June 27. If your external DNS provider supports Autodiscover SRV records.microsoft. To obtain this update.80. Step 4: Implementing the Autodiscover SRV Record for Outlook Anywhere Users Because this solution uses one single-name certificate. you will not have to use a certificate that supports multiple DNS names or have to administer a second Web site. 2007 [ http://go. and then run the following command: Copy Code Import-ExchangeCertificate -Path <full path to CER file> | EnableExchangeCertificate -Services iis Step 2: Modify the Service Connection Point By default. open the Exchange Management Shell.microsoft. For more information about this software update for Outlook 2007.com/fwlink/? linkid=3052&kbid=940881 ] . see Microsoft Knowledge Base article 939184. Summary of Scenario 2 In this scenario you installed a single-name certificate where the common name of the certificate references the host name users will use to connect to Exchange from the Internet. the URL for the Autodiscover service stored in the SCP object in Active Directory will reference the internal FQDN for the Client Access server during Exchange 2007 Setup. run the following command: Copy Code Set-ClientAccessServer -identity <servername> AutodiscoverServiceInternalUri https://autodiscover. clients that are not domain-connected that run Outlook 2007 will receive a security warning when they connect to the Autodiscover service.com/autodiscover/autodiscover. for example. To use the Exchange Management Shell to change the internal URL for the Autodiscover service In the Exchange Management Shell. Important: You must repeat this step for every Client Access server that is installed in your Exchange messaging infrastructure.microsoft. see Microsoft Knowledge Base article 940881.contoso.com/en-us/library/bb332063(EXCHG. Outlook 2007 clients will perform an additional check for a DNS SRV record to locate the Autodiscover service that does not require multiple Web sites and IP addresses or a new Unified Communications SSL certificate. mail.com/fwlink/? linkid=3052&kbid=939184 ] .com.

and will also be unsuccessful.com/en-us/library/bb332063(EXCHG. and then connect. where the common name of one certificate references the host name users will use to connect to Exchange from the Internet. This solution is most efficient if the following conditions are true: You do not want the additional administrative overhead of managing multiple Web sites and IP addresses. it will fail over and try to locate the Autodiscover service by using the following URLs using DNS: https://contoso. This solution also requires an Outlook 2007 software update that supports Autodiscover SRV records.xml and then https://autodiscover. a client that is not domain-connected will first try to locate the Autodiscover service by using the SCP object. 2. The certificate does not include a DNS name for the Autodiscover service.White Paper: Exchange 2007 Autodiscover Service Page 18 of 41 services because the FQDN on the certificate differs from the FQDN referenced in the SCP and the internal URLs for the Exchange services. open the properties of your network adapter. you must obtain a second certificate for the Autodiscover Web site. Select Internet Protocol. Because the client cannot to contact Active Directory. The existing certificate will typically be exported from a legacy Exchange server or will be a certificate that was recently purchased. as shown in the following figure. http://technet.contoso. the client will try one more method. click Add. in the TCP/IP Address dialog box. and then. On the Exchange 2007 Client Access Server. To add a second IP address to your network adapter 1. enter an available IP address in the text box for the IP address.80. In either case. 3. and then click Properties.com/autodiscover/autodiscover. Finally.com/autodiscover/autodiscover. This request will then fail over to the HTTP redirect algorithm. Step 1: Adding a Second IP Address to Your Network Adapter The first step in this process involves adding a second IP address to your network adapter on your Client Access server. for example: autodiscover.printer). Return to top Scenario 3: How to Use Two Single-Name Certificates This section describes how to use two single-name certificates. and the common name on the second certificate references the Autodiscover host name. Under IP addresses.microsoft.com. If your external DNS provider supports SRV records. Click Advanced. 4.contoso.xml. It will check for an Autodiscover SRV record in DNS.aspx 3/2/2010 .

This host record should map to a second public IP address that points to another entry point to your Client Access server.microsoft. and then assign it the local IP address that is assigned to the Default Web Site. Enter "mail" for the host name that is being used on the Default Web Site.com. http://technet. contoso. for example. you will already have a host record in external DNS for the host name that users will be using to connect to Exchange from the Internet.80.contoso.com. and then create the host record within that zone. You must also add an additional host record for the Autodiscover service so that Outlook 2007 clients can find and connect to the Autodiscover service when they use Outlook Anywhere from the Internet. Note: If your internal DNS namespace differs from your external namespace.com/en-us/library/bb332063(EXCHG. mail.printer). click Add.aspx 3/2/2010 .contoso. for example. for example.White Paper: Exchange 2007 Autodiscover Service Page 19 of 41 5. mail. and then expand the Forward Lookup Zones container. 3. and then click New Host (A). Step 2: Create Required DNS Records In most cases. To create the required host records in internal DNS 1. 2.com. Open DNS Manager. Right-click your DNS zone. The following procedure describes how to create the host record in internal DNS for the host name that is referenced in the common name of the certificate on the Default Web Site. After you have entered an available IP address. you must create an additional DNS zone that matches your external namespace.

locate the . e.White Paper: Exchange 2007 Autodiscover Service Page 20 of 41 Step 3: Install a Certificate on the Default Web Site The procedures in the following section assume that you already have obtained a valid third-party SSL certificate that uses the common name your users will be using to connect to your Exchange Messaging infrastructure. and then click Next. Click Next. In IIS Manager. b. and then click Next.microsoft. and then click Finish. and then click Next. 7. f. click Browse.com/en-us/library/bb332063(EXCHG. Name the file and save it to a location that you will use later. To use an existing SSL certificate from an earlier version of Exchange 1.pfx file that you copied to the Client Access server. On the Web Server Certificate Wizard.pfx file. and then click Next. Enter a password. export the existing certificate in PFX format by using the following procedure. and then select the check box next to Mark this Key as Exportable. Click Server Certificate. The first option describes how to use a preexisting certificate that you would export from an existing Exchange server that is running an earlier version of Microsoft Exchange. Locate the certificate that you just imported. and then click Import. Import the certificate to the Personal Store by following these steps: a. select Personal Certificate Store. 2. 8. To determine the Thumprint attribute of the imported certificate. Right-click Personal. right-click Default Web Site. select the Export the current certificate to a . see "Step 2: Install the Certificate" in the Scenario 1: How to Use a Certificate That Supports Multiple DNS Names section earlier in this white paper. 5.pfx file option. copy the thumbprint of the certificate. Enter the password that you applied to the . Click Finish. Option 1: Using an Existing SSL Certificate The following procedures describe how to use an existing SSL certificate that you have already implemented for an earlier version of Microsoft Exchange. Select Place all certificates in the following store. The second option describes how to use a new third-party certificate. select All Tasks.80. 6. click Properties and then click the Directory Security tab. d. In the Certificate Import Wizard.aspx 3/2/2010 . 3. 4. open Exchange Management Shell and run the following command: Copy Code Get-ExchangeCertificate | fl 9. If you must create a certificate request. expand the top-level Certificates (Local Computer). Using IIS Manager on your earlier version of Exchange. In the Certificates snap-in for MMC. c.printer). and then run the following command: Copy Code Enable-ExchangeCertificate -Thumbprint <thumbprint_of_new_certificate> Services iis http://technet.

80. Click Advanced. To use the Exchange Management Shell to install and enable a new third-party SSL certificate On the Client Access server.White Paper: Exchange 2007 Autodiscover Service Page 21 of 41 Option 2: Using a New Single-Name Certificate Use the Exchange Management Shell on your Client Access server to install and enable your new thirdparty certificate. expand Web Sites.printer). http://technet. run the following command: Copy Code Import-ExchangeCertificate -Path <full path to CER file> | EnableExchangeCertificate -Services iis Step 4: Configure the Default Web Site The next step in this process is to configure the Default Web Site by using IIS Manager. the IP address will be assigned to All Unassigned. and then click Properties. right-click Default Web Site.aspx 3/2/2010 . and then change the IP assignment for port 443 to the primary IP address.microsoft. in the Exchange Management Shell. 2. click Edit. To configure the Default Web Site by using IIS Manager 1. In IIS Manager. Select your primary IP address and assign it to the Default Web Site. By default. 3.com/en-us/library/bb332063(EXCHG. The following procedure describes this process.

80. and then click Next. click New. In IIS Manager. 2. 4.com/en-us/library/bb332063(EXCHG. http://technet.White Paper: Exchange 2007 Autodiscover Service Page 22 of 41 Step 5: Configure the Autodiscover Web Site The next step in this process is to configure the Autodiscover Web site by using IIS Manager. 3.microsoft. click Next. For example. right-click Web Sites.printer).aspx 3/2/2010 . select the second IP address that you added from the drop-down list. and then select Web Site. "Autodiscover Web Site". enter the name of your Web site. The following procedure describes this process. on the Web Site Description page. Click Next. in the Description field. To configure the new Autodiscover Web site 1. When the Web Site Creation Wizard opens. On the IP Address and Port Settings page. In the Web Site Creation Wizard.

On the Web Site Access Permissions page. 5. 6.80. and then click Finish. http://technet. When the Web Server Certificate Wizard opens. select Assign an existing certificate and then click Next. 3. select c:\Inetpub\wwwroot. In IIS Manager. click Next. On the Server Certificate page. Leave the Anonymous access check box selected. and then click Properties.aspx 3/2/2010 . On the Directory Security tab. you must use IIS Manager to install this certificate on the Autodiscover Web site. right-click the Autodiscover Web Site. Step 6: Installing a Certificate on the Autodiscover Web Site The following procedure in this section assumes that you have already obtained a valid third-party certificate with the common name users will be using to connect to the Autodiscover service. for example. expand Web Sites.printer). click the Server Certificate button. click Browse.com/en-us/library/bb332063(EXCHG. and then click OK. enter the following command to import the second certificate into the Personal Certificate store on the server: Copy Code Import-ExchangeCertificate -path <full_path_to_CER_file> 2.contoso. To use the Exchange Management Shell and IIS Manager to install and enable a new third-party SSL certificate 1. On the Web Site Home Directory page.microsoft. accept the default setting for Read permission.White Paper: Exchange 2007 Autodiscover Service Page 23 of 41 5. In the Exchange Management Shell. 4. Because the Enable-ExchangeCertificate command only works for certificates installed on the Default Web Site.com. and then click Next. autodiscover. click Next.

run the following command: Copy Code New-AutodiscoverVirtualDirectory -WebSite "Autodiscover Web Site" Note: The name of the Web site that you enter is case-sensitive.80. 8. the URL for the Autodiscover service stored in the SCP object in Active Directory will reference the internal FQDN for the Client Access server during Exchange 2007 Setup. On the Certificate Summary page.contoso. Because each http://technet.com/autodiscover/autodiscover.microsoft.xml Step 9: Configure the Exchange Services URLs Now that you have configured SSL for your Autodiscover service deployment scenario. On the Available Certificates page. On the SSL Port page.printer). 7. domain-connected clients will connect to the Autodiscover service that is hosted under the Default Web Site that is found by using the SCP object. Important: You must repeat this step for every Client Access server that you install in your Exchange messaging infrastructure. Summary of Scenario 3 After you configure Exchange to use two single-name certificates and Web sites. Step 8: Modify the SCP Object By default. For more information. click Next and then click Finish to complete the Web Server Certificate Wizard. run the following command: Copy Code Set-ClientAccessServer -identity <servername> AutodiscoverServiceInternalUri https://autodiscover. You will use the Set-ClientAccessServer cmdlet to modify this URL so that it points to the new location (FQDN) for the Autodiscover service. To use the Exchange Management Shell to change the internal URL for the Autodiscover service In the Exchange Management Shell. see How to Configure Exchange Services for the Autodiscover Service later in this white paper. you will use the Exchange Management Shell to create a new Autodiscover virtual directory. accept the default setting of 443 and then click Next. Conversely.aspx 3/2/2010 . you must configure your Exchange services for external and internal access.White Paper: Exchange 2007 Autodiscover Service Page 24 of 41 6. non-domain-connected clients will locate the Autodiscover service by using DNS and connect to the Autodiscover service hosted under the second Web site.com/en-us/library/bb332063(EXCHG. confirm the details are correct. Step 7: Create a New Autodiscover Virtual Directory After you have configured the new Autodiscover Web site in IIS. select the certificate that was provided by your CA for the Autodiscover Web site and then click Next. To use the Exchange Management Shell to create a New Autodiscover virtual directory In the Exchange Management Shell.

microsoft. Step 1: Adding a Second IP Address to Your Network Adapter The first step in this process involves adding a second IP address to your network adapter on your Client Access server.com. click Add and then enter an available IP address. for example.80. mail. all clients should be able to connect without receiving any security warnings. http://technet.printer). Click Advanced. 4. Note: These steps assume that you have already obtained a valid third-party certificate with the common name users will be using to connect to Exchange from the Internet which is installed on the Default Web Site of your Client Access server. open the properties of your network adapter. 2. review the optional information that appears after the following steps. On the Exchange 2007 Client Access server.aspx 3/2/2010 .contoso. Select Internet Protocol and then click Properties. To add a second IP address to your network adapter 1.com/en-us/library/bb332063(EXCHG. 3.White Paper: Exchange 2007 Autodiscover Service Page 25 of 41 Web site contains a valid certificate. Under IP addresses. Note: If you are a large-scale hoster and unable to implement Scenario 2. Return to top Scenario 4: How to Use a Single SSL Certificate and the Autodiscover Redirect Web Site The following section describes how to configure the Autodiscover service when you use one singlename certificate with an SSL Web site in addition to a second Web site responsible for redirecting incoming requests over port 80 to the Autodiscover virtual directory set to accept requests over port 443.

80. mail.printer). 3. Right-click your DNS zone. you will already have a host record in external DNS for the host name users will be using to connect to Exchange from the Internet. To create the required host records in internal DNS 1.microsoft. 2. Open DNS Manager and expand the Forward Lookup Zones container.White Paper: Exchange 2007 Autodiscover Service Page 26 of 41 Step 2: Create Required DNS Records In most cases.com. for example. Enter "autodiscover" and the second IP address which you already assigned to your network adapter. This host record should map to a second public IP address that points to another entry point to your Client Access server. The following procedure describes how to create the required host records in internal DNS. contoso.contoso.com/en-us/library/bb332063(EXCHG. http://technet.com. You must also add an additional host record for the Autodiscover service so that Outlook 2007 clients can find and connect to the Autodiscover service when they use Outlook Anywhere from the Internet. for example. and then click New Host (A).aspx 3/2/2010 .

2.contoso. 3. and then click Edit and change the IP assignment for port 443 to the primary IP address. http://technet.com/en-us/library/bb332063(EXCHG. By default.aspx 3/2/2010 . the IP address will be assigned to All Unassigned. Select your primary IP address and assign it to the Default Web Site. for example. Step 3: Configure the Default Web Site The next step in this process is to configure the Default Web site. and assign it the local IP address which is assigned to the Default Web Site. Create an additional host record for the host name being used on the Default Web Site. right-click the Default Web Site and then click Properties.microsoft.80.com.White Paper: Exchange 2007 Autodiscover Service Page 27 of 41 4. The following procedure describes this process. Click Advanced.printer).mail. In IIS manager. To configure the Default Web Site 1.

http://technet. Autodiscover Web Site. 3.White Paper: Exchange 2007 Autodiscover Service Page 28 of 41 Step 4: Create a New Autodiscover Directory Structure The following procedure describes how to create a new Autodiscover directory structure which will be used by the Autodiscover redirect Web site that you create in the next step. In IIS Manager. 2.xml. In the New Web Site Wizard. select the second IP address that you added and then click Next. Create a subfolder under c:\Inetpub\Autodiscover named Autodiscover. Create a new folder under c:\Inetpub named Autodiscover. open a new Windows Explorer window. right-click Web Sites. and then locate C:\Inetpub. To create a new Autodiscover directory structure 1. 2. Create a new blank text file. In the IP Address and Port Settings window. Step 5: Create the Autodiscover Redirect Web Site To use IIS Manager to create the Autodiscover redirect Web site 1. 3.printer). in the Description box. and then click New Web Site. On the Client Access server.aspx 3/2/2010 . and then click Next. for example. enter the name of the Web site. 4.microsoft.com/en-us/library/bb332063(EXCHG.80. and then name it autodiscover.

and then select Properties.com/en-us/library/bb332063(EXCHG.80. https://mail. browse and then select c:\Inetpub\autodiscover.xml file. Expand the Autodiscover Web Site and select the Autodiscover virtual directory under the Web site. In the Web Site Home Directory window. right-click the autodiscover.microsoft. 7. In the right pane. 6.xml file that is located under the Default Web Site by using the FQDN users will use to connect to Outlook Web Access. 5.aspx 3/2/2010 .com/autodiscover/autodiscover.White Paper: Exchange 2007 Autodiscover Service Page 29 of 41 4. and then click Next. for example.printer). Exchange ActiveSync and Outlook Anywhere. Select the A redirection to a URL option and enter the URL to the Autodiscover.xml.contoso. http://technet. leave the Anonymous access check box selected.

aspx 3/2/2010 . see How to Configure Exchange Services for the Autodiscover Service later in this white paper.80.com/en-us/library/bb332063(EXCHG.xml Step 7: Configure the Web Services URLs Now that you have configured SSL for your Autodiscover service deployment scenario. you should consider configuring the Autodiscover service so http://technet.microsoft. If you expect heavy Web traffic. For more information. To use the Exchange Management Shell to change the internal URL for the Autodiscover service In the Exchange Management Shell.White Paper: Exchange 2007 Autodiscover Service Page 30 of 41 Step 6: Modify the Service Connection Point Object By default. For internal users who use Outlook 2007.contoso.printer). you must configure your Exchange services for external and internal access. you will use the Set-ClientAccessServer cmdlet to modify the URL so that it references the common name of the certificate on the Default Web Site. the URL for the Autodiscover service stored in the SCP object in Active Directory will reference the internal FQDN for the Client Access server during Exchange 2007 Setup. run the following command: Copy Code Set-ClientAccessServer -AutodiscoverServiceInternalUri https://mail. Return to top Optional Deployment Information for a Large-Scale Hosted Environment For large-scale hosted environments. using a single redirect Web site as discussed earlier may not be appropriate.com/autodiscover/autodiscover.

you may even host the Autodiscover service on a dedicated Web server if you want.com/autodiscover/autodiscover.xml. When this occurs. Also. For example. there is no need for any virtual directories and you do not have to set up SSL certificates.contoso. These clients will also be unable to locate Autodiscover by using the following URLs: https://contoso.xml The clients will instead use an alternative method: an HTTP redirect. In the site in the previous figure.no would be called autodiscover.aspx 3/2/2010 .se.xml https://autodiscover.White Paper: Exchange 2007 Autodiscover Service Page 31 of 41 that incoming requests for the Autodiscover service are managed by individual Web sites for each domain.com/autodiscover/autodiscover. After you configure Exchange to use an SSL certificate with redirection.contoso. each with its corresponding DNS entries for each hosted e -mail domain. To configure this kind of scenario.se would be called autodiscover.printer). and the domain named contoso. domain-connected clients will continue locating the Autodiscover service by using the SCP object and connect to the Autodiscover service that is hosted under the Default Web Site. configure redirection for each of your sites by modifying each Web site's autodiscover.com/autodiscover/autodiscover.80. The following figure illustrates the Autodiscover service in a hosted environment.com/en-us/library/bb332063(EXCHG. a warning message is displayed in Outlook 2007 that says: Allow this website to configure server settings? http://technet. On the other hand. you create separate Web sites. the client will receive a redirect from the Autodiscover site to the site that is dedicated to handling e-mail.contoso.microsoft. clients that are not domainconnected will be unable to locate the SCP object and fail over to using DNS.contoso. Note: These sites should be configured only for HTTP (port 80) traffic.xml file so that it points to https://mail. The Autodiscover service in a hosted Exchange environment In this scenario.no. When the redirect happens. the domain named contoso. in IIS Manager. These requests can then be redirected for each hosted domain to the Autodiscover virtual directory under the Default Web Site in Internet Information Services (IIS).

Mailbox. Finally. You cannot suppress the Autodiscover redirect warning in Outlook 2007 [ http://go. Based on these connectivity factors. Return to top Additional Deployment Scenarios and Considerations for the Autodiscover Service If your topology includes multiple sites or forests.White Paper: Exchange 2007 Autodiscover Service Page 32 of 41 Outlook 2007 lets users turn off the option for this warning message to continue to appear. To do this. Additionally. We recommend that you instruct users to turn off the warning message on their Outlook 2007 clients. see Microsoft Knowledge Base article 956528.microsoft. distributed organization that has Active Directory sites that are separated by low -bandwidth network connectivity. you can suppress the Autodiscover redirect warning for HTTP and SRV redirections. Configuring the Autodiscover Service to Use Site Affinity for Internal Communication If you manage a large.com/en-us/library/bb332063(EXCHG.printer). Or. each Active Directory site has Client Access servers and Mailbox servers. the client will connect to the Autodiscover service as you specified. and users in the APAC-contoso site to use the Client Access servers in the APAC-contoso or the Europe-contoso site. After you configure site affinity for the Autodiscover service. you might want to allow users in the US-contoso and Europecontoso sites to use either the Client Access servers in the US-contoso or the Europe-contoso sites. we recommend that you use site affinity for the Autodiscover service for intranet-based traffic.aspx 3/2/2010 . if you are not providing external access to your Exchange messaging infrastructure. The following example uses a topology that includes one forest with three sites: US-contoso A contoso site that is located in North America Europe-contoso A contoso site that is located in Europe APAC-contoso A contoso site that is located in Asia In this example. and Hub Transport server roles installed in the Exchange messaging environment. For Exchange features such as the Availability service and Unified Messaging. Specifying which Active Directory sites are preferred is also known as configuring site scope.com/fwlink/?linkid=3052&kbid=956528 ] . The UScontoso site is connected to the Europe-contoso site by using a high-speed connection. This cmdlet lets you specify the preferred Active Directory sites for connecting to the Autodiscover service on a specific Client Access server. For the Autodiscover service to function correctly for Outlook 2007. You configure site affinity by using the Set-ClientAccessServer cmdlet. you specify which Active Directory sites are preferred for clients to connect to a particular Autodiscover service instance.microsoft. To use site affinity. The US-contoso site is connected to the APAC-contoso site by using a low-speed connection. you must make sure that your Exchange organization meets the following requirements: You must have at least one Exchange 2007 Client Access server installed in each Active Directory site where user's mailboxes reside for your Exchange deployment. other considerations must be addressed when you configure the Autodiscover service to handle these types of Exchange deployments. The following sections describe the scenarios and how to deploy the Autodiscover service in each of these scenarios.80. http://technet. you must also have the Unified Messaging. there are several steps in the Autodiscover deployment process that you will not have to perform. users in the Europe-contoso site to use any Client Access servers in the organization for the Autodiscover service requests. The APAC-contoso site is connected to the Europe-contoso site by using a high-speed connection. the Client Access servers can be reached by using a common internal namespace across all sites.

Copy Code Set-ClientAccessServer -Identity "apac-cas" -AutodiscoverServiceInternalURI "https://internal. use the following command.com/autodiscover/autodiscover. Copy Code Set-ClientAccessServer -Identity "us-cas" -AutodiscoverServiceInternalURI "https://internal. it will use the APAC-CAS SCP record for its Autodiscover requests.printer). Additionally. If an Outlook 2007 client is a member of the Europe-contoso Active Directory site.xml" -AutoDiscoverSiteScope "apac-contoso".xml" -AutoDiscoverSiteScope "us-contoso". the Outlook client can select the SCP record from the list in which the site scope equals "us-contoso".com/en-us/library/bb332063(EXCHG.microsoft."europe-contoso" The previous command ensures the following: If an Outlook 2007 client is a member of the US-contoso Active Directory site. it will use the US-CAS SCP record for its Autodiscover requests. Additionally. To do this. the Outlook client can also use either the US-CAS SCP record or the APAC-CAS SCP record after you run the previous commands. it can use the US-CAS SCP record for its Autodiscover requests. if a user is located in the US-contoso site and tries to locate the Autodiscover service by using Outlook 2007.80. You can configure site scope for users in the APAC-contoso site by configuring the Autodiscover site scope property on the Client Access servers in the APAC-contoso site. the client will not try to use a US-CAS server for Autodiscover requests. http://technet. Therefore. Finally.xml" -AutoDiscoverSiteScope "us-contoso". it can use the APAC-CAS SCP record for its Autodiscover requests. To do this.com/autodiscover/autodiscover. configure the Autodiscover site scope property as follows."europe-contoso" The previous command ensures the following: If an Outlook 2007 client is a member of the APAC-contoso Active Directory site. If an Outlook 2007 client is a member of the Europe-contoso Active Directory site. Additionally. because the Client Access servers in the Europe-contoso Active Directory site are connected to both the US-contoso and APAC-contoso sites by using a high-speed connection. "europe-contoso".aspx 3/2/2010 .contoso. To do this use the following command. you will want to make sure that users in either of those sites can use the Client Access servers in the Europe-contoso site. the client will not try to use an APAC-CAS server for Autodiscover requests. In this case.com/autodiscover/autodiscover. "apac-contoso" The previous command ensures that Outlook 2007 clients that are members of the Europe-contoso Active Directory site use the Europe-CAS SCP record for Autodiscover service requests. the client will either access a US-CAS server or a Europe-CAS server.contoso.contoso. Copy Code Set-ClientAccessServer -Identity "europe-cas" -AutodiscoverServiceInternalURI "https://internal.White Paper: Exchange 2007 Autodiscover Service Page 33 of 41 You can configure site scope for users in the US-contoso site by configuring the Autodiscover site scope correctly on the Client Access servers in the US-contoso Active Directory site.

the account you use must be delegated the Exchange Server Administrator role and membership in the local Administrators group for the target server. if you did not run the previous commands. see Set-ClientAccessServer [ http://technet. you delete the site-scope settings. a user in the US-contoso Active Directory site would potentially use the APACCAS server. and the rights that are required to administer Exchange 2007. you must update Active Directory in the user account forest to include the information that Active Directory requires to enable the client to access the resource forest. The following sections describe how the Autodiscover service is used in these two deployment scenarios. Before You Begin To perform the following procedure.microsoft.80. on the other hand. Europe-contoso. For example.microsoft. If.printer).xml" AutoDiscoverSiteScope "SiteName" For more information about syntax and parameters. http://technet. or the US-CAS server. see Permission Considerations [ http://technet.White Paper: Exchange 2007 Autodiscover Service Page 34 of 41 If you do not alter the site-scope settings for the Autodiscover service. user accounts reside in one forest (known as a user account forest) and Microsoft Exchange is deployed in a separate forest (known as a resource forest).com/en-us/library/bb125157(EXCHG. Return to top How to Configure the Autodiscover Service to Use Site Affinity You can use the Set-ClientAccessServer cmdlet in the Exchange Management Shell to configure the Autodiscover service to use site affinity on a computer that is running Exchange 2007 that has the Client Access server role installed. The Autodiscover SCP pointer record includes the LDAP URL of the resource forest that the client will use to locate the Autodiscover service in the resource forest. The Outlook client contacts Active Directory in the user account forest to locate the URL for the Autodiscover service. Two of the multiple forest deployment scenarios are the resource forest topology and the multiple trusted forest topology. Configuring the Autodiscover Service in a Resource Forest Topology If you use a resource forest topology.com/en-us/library/aa996881 (EXCHG. For more information about permissions. delegating roles. the Outlook client will only use the Client Access servers in its local site (US-contoso. To do this. Return to top Configuring the Autodiscover Service for Multiple Forests You can deploy Microsoft Exchange by using multiple forests. To use the Exchange Management Shell to configure site affinity for the Autodiscover service Run the following command: Copy Code Set-ClientAccessServer -Identity "ServerName" AutodiscoverServiceInternalURI "https://internalsitename/autodiscover/autodiscover.aspx ] . APAC-contoso).80). Outlook will randomly select an SCP record for Autodiscover requests.microsoft. the Europe-CAS server.aspx 3/2/2010 . you must create an Autodiscover SCP pointer record in Active Directory in the user account forest.com/en-us/library/bb332063(EXCHG. Because the service is hosted in the resource forest. the following will occur: 1. This could result in a poor experience for the end user because the request may go out of the user's Active Directory site and use a low quality network connection.aspx ] .80). In this scenario.

com/en-us/library/bb332063(EXCHG. the Outlook client will retrieve an SCP record at random.microsoft. except that the Autodiscover SCP object must be configured in all forests. you will not have to extend the schema or manually create the Autodiscover SCP record container in the user forest.White Paper: Exchange 2007 Autodiscover Service Page 35 of 41 2. the user accounts and Microsoft Exchange are deployed in multiple forests. you can update DNS in the user forest with a host record that points to the internal IP address of the Client Access server in the resource forest where Autodiscover is hosted.80. the Outlook client will retrieve an SCP record at random. Outlook binds to the target forest by using the LDAP URL and retrieves the SCP records. Depending on your SCP record configuration. and then run the Export-AutodiscoverConfig cmdlet in the resource forest that contains the Client Access servers that provide the Autodiscover service against the target forests. Note: To synchronize Active Directory sites between forests. you must update Active Directory so that users who are running Microsoft Office Outlook 2007 in one forest can access the Client Access servers in the remote (or target) forest to use the Autodiscover service. you must extend the schema in the user forest by running Exchange 2007 Setup with the /PrepareAD or /PrepareSchema switch.microsoft. Note: If you do not want to extend the schema in the user forest. Also. Return to top How to Configure the Autodiscover Service When You Use Multiple Forests If your Exchange deployment has two or more trusted forests. and then clicking Windows Support Tools. Then select Support Tools Help. To configure the Autodiscover SCP object in the multiple forest topology. Exchange 2007 features such as the Availability service and Unified Messaging rely on the Autodiscover service to access user accounts across forests. the following will occur: a. http://technet. 4. In this scenario. This will configure the SCP information for the Autodiscover pointer in Active Directory. 3.aspx 3/2/2010 . Or. The Outlook client connects to the URL that is specified in the SCP record that was obtained and retrieves the required user profile settings by using the Autodiscover service. you can manually create the root Autodiscover SCP record container in the user forest. Note: If you will be manually creating the Autodiscover SCP record container. clicking Programs. if the Active Directory site topology is not being replicated between the user account forest and the resource forest. To do this. you can access the Active Directory Service Interfaces (ADSI) Edit tool by going to the Start menu. you must install the Windows Server 2003 Support Tools from the Windows Server 2003 CD. Important: If you install Exchange 2007 Service Pack 1 (SP1). If the SCP records do not have a site scope that matches the Outlook client's site. the Autodiscover service must be available to users across multiple trusted forests. After the Autodiscover SCP record container is installed.com/fwlink/?LinkId=21177 ] . run the Export-AutoDiscoveryConfig cmdlet from each forest that has the Autodiscover service against each target forest where Microsoft Exchange is deployed. the account you use must be delegated the Exchange Server Administrator role and membership in the local Administrators group for the target server.printer). see "Synchronizing Sites and Subnets" in Multiple Forest Considerations in Windows 2000 and Windows Server 2003 [ http://go. Configuring the Autodiscover Service in a Multiple Trusted Forest Topology In the multiple trusted forest scenario. This scenario resembles the resource forest scenario. Before You Begin To perform the following procedures. which requires Microsoft Identity Lifecycle Manager 2007 synchronization. If the account forest Active Directory sites are in the resource forest. b. the Outlook client will retrieve the SCP records for the Outlook client's Active Directory site.

Return to top Managing the Autodiscover Service Managing the Autodiscover service for users includes performing tasks such as making sure that users will be able to use the Autodiscover service after their mailboxes are moved from one forest to another forest. On an Exchange 2007 Client Access server in the resource forest.aspx ] .com /prepareschema Or. see Permission Considerations [ http://technet. create the "Microsoft Exchange Autodiscover" container in the user account forest by following these steps: Start ADSI Edit.DC=<root domain>.80). Expand the Configuration container. click New. and the rights that are required to administer Exchange 2007. Right-click CN=Services. Expand the CN=Services container.80). Expand CN=Configuration. and then click Next. Under Select a Class. select Container.microsoft. enter the user name and password for the account that has the required permissions for the target forest in the variable "$a" by running the following command: Copy Code $a = Get-Credential 2.aspx 3/2/2010 . Allow Active Directory replication to occur before you continue with the next step. and then select Object. On an Exchange 2007 Client Access server in the resource forest. Click Finish. enter "Microsoft Exchange Autodiscover".printer). and then click Next.microsoft.com/en-us/library/aa996881 (EXCHG.aspx ] . To use the Exchange Management Shell to configure the Autodiscover service for multiple forests 1.com/en-us/library/aa998832(EXCHG. Next to Value. http://technet.com/en-us/library/bb332063(EXCHG. see Export-AutoDiscoverConfig [ http://technet.microsoft. run the following command: Copy Code Export-AutoDiscoverConfig -DomainController DomainControllerName TargetForestDomainController TargetForestDomainControllerName TargetForestCredentials $a -MultipleExchangeDeployments $true For more information about syntax and parameters. delegating roles.80.White Paper: Exchange 2007 Autodiscover Service Page 36 of 41 For more information about permissions. To use ADSI Edit to extend the schema in the user forest Run Exchange 2007 Setup on a server in the user forest by using the following command: Copy Code Setup.

com</EMailAddress>\r\n <AcceptableResponseSchema>http://schemas.contoso. For example. When you configure a mail contact.aspx 3/2/2010 .microsoft.0" encoding="utf-8" ?>\r\n <Autodiscover xmlns="http://schemas. you must configure a mail contact in the original forest where the user's mailbox resided.com/en-us/library/bb332063(EXCHG. For this example. trusted forests and the mailbox for a user is kwekua@contoso.80.com/exchange/autodiscover/outlook/requestschema/2006">\r <Request>\r\n <EMailAddress>kwekua@contoso.com' -Name 'Kweku Ako Adjei' -Alias 'kwekua' -OrganizationalUnit 'contoso. The client will then try to contact the Autodiscover service by using the new e-mail address against the new forest.contoso. Copy Code New-MailContact -ExternalEmailAddress 'SMTP:kwekua@fourthcoffee. This user originally resided in the forest named contoso. the following request is sent to the Outlook 2007 client.printer). contoso. you have to set a contact in mail1.com and uses the contoso.com/exchange/autodiscover/responseschema/2006"><Response xmlns="http://schemas. when the user connects to contoso.com by using the following command in the Exchange Management Shell. Depending on your deployment. the two forests must be trusted.White Paper: Exchange 2007 Autodiscover Service Page 37 of 41 The following sections describe the common management tasks for the Autodiscover service.com.com/Users' -FirstName 'Kweku' Initials '' -LastName 'Ako Adjei' After you configure the contact.com credentials. <?xml version="1. the user will authenticate to the original forest where the mailbox resided. For the Autodiscover service to handle this move.com and fourthcoffee. and the user will receive a redirect that uses the new e-mail address. How to Configure the Autodiscover Service for Cross Forest Moves You can use the Exchange Management Shell to configure your Microsoft Exchange deployment to handle mailboxes that are moved from one forest to another for the Autodiscover service.com/exchange/autodiscover/outlook/res </Request>\r\n </Autodiscover> The Outlook 2007 client will receive the following redirect response from contoso. <?xml version="1.contoso.contoso.com/exchange/autodiscover/outlook/responseschema/2006a"> http://technet.com. For a cross-forest mailbox move.contoso.com and was moved to the forest named fourthcoffee.com are separate.com.0" encoding="utf-8"?>\r\n <Autodiscover xmlns="http://schemas. some of these procedures may not have to be performed.

When you enable Outlook Anywhere. they will be unable to use Exchange features such as Out of Office functionality.com/en-us/library/bb124519(EXCHG. the Autodiscover service information that is provided to the Microsoft Office Outlook 2007 client may be incorrect for clients that are connecting from outside your network. Unified Messaging (UM).com/en-us/library/bb332063(EXCHG. for the Autodiscover service on a Microsoft Exchange 2007 computer that has the Client Access server role installed.aspx 3/2/2010 . If you do not configure the external URL values.com' -Name 'Kweku Ako Adjei' -Alias 'kwekua' -OrganizationalUnit 'contoso. the account you use must be delegated the Exchange Server Administrator role and membership in the local Administrators group for the target server. To use the Exchange Management Shell to create a new mail contact for the Autodiscover service to handle cross-forest mailbox moves Run the following command: Copy Code New-MailContact -ExternalEmailAddress 'SMTP:kwekua@fourthcoffee.printer). you must also configure external access to Microsoft Exchange services for the Autodiscover service. For more information about permissions. Unified Messaging. and the offline address book. Return to top How to Configure Exchange Services for the Autodiscover Service This section explains how to configure Microsoft Exchange services.com/Users' FirstName 'Kweku' -Initials '' -LastName 'Ako Adjei' For more information about syntax and parameters. see New-MailContact [ http://technet. or offline address book downloads. see Permission Considerations [ http://technet.microsoft. This includes the URLs for the Availability service. and the rights that are required to administer Exchange 2007. such as the Availability service.com forest.80).microsoft. delegating roles.contoso. http://technet.80.com/en-us/library/aa996881 (EXCHG.White Paper: Exchange 2007 Autodiscover Service Page 38 of 41 <Account>\r\n <Action>redirectAddr</Action>\r\n <RedirectAddr>kwekua@fourthcoffee. They may be able to connect to their Microsoft Exchange mailbox. the Availability service.aspx ] . Before You Begin To perform the following procedure on an Exchange 2007 Client Access server. Exchange Web Services.microsoft. However.aspx ] .com</RedirectAddr>\r\n </Account>\r\n </Response></Autodiscover> The user will then be able to connect to the Autodiscover service by using this new e-mail address in the mail2.80).

as discussed in Scenario 1: Using a Certificate That Supports Multiple DNS Names earlier in this white paper. and encryption settings for the following Web services: Outlook Anywhere Offline address book Unified Messaging Exchange Web Services If you performed a custom installation of Exchange 2007 and you will not be using an Exchange service such as Unified Messaging.contoso. To use the Exchange Management Shell to configure the external host name for Outlook Anywhere for the Autodiscover service Run the following command: Copy Code Enable-OutlookAnywhere -Server CAS01 -ExternalHostname "mail.com/en-us/library/bb332063(EXCHG. If you have configured the Autodiscover service by following Scenario 2: Using One Single-Name Certificate or Scenario 3: Using Two SingleName Certificates. you will not have to complete the procedure to configure the external URL for Unified Messaging for the Autodiscover service later in this section.printer).com/en-us/library/bb124993(EXCHG. Important: The following procedures assume that you are using a Unified Communications certificate that supports multiple DNS names. authentication. the external URL values are NULL and must be configured by using the virtual directory cmdlet for each component.microsoft. if you are not providing external access to your Exchange services. Before You Begin To perform the following procedures.asmx. the internal URL is configured by Microsoft Exchange Setup and references the internal FQDN of the Client Access server. In this section.microsoft.contoso. For more information about permissions.aspx 3/2/2010 . delegating roles. you will configure external host name.com/OAB -RequireSSL:$true http://technet.White Paper: Exchange 2007 Autodiscover Service Page 39 of 41 Generally. To use the Exchange Management Shell to configure the external URL for the offline address book for the Autodiscover service Run the following command: Copy Code Set-OABVirtualDirectory -identity "CAS01\OAB (Default Web Site)" externalurl https://mail.com" ExternalAuthenticationMethod "Basic" -SSLOffloading:$False For more information about syntax and parameters. However. you must set the internal URL to https://mail. see Permission Considerations [ http://technet. and the rights that are required to administer Exchange 2007.80). see Enable-OutlookAnywhere [ http://technet.aspx ] .microsoft.80. For example.com/ews/exchange. the account you use must be delegated the Exchange Server Administrator role and membership in the local Administrators group for the target server. Additionally.80). you can safely ignore these procedures.com/en-us/library/aa996881 (EXCHG.aspx ] .contoso. you must also modify the internal URL of each Exchange service so that the FQDN in the URL references the common name of the certificate on the Default Web Site.

see Set-WebServicesVirtualDirectory [ http://technet.contoso.contoso.com/fwlink/?LinkId=80756 ] . Note: If Exchange 2007 will be deployed behind an ISA Server computer.aspx 3/2/2010 .White Paper: Exchange 2007 Autodiscover Service Page 40 of 41 For more information about syntax and parameters. Use this information to help you define a deployment strategy for the Autodiscover service to provide your users with the Microsoft Exchange features that you enable. Return to top Autodiscover and ISA Server 2006 When an Exchange 2007 Client Access server is deployed with an advanced firewall server such as ISA Server 2006.printer).com/en-us/library/bb124707(EXCHG.80).microsoft. see the following topics: http://technet.microsoft. To use the Exchange Management Shell to configure the external URL for Exchange Web Services for the Availability service and Out of Office services Run the following command: Copy Code Set-WebServicesVirtualDirectory -identity "CAS01\EWS (Default Web Site)" externalurl https://mail. you will typically create a Web Publishing rule for each application and use the same Web listener because listeners in ISA Server 2006 can handle multiple authentication methods. To use the Exchange Management Shell to configure the external URL for Unified Messaging for the Autodiscover service Run the following command: Copy Code Set-UMVirtualDirectory -identity "CAS01\UnifiedMessaging (Default Web Site)" -externalurl https://mail. see the documentation about how to configure ISA Server in Publishing Exchange Server 2007 with ISA Server 2006 [ http://go.com/EWS/Exchange.80.80). see Set-OABVirtualDirectory [ http://technet.aspx ] .aspx ] .microsoft.microsoft.80). Conclusion This white paper provides the necessary information to enable you to deploy and configure the Autodiscover service for your users.com/en-us/library/bb332063(EXCHG.com/en-us/library/aa997233(EXCHG.microsoft. Additional Information For more information about Exchange 2007 features.asmx BasicAuthentication:$True For more information about syntax and parameters.com/en-us/library/bb124335(EXCHG. Notice that the rule you create for Outlook Anywhere has the option to include the Autodiscover virtual directory.aspx ] . see Set-UMVirtualDirectory [ http://technet.asmx BasicAuthentication:$True For more information about syntax and parameters.com/UnifiedMessaging/Service.

80).80).80.aspx 3/2/2010 .80).printer).microsoft.80).com/en-us/library/bb232134 (EXCHG.com/en-us/library/bb232155 (EXCHG.White Paper: Exchange 2007 Autodiscover Service Page 41 of 41 Unified Messaging [ http://technet.aspx ] Planning for Client Access Servers [ http://technet.microsoft.com/en-us/library/bb232184 (EXCHG.com/en-us/library/bb332063(EXCHG.microsoft.aspx ] Understanding Offline Address Books [ http://technet.aspx ] Tags: autodiscover Community Content http://technet.com/en-us/library/bb123911(EXCHG.microsoft.aspx ] Understanding the Availability Service [ http://technet.microsoft.

Sign up to vote on this title
UsefulNot useful