Topic Last Modified: 2010-11-07
To provide your Lync Server 2010 users with voice mail capabilities on hosted Exchange Unified Messaging (UM), you must perform the following configuration tasks on the Edge Server:
- Configure the Edge Server for federation.
- Replicate Central Management store data to the Edge Server and
verify the replication.
- Create a hosting provider on the Edge Server.
For details, see the Lync Server Management Shell documentation for the following cmdlets:
- Set-CsAccessEdgeConfiguration
- New-CsHostingProvider
To configure the Edge Server for federation
-
Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Management Shell.
-
Run the Set-CsAccessEdgeConfiguration cmdlet to configure the server for federation. For example, run:
Copy Code Set-CsAccessEdgeConfiguration -UseDnsSrvRouting -AllowFederatedUsers 1 -EnablePartnerDiscovery 0
The preceding example sets the following parameters:
- UseDnsSrvRouting specifies that Edge Servers will rely
on DNS SRV records when sending and receiving federation
requests.
- 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 not listed
in the Active Directory allowed domains list. If False, Lync Server
will only federate with domains 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.
To replicate data to the Edge Server and verify the replication
-
Replicate the Central Management store data to the Edge Server. For the procedure, see Export Your Topology and Copy It to External Media for Edge Installation.
-
Verify that the replication to the Edge Server is complete. For the procedure, see Verify Connectivity Between Internal Servers and Edge Servers.
To create a hosting provider on the Edge Server
-
Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Management Shell.
-
Run the New-CsHostingProvider cmdlet to configure the hosting provider. For example, run:
Copy Code New-CsHostingProvider -Identity Fabrikam.com -Enabled $True -EnabledSharedAddressSpace $True -HostsOCSUsers $False -ProxyFQDN "proxyserver.fabrikam.com" -IsLocal $False
The preceding example sets the following parameters:
- Identity specifies a unique string value identifier for
the hosting provider you are creating, in this example,
Fabrikam.com. Note that the command will fail if an existing
provider has already been configured with that Identity.
- Enabled indicates whether the network connection between
your domain and the hosting provider is enabled. Messages cannot be
exchanged between the two organizations until this value is set to
True.
- EnabledSharedAddressSpace indicates whether the hosting
provider is being used in a shared SIP address space (split domain)
scenario.
- HostsOCSUsers indicates whether the hosting provider is
used to host Lync Server accounts. If False, the provider
hosts other account types, such as Microsoft Exchange accounts.
- ProxyFQDN specifies the fully qualified domain name
(FQDN) for the proxy server used by the hosting provider, in this
example, proxyserver.fabrikam.com. 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.
- Identity specifies a unique string value identifier for
the hosting provider you are creating, in this example,
Fabrikam.com. Note that the command will fail if an existing
provider has already been configured with that Identity.