Components and Topologies for On-Premises Unified Messaging
Topic Last Modified: 2011-01-26
This topic describes the Microsoft Exchange Server components required to provide Exchange Unified Messaging (UM) features to Microsoft Lync Server 2010 communications software Enterprise Voice users whose mailboxes are homed on an on-premises Microsoft Exchange deployment. It also describes the supported topologies for on-premises Exchange UM integration.
Exchange Server Components
To provide the Exchange UM features and services described earlier in this section to Enterprise Voice users in your organization, you must deploy the following Microsoft Exchange server roles:
Mailbox Server, which hosts user mailboxes and provides a single storage location for email and voice mail.
Hub Transport Server, which routes email messages from the Exchange UM Server to user mailboxes.
Client Access Server, which hosts client protocols and services, such as Post Office Protocol version 3 (POP3), Internet Message Access Protocol 4 (IMAP4), Secure Hypertext Transfer Protocol (HTTPS), Outlook Anywhere, Availability service, and Autodiscover service. The Client Access Server also hosts Web services.
Exchange UM Server, which connects Microsoft Exchange Server with Lync Server 2010.
You can deploy Lync Server and Exchange UM in the same forest or multiple forests. If the deployment spans multiple forests, you must perform the Exchange integration steps for each Exchange UM forest. Furthermore, you must configure each Microsoft Exchange forest to trust the Lync Server forest and the Lync Server forest to trust each Exchange UM forest. In addition to this forest trust, the Exchange UM settings for all users must be set on the user objects in the Lync Server forest.
Lync Server supports the following topologies for Exchange UM integration:
Single domain (that is, a single forest with a single domain). Lync Server, Microsoft Exchange, and users all reside in the same domain.
Multiple domain (that is, a root domain with one or more child domains). Lync Server, and Microsoft Exchange servers are deployed in different domains from the domain where you create users. Exchange UM servers can be deployed in different domains from the Lync Server pool they support.
Multiple forest (that is, resource forest). Lync Server is deployed in a single forest, and then users are distributed across multiple forests. The users’ Exchange UM attributes must be replicated over to the Lync Server forest.
Exchange can be deployed in multiple forests. Each Exchange organization can provide Exchange UM to its users, or the Exchange UM servers can be deployed in the same forest as Lync Server.