Lync mobility deployment – Quick reference guide

  • Article
  •        Login to frontend server and ensure that mobility services are successfully installed. You can see new virtual directory (McX) created under internal and external web sites . 
  •        Verify following DNS records are resolving properly. lyncdiscoverinternal.<sipdomain from internal network and lyncdiscover.<sipdomain from public DNS. Ensure that these IP addresses are pointed to reverse proxy external interface. 
  •         Ensure that port 5086 is allowed from internal network and port 5087 is allowed from internet for mobility service process. You should set the ports on external and internal web services using Set-CsWebServer commandlet. 
  •         Verify certificate subject alternative name on frontend , director and reverse proxy roles . Following SAN should be added on all boxes . lyncdiscoverinternal.<sipdomain , lyncdiscoverinternal.<sipdomain . Reverse proxy required only external auto discover SAN. 
  •        Verify web publishing rule on ISA box and ensure that external traffic is forwarding to frontend server as expected. Port 80-8080 forwarding doesn’t need a SAN entry on reverse proxy. However 443-4443 does required a SAN entry on reverse proxy server . 
  •          Have you tested peer to peer mobility instant messaging after deployment? It should be working as expected. 
  •        WI-FI internal mobility connectivity required cookie-based persistence set on hardware LB for internal web service URL. 
  •      For push notification for apple IOS and windows phones required port 5223 from enterprise WI-FI network . 
  •       For joining conference and work call feature required enterprise voice feature to be enabled for users .

Comments

  • Anonymous
    January 01, 2003
    @Jward - Please refer below link www.microsoft.com/.../details.aspx  and have a look at "update certificates with new subject alternative names" . You can use Set-CsWebServer cmdlet to set the ports .

  • Anonymous
    January 01, 2003
    @pyore - Yes , you are right , internal website should forward the connection to ISA external leg and get it connected.

  • Anonymous
    January 01, 2003
    @JBoyd – I am going to highlight few sentences mentioned in the mobility deployment guide  mobility , The Microsoft Lync Server 2010 Autodiscover Service returns all the Web Services URLs for the user's home pool, including the Mobility Service URLs. However, both the internal Mobility Service URL and the external Mobility Service URL are associated with the external Web Services FQDN. Therefore, regardless of whether a mobile device is internal or external to the network, the device always connects to the Microsoft Lync Server 2010 Mobility Service externally through the reverse proxy. So what I meant was internal mobility client will eventually forwarded to reverse proxy.

  • Anonymous
    December 22, 2011
    Good post, we're finding it very useful. A couple questions though: How do you add SANs to internally issued certificates? How do you set the ports for internal/external access and check that they're listening correctly? Thanks, J

  • Anonymous
    January 04, 2012
    The comment has been removed

  • Anonymous
    January 13, 2012
    Hi Saleesh, When I browse to lyncdiscover.external.x from the internet I get the external webservices url i.e. meetings.external.x However when I browse to lyncdiscoverinternal.internal.x I get passed our lync standard server fqdn lync.external.x... I would have expected to be passed the external webservices??