Deployment Process for Mobility

 

Topic Last Modified: 2012-10-09

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

Mobility Deployment Process

Phase	Steps	Permissions	Deployment documentation
Create Domain Name System (DNS) records	Create an internal DNS CNAME or A (host) record to resolve the internal Autodiscover Service URL. Create an external DNS CNAME or A (host) record to resolve the external Autodiscover Service URL.	Domain Admins DnsAdmins	Creating DNS Records for the Autodiscover Service
Install cumulative update for Lync Server 2010: November 2011	Install updates on all server roles in your deployment.	CsAdministrator	Installing Cumulative Update for Lync Server 2010: November 2011
Set ports for the Front End Server	Set internal listening port for the Mobility Service. Set external listening port for the Mobility Service.	RTCUniversalServerAdmins	Setting Internal Server Ports for Mobility
Install Microsoft Lync Server 2010 Mobility Service and Microsoft Lync Server 2010 Autodiscover Service	Run McsStandalone.msi on each Front End Server to install the Mobility Service and the Autodiscover Service. Run McsStandalone.msi on each Director to install the Autodiscover Service.	CsAdministrator	Installing the Mobility and Autodiscover Services
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
Configure the reverse proxy	Assign certificates updated with subject alternative names to the Secure Sockets Layer (SSL) Listener. Configure a new web publishing rule for the external Autodiscover Service URL. Ensure that a web publishing rule exists for the external Lync Server Web Services URL on your Front End pool. Or If you choose to use HTTP for the initial Autodiscover request and not update subject alternative name lists on the certificates, configure a new web publishing rule for port 80 HTTP.	Local administrator	Configuring the Reverse Proxy for Mobility
Test your mobility deployment	Run Test-CsMcxP2PIM to test sending an instant message from one person to another.	CsAdministrator	Verifying Your Mobility Deployment
Configure for push notifications	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.	RtcUniversalServerAdmins	Configuring for Push Notifications
Configure mobility policy	Use the Set-CsMobilityPolicy cmdlet to allow or disallow user access to mobility features and to enable or disable Call via Work. These features are enabled by default.	CsAdministrator	Configuring Mobility Policy