Applies to: Exchange Server 2013

Topic Last Modified: 2012-12-10

With federated sharing, users in your on-premises Exchange organization can share free/busy calendar information with recipients in other Exchange organizations that are also configured for federated sharing. Free/busy sharing can be enabled between two organizations running Exchange 2013 and also between organizations with a mixed Exchange deployment. To learn more about federated sharing, see Sharing.

This topic provides a summary of the requirements and configuration steps necessary to enable free/busy sharing between different types of the following common Exchange deployments:

For additional management tasks related to federated sharing, see Federation Procedures.

What do you need to know before you begin?

  • Estimated time to complete each procedure: 2 hours.

  • Procedures in this topic require specific permissions. See each procedure for its permissions information.

  • Before you perform the procedures in this topic, make sure you understand the limitations associated with sharing free/busy information across Exchange organizations. For details, see Limitations of free/busy sharing.

  • For information about keyboard shortcuts that may apply to the procedures in this topic, see Keyboard Shortcuts in the Exchange Admin Center.

What do you want to do?

Configure free/busy sharing between Exchange 2013 organizations

Complete the steps in Configure Federated Sharing for both organizations.

Configure free/busy sharing between Exchange 2013 and Exchange 2010 SP2 organizations

Configure free/busy sharing between Exchange 2013 and Exchange 2007 organizations

  • Configure federated sharing for the Exchange 2013 organization. Complete the steps in Configure Federated Sharing.

  • Complete the following steps in the Exchange 2007 organization:

    1. Add an Exchange 2010 SP2 server

      An Exchange 2010 SP2 server with the Client Access server role must be installed in the Exchange 2007 organization. If you have existing Exchange 2010 servers, they should also be updated to Exchange 2010 SP2. For information about installing Exchange 2010 in an Exchange 2007 organization, see Exchange 2007 - Planning Roadmap for Upgrade and Coexistence.

    2. Configure federated delegation

      Configure federated delegation for the Exchange 2007 organization. On an Exchange 2010 SP2 server in the Exchange 2007 organization, complete the steps in Configure federated delegation.

    3. Configure Active Directory synchronization

      Active Directory synchronization must be configured for all users that need to share free/busy information between the organizations. You can either configure the Active Directory synchronization manually or use an automated Active Directory synchronization service. To configure Active Directory synchronization, see the steps below:

    4. Create an availability address space

      Create an availability address space for the remote Exchange 2013 organization that directs availability requests from Exchange 2007 mailbox users to the Exchange 2010 SP2 Client Access server in the Exchange 2007 organization. This setting enables user availability requests from Exchange 2007 users for users in the remote Exchange 2013 organization to be proxied through the Exchange 2010 Client Access server in the Exchange 2007 organization. The Exchange 2010 Client Access server in the Exchange 2007 organization uses the federation trust and organization relationship to send the availability requests to the remote Exchange 2013 organization forest availability endpoint.

      To configure the availability address space, on the Exchange 2010 Client Access server in the Exchange 2007 organization, run the following command in the Exchange Management Shell:

      Copy Code 
      Add-AvailabilityAddressSpace -AccessMethod InternalProxy -ProxyUrl https://<Exchange 2010 CAS server name>/ews/exchange.asmx -ForestName <SMTP domain of the remote Exchange organization> -UseServiceAccount $True
      For detailed syntax and parameter information, see Add-AvailabilityAddressSpace

Configure Free/Busy Sharing Between Exchange 2013 and Exchange 2003 Organizations

  • Configure federated sharing for the Exchange 2013 organization. Complete the steps in Configure Federated Sharing.

  • Complete the following steps in the Exchange 2003 organization:

    1. Add Exchange 2010 SP2 server.

      An Exchange 2010 SP2 server with the Client Access server role must be installed in the Exchange 2003 organization. If you have existing Exchange 2010 servers, they should also be updated to Exchange 2010 SP2. For information about installing Exchange 2010 in an Exchange 2003 organization, see Exchange 2003 - Planning Roadmap for Upgrade and Coexistence.

      Warning:
      For free/busy sharing to work properly between Exchange 2013 and Exchange 2003 organizations, the OU=EXTERNAL (FYDIBOHF25SPDLT) public folder must exist in the public folder hierarchy. This folder is automatically created on the Exchange 2010 Mailbox server in the Exchange 2003 organization only if you select the option to create public folders as part of configuring client settings for Outlook 2003 support during Exchange 2010 Setup. Additionally, this option is presented during the setup process only if the Exchange 2010 Mailbox server is the first Mailbox server installed in the organization. If the OU=EXTERNAL (FYDIBOHF25SPDLT) public folder wasn’t created during Setup, you must manually create it. For details about how to create this public folder, see How to troubleshoot Free/Busy issues when you use Exchange Federation in the Microsoft Office 365 for enterprises environment.
    2. Configure federated delegation.

      Configure federated delegation for the Exchange 2003 organization. On an Exchange 2010 SP2 server in the Exchange 2003 organization, complete the steps in Configure federated delegation.

    3. Configure Active Directory synchronization.

      Active Directory synchronization must be configured for all users that need to share free/busy information between the organizations. You can either configure the Active Directory synchronization manually or use an automated Active Directory synchronization service. To learn more about Active Directory synchronization, see Forefront Identity Management.

    4. Configure public folders for free/busy sharing in your Exchange 2003 organization.

      Complete the following steps on an Exchange 2003 server:

      • In Exchange System Manager, in the console tree, navigate to Administrative Groups > First Administrative Group > Servers.

      • Select your Exchange 2003 server, and then navigate to First Storage Group > Public Folder Store > Public Folders > Schedule+ FREE BUSY.

      • In the action pane, select the OU=EXTERNAL (FYDIBOHF25SPDLT) folder for the First Administrative Group.

      • Right-click the OU=EXTERNAL (FYDIBOHF25SPDLT) folder, and then click Properties.

      • In OU=EXTERNAL (FYDIBOHF25SPDLT) Properties, select the Replication tab.

      • To replicate the OU=EXTERNAL (FYDIBOHF25SPDLT) folder to the Exchange 2010 Client Access/Mailbox server, click Add.

      • In Select a Public Folder Store, select the Public Folder Database for the Exchange 2010 Client Access/Mailbox server, and then click OK.

        Note:
        By default, Exchange uses the replication schedule set on the public folder database.
      • Click OK to close OU=EXTERNAL (FYDIBOHF25SPDLT) Properties and save your changes.

      • Complete the same steps above for the OU=Exchange Administrative Group (FYDIBOHF23SPDLT) folder.

        Warning:
        Depending on the size of your public folders, this replication could take several hours to complete.
      • After the OU=EXTERNAL (FYDIBOHF25SPDLT) and OU=Exchange Administrative Group (FYDIBOHF23SPDLT) public folders have replicated to the Exchange 2010 Client Access/Mailbox server, you must remove the replicas for these public folders on the Exchange 2003 server.

    5. Modify the LegacyExchangeDN parameter

      Modify the LegacyExchangeDN parameter on all mail-enabled objects in the Exchange 2003 organization that reference the remote Exchange 2013 organization. Change the existing organizational unit (OU) value for the mail-enabled object to External (FYDIBOHF25SPDLT). For example, LegacyExchangeDN=/o=First Organization/ou=External (FYDIBOHF25SPDLT)/cn=Recipients/cn=User Name.

      To modify mail-enabled objects in the Exchange 2003 organization, you can use either the Active Directory Service Interfaces Editor (ADSI Edit) tool or the Microsoft Exchange Server LegacyDN Utility.