Topic Last Modified: 2011-05-02

Important:
If you want to use Microsoft Exchange Server Unified Messaging (UM) to provide call answering, Outlook Voice Access, or auto-attendant services for Enterprise Voice users, read the information in “On-Premises Exchange Unified Messaging Integration” in the Planning documentation, and then follow the instructions in this section.

Configuring Exchange Server Unified Messaging to work with Enterprise Voice consists of the following tasks:

Requirements and Recommendations

Before you begin, the documentation in this section assumes that you have deployed the following Exchange server roles: Hub Transport, Client Access, Mailbox, and Unified Messaging.

For details about deploying Microsoft Exchange Server 2007 Service Pack 1 (SP1), see the Exchange Server 2007 TechNet Library at http://go.microsoft.com/fwlink/?LinkID=129672.

For details about deploying Microsoft Exchange Server 2010, see the Exchange Server 2010 TechNet Library at http://go.microsoft.com/fwlink/?LinkID=186202.

Also note the following:

  • If Exchange UM is installed in multiple forests, the Exchange integration steps must be performed for each UM forest. In addition, each UM forest must be configured to trust the forest in which Lync Server is deployed, and the forest in which Lync Server is deployed must be configured to trust each UM forest.

  • Integration steps are performed on both the server running Exchange Server Unified Messaging and the server running Lync Server. You should perform the Exchange Server Unified Messaging integration steps before you perform the Lync Server integration steps.

    Note:
    To see which integration steps are performed on which servers and by which administrator roles, see Deployment Process for Integrating On-Premises Unified Messaging and Lync Server 2010.

The following tools must be available on each server running Exchange UM:

  • Exchange Management Shell

  • The script exchucutil.ps1, which performs the following tasks:

    • Creates a UM IP gateway for each Lync Server.

    • Creates a hunt group for each gateway. The pilot identifier of each hunt group specifies the UM SIP URI dial plan used by the Front End pool or Standard Edition server that is associated with the gateway.

    • Grants Lync Server permission to read Exchange UM objects in Active Directory Domain Services (AD DS).

In This Section