) or Front End pool/server FQDN if no Director is deployed.īefore installation of the Mobility service each Lync Server must first be upgraded to Cumulative Update 4. Create a new internal DNS Alias (CNAME) record with an Alias Name of lyncdiscoverinternal for the new internal autodiscover FQDN and set the target host as the Director FQDN (e.g.By using an alias record then the single pool FQDN will always be used as the resolution target. As the example environment has a single primary SIP domain defined as then the internal and external Autodiscover records are created in this same namespace.īoth Alias (CNAME) or Host (A) records are supported, but the simpler approach of using CNAME records will be used for the internal record as this approach works better with a pool since additional server nodes would require additional autodiscover A records. The first step is to define a new DNS record in the same internal forward lookup zone for each defined SIP domain in the Lync topology. Steps which are different when a Director role is or is not deployed are specifically identified and explained in detail. All servers are running Windows Server 2008 R2 and Lync 2010 Server CU3 version software. The example environment used in this article include a single Enterprise Edition Front End Server, Director Server, Edge Server, and Forefront TMG server for a reverse proxy. A traditional single-homed collocated Front End server is supported and works fine, it is only the multiple NIC scenario that is not. Microsoft Lync Server 2010 Mobility Service and Microsoft Lync Server 2010 Autodiscover ServiceĪn important requirement is that the Mobility service is not supported on a Front End server with a collocated Mediation Server role that has two separate network interfaces which are configured separately as a primary interface for Lync server/client communications and a PSTN interface.Lync Server 2010 Hotfix KB 2493736 (Cumulative Update 4).Microsoft Lync Server 2010 Mobility Guide.(A special thanks goes out to Dave Howe at Microsoft for yet again fielding numerous questions related to how the new Mobility service operates in the undocumented areas.) Prerequisitesīefore beginning the configuration and deployment steps in this article first make sure that each of the following packages has been downloaded it is also recommended to review the official deployment guide. Understanding these concepts can greatly increase the odds of a successful deployment, and this article addresses some of the more complicated or potentially confusing aspects of the overall solution. Now that the Lync 2010 Mobility Service has been out for a week there has been ample time, relatively speaking, to dissect the documentation, run through multiple installation attempts, and perform some initial discovery work on exactly what this new service is and how it appears to function.
0 Comments
Leave a Reply. |