Topic Last Modified: 2010-12-07
The Lync Server 2010 ExUM Routing application supports integration with an on-premises Exchange Unified Messaging (UM) deployment, with Exchange UM hosted by a service provider, or with a combination of the two. The following diagram shows all three possibilities.
The following modes are supported:
- On-premises deployment: Lync Server and Exchange UM are
both deployed on local servers within your enterprise.
- Cross-premises deployment: Lync Server is deployed on
local servers within your enterprise and Exchange UM is hosted in
an online service provider’s facility, such as a Microsoft Exchange
Online data center.
- Mixed deployment: Your Lync Server deployment has some
user mailboxes homed on local Exchange servers within your
enterprise and some mailboxes homed in a hosted Exchange service
Note: The mixed deployment can be used as a transitional solution during evaluation and phased migration of users to hosted Exchange UM, or a permanent solution if you opt to keep some users’ Exchange UM services on-premises after transferring others.
Shared SIP Address Space
To integrate Lync Server with an on-premises Exchange UM deployment, you grant Lync Server permission to read Exchange UM Active Directory Domain Services objects. This approach does not work for integration with hosted Exchange UM, however, because Lync Server and Exchange UM are installed in separate forests with no trust between them.
To integrate Lync Server with hosted Exchange UM, you must configure a shared SIP address space (also called a split domain). In this configuration, the same SIP domain address space is available to both Lync Server and the hosted Exchange UM service provider.
|Use of the shared SIP address space is similar to the approach used in a cross-premises Lync Server environment, in which some users are homed in the on-premises deployment and some are homed in a hosted deployment (such as Microsoft Lync Online 2010). The SIP domain is split between them. When you integrate Lync Server with hosted Exchange UM, ensure that you include the Exchange UM service provider in the shared SIP address space.|
To configure the shared SIP address space for integrating with an Exchange UM service provider, you need to configure your Edge Server as follows:
- Configure the Edge Server for federation by running the
Set-CsAccessEdgeConfiguration cmdlet to set the following
- UseDnsSrvRouting specifies that Edge Servers will rely
on DNS SRV records when sending and receiving federation
- AllowFederatedUsers specifies whether internal users are
allowed to communicate with users from federated domains. This
property also determines whether internal users can communicate
with users in a split domain scenario.
- EnablePartnerDiscovery specifies whether Lync Server
will use DNS records to try to discover partner domains that are
not listed in the Active Directory allowed domains list. If False,
Lync Server will federate only with domains that are found on the
allowed domains list. This parameter is required if you use DNS
service routing. In most deployments, the value is set to false to
avoid opening up federation to all partners.
- UseDnsSrvRouting specifies that Edge Servers will rely on DNS SRV records when sending and receiving federation requests.
- Replicate the Central Management store to the Edge Server and
verify the replication. For details, see Export Your Topology and
Copy It to External Media for Edge Installation in the
- Configure a hosting provider on the Edge Server by
running the New-CsHostingProvider cmdlet to set the
- Identity specifies a unique string value identifier for
the hosting provider that you are creating, for example, Hosted
- Enabled indicates whether the network connection between
your domain and the hosting provider is enabled. Must be set to
- EnabledSharedAddressSpace indicates whether the hosting
provider will be used in a shared SIP address space scenario. Must
be set to True.
- HostsOCSUsers indicates whether the hosting provider is
used to host Lync Server accounts. Must be set to False.
- ProxyFQDN specifies the fully qualified domain name
(FQDN) for the proxy server used by the hosting provider, for
example, proxyserver.fabrikam.com. Contact your hosting
provider for this information. This value cannot be modified. If
the hosting provider changes its proxy server, you will need to
delete and then recreate the entry for that provider.
- IsLocal indicates whether the proxy server used by the
hosting provider is contained within your Lync Server topology.
Must be set to False.
- Identity specifies a unique string value identifier for the hosting provider that you are creating, for example, Hosted Exchange UM.