Chinaunix首页 | 论坛 | 博客
  • 博客访问: 1949365
  • 博文数量: 208
  • 博客积分: 7288
  • 博客等级: 少将
  • 技术积分: 45837
  • 用 户 组: 普通用户
  • 注册时间: 2006-09-19 14:58















分类: 虚拟化

2011-12-15 17:13:59

Enabling Lync 2010 for iPhone, iPad, Android and Other Mobile Devices


Microsoft recently announced their support to third party smartphones such as iPhone, iPad, Android, and Nokia devices. This support allows users to run IM clients on their third party mobile devices in addition to their desktop, OWA and Mac OS X clients. To allow support for devices mentioned above, you must make a few changes to your Lync 2010 environment. Microsoft introduced a new feature called Mobility Service. Extra components and configuring is required in your Lync environment to support this new service. Mobility Service is an MSI installer that needs to run on Lync 2010 FrontEnd servers and extra SAN certificate name is required. Below is a walkthrough of the installation of this new service.

Microsoft introduces two new services: Mobility Service and Autodiscover Service to support these additional third party devices. This new Autodiscover service is URL based  just like Exchange 2010 ) and it’s different from DNS auto discovery process in that it is introduced in RTM version of Lync 2010. Autodiscover service allows third party Lync mobile clients to autodiscover Lync servers. Autodiscover virtual directory is automatically created just like Exchange 2010. This virtual directory is created under both internal and external site but only external site should be used. Mobility service allows for push notification for iPhone and iPad clients, which do not support processes to run in the background. This is not a problem with Android devices. New virtual directory (Mcx) for Mobility service is automatically created within IIS sites (both sites, 443 and 4443).


Requirements to support iPhone, iPad, Android and other devices

  • New DNS name for autodiscover service (this need to be added to SAN Certificate also)
  • As mentioned above, you will need to reissue certificates for TMGs and Lync FrontEnd servers to include the new autodiscover DNS name
  • If you are using hardware loadbalncers such as F5, use cookie-based persistence.
  • New rule on TMG or ISA to allow autodiscover service.
  • Create internal and external autodiscover DNS records.
  • Add these autodiscover DNS records to SAN Certificate.




 High Level Overview of Lync 2010 Mobility Service Installation

  1. Create Internal and External DNS records for Autodiscover service.
  2. Install Lync 2010 Nov. cumulative update.
  3. Configure IIS Ports for Mobility Service.
  4. Add SAN names for newly created DNS records on certificates used on reverse proxy (TMG or ISA) and Lync FrontEnd servers.
  5. Run Lync 2010 Mobility Service Installer.
  6. Add listener on reverse proxy (TMG) for autodiscover service.
  7. Configure Edge Server for push notifications




Create Internal and External DNS records for Autodiscover service

  • Create a new internal DNS record ( ) that points to internal IP of FrontEnd Server pool.
  •  Create a new external DNS record ( ) that points to external IP of reverse proxy ( TMG or ISA).



Install Lync 2010 Nov cumulative update.

  1. Download update from
  2. Logon to Lync Server:
    run Stop-CSWindowsService (this will stop all the services)
    run “net stop w3svc”
  3. Install the update by running LyncServerUpdateInstaller.exe
  4. run “Stop-CSWindowsService” again
  5. Run “net start w3svc” after the install.
  6. Run “Install-CSDatabase –Update –ConfiguredDatabases –SqlServerFqdn” (This will apply changes to the lync database)
  7. Run “Start-CsWindowsService” ( to start Lync services)



Configure IIS Ports for Mobility Service

  1. Run “Set-CsWebServer –Identity –McxSipPrimaryListeningPort 5086”
  2. Run “Set-CsWebServer –Identity –McxSipExternalListeningPort 5087”
  3. Run “Enable-CsTopology”



Add SAN names for newly created DNS records on certificates used on reverse proxy (TMG or ISA) and Lync FrontEnd servers.

  1. Logon to Lync FrontEnd servers and run below commands.
  2. Use built-in Lync Wizard or Request-CsCertificate command to request the certificate.
  3. Use below commands to assign the certificate.
  4. Run “Get-CsCertificate” ( This will return the certificates that is assign to this server )
  5. Run “Set-CSCertificate –type default,webservicesinternal,webservice***ternal –Thumbprint C3RtThumbprint”



Run Lync 2010 Mobility Service Installer

  1. Download the McsStandalone.msi from Microsoft ( )
  2. Run the installer on all FrontEnd Servers. (note: if you running IIS 7.0 instead of 7.5, you must make additional config to applicationHost.config file)
  3. Copy above MSI installer to C:\ProgramData\Microsoft\Lync Server\Deployment\cache\4.0.7577.0\setup
  4. Open Lync Management Shell and run below command
    Run cd "C:\Program Files\Microsoft Lync Server 2010\Deployment\"





Run "Bootstrapper.exe"

  1. Add listener on reverse proxy (TMG) for autodiscover service.
  2. Open TMG Console, aka Forefront TMG Management
  3. Under ServerName > Firewall Policy > click NEW > Web Site Publishing Rule
  4. Select “Rule Action page” and select “Allow”
  5. Select “Publish a single Web site or load balance” from “Publishing Type” page.
  6. Select “Use SSL to connect to the published Web server or server farm” from Server Connection Security page.
  7. In “Internal Site name”, enter the full fqdn name of lyncfrontEnd server pool (example:
  8. Enter “/*” in the path field and select “Forward the original host header”
  9. In “Public Name Details” page, Under Accept Requests for, choose “This domain name”. In “Public Name”, enter, under “Path” enter “/*”
  10. In “Select Web Listener” page, under “Web Listener”, choose SSL Listener with newly created certificate.
  11. In “Authentication Delegation” page, choose “No delegation, but client may authenticate directly”.
  12. In “User set” page, select “All Users”.
  13. Finally, click Finish.
  14. Now, open the properties of newly created rule and configure below settings.
  15. check “forward the original host header instead of the actual one”.
  16. For frontend pool configurations, choose “requests appear to come from the original client”
  17. In “Bridging” page, choose “Web server”, choose “Redirect requests to HTTP port” and use “8080” as the port, choose “Redirect requests to SSL port” and use “4443” as the port.
  18. Click OK, Apply the configuration and test the rule.



Configure Edge Server for Push Notifications

  1. Log on to your Lync Edge server and open Lync Management Shell
  2. Run below command to add Lync Server hosting provider
    New-CsHostingProvider -Identity "MSLyncPush" -Enabled $True -ProxyFqdn "" -VerificationLevel UseSourceVerification
  3. Run below command to setup hosting provider federation to Lync Online Push notification service.
    New-CsAllowedDomain -Identity ""
  4. Run below commands to enable Push notifications:
    Set-CsPushNotificationConfiguration -EnableApplePushNotificationService $True -EnableMicrosoftPushNotificationService $True
    Set-AccessEdgeConfiguration -AllowFederatedUsers $True
  5. Use below command test the configuration (optional)
    Test-CsMcxPushNotification -AccessEdgeFqdn EdgeserviceFQDN



阅读(2351) | 评论(0) | 转发(0) |