Deployment process for mobility in Lync Server 2013

 

Topic Last Modified: 2013-02-19

Some information in this topic pertains to Cumulative Updates for Lync Server 2013: February 2013. It is noted accordingly.

This section describes the sequence of steps required to deploy the Lync Server 2013 mobility feature.

Mobility Deployment Process

Phase	Steps	Permissions	Deployment documentation
Create Domain Name System (DNS) records	Create an internal DNS CNAME or A (host, if IPv6, AAAA) record to resolve the internal Autodiscover Service URL. Create an external DNS CNAME or A (host, if IPv6, AAAA) record to resolve the external Autodiscover Service URL.	Domain Admins DnsAdmins	Creating DNS records for the Autodiscover Service in Lync Server 2013
Modify certificates	Add subject alternative name entries to the following certificates to support secure connections for mobile users: Director certificate Front End pool certificate Reverse proxy certificate	Local administrator	Modifying certificates for mobility in Lync Server 2013
Configure the reverse proxy	Assign certificates updated with subject alternative names to the Secure Sockets Layer (SSL) Listener. Reconfigure the web publishing rule for the external Autodiscover Service URL. Be sure that a web publishing rule exists for the external Lync Server 2013 Web Services URL on your Front End pool. Or If you choose to use HTTP for the initial Autodiscover request and do not update subject alternative name lists on the certificates, configure a new web publishing rule or reconfigure an existing publishing rule for port 80 HTTP.	Local administrator	Configuring the reverse proxy for mobility in Lync Server 2013
Test your mobility deployment for Lync 2010 Mobile using the Mcx Mobility Service	Run Test-CsMcxP2PIM to test sending an instant message from one person to another. See the Lync Server Management Shell cmdlet documentation for Test-CsMcxP2PIM for a complete list of options.	CsAdministrator	Verifying your mobility deployment in Lync Server 2013
Test your mobility deployment for Lync 2013 Mobile clients using the UCWA Web components	Use the Test-CsUcwaConference cmdlet to test and verify that pre-defined test users or a pair of actual users can use UCWA to create and participate in a conference. See the Lync Server Management Shell cmdlet documentation for Test-CsUcwaConference for a complete list of options.	CsAdministrator	Verifying your mobility deployment in Lync Server 2013
Configure for push notifications	For Lync Server 2013 Edge Servers, add a Lync Server online hosting provider and configure hosting provider federation. For Lync Server 2010  Edge Servers, add a Lync Server online hosting provider and configure hosting provider federation. For Office Communications Server 2007 R2 Edge Servers, add a federated partner. If you want to support push notifications over a Wi-Fi network, configure a firewall rule outbound for TCP port 5223. Use the Set-CsPushNotificationConfiguration cmdlet to enable push notifications to the Apple Push Notification Service (APNS) and Microsoft Push Notification Service (MPNS). This feature is disabled by default. Use the Test-CsFederatedPartner cmdlet to test the federation configuration and the Test-CsMCXPushNotification cmdlet to test push notifications. Note Push notifications are used for Lync 2010 Mobile clients on Apple devices and Windows Phone Push notification is required for Lync 2013 Mobile clients on Windows Phone only	RtcUniversalServerAdmins	Configuring for push notifications in Lync Server 2013
Configure mobility policy	Use the Set-CsMobilityPolicy cmdlet to allow or disallow: Call via Work Enable IP Audio and IP Video Require WiFi for IP Audio and/or IP Video	CsAdministrator	Configuring mobility policy in Lync Server 2013