(DER X.509) and copy them to your local Mac. Microsoft Lync (2011) on Sierra: Nope 11902 Views 15 Replies.
Get lync for mac for mac#
You can use the Lync Connectivity Analyzer to learn more about the service URL’s returned during Lync Discovery. This enables the new Microsoft Skype for Business for Mac client to communicate together with Lync 2013.
is resolved to the external Autodiscover web service (via the reverse proxy) which returns a list of service URL’s. The client uses this information to connect to the Edge servers SIP access interface. The client uses this information to connect to the Front End server or pool.Įxternal – lyncdiscover. is resolved to the internal Autodiscover web service which returns a list of service URL’s. Lync Discover Process for Desktop Clients is resolved to the external Autodiscover web service (via the reverse proxy) which returns a list of service URL’s. The mobile client will use this information to connect to the external Web Services FQDN. Because both the internal and external Mobility Service URL’s for Lync 2010, and the UCWA URL for Lync 2013 are all associated to the external Web Services FQDN, mobile traffic is routed externally via the reverse proxy regardless of location.Įxternal – lyncdiscover.
Get lync for mac windows#
Lync Discover Process for Mobile Clients (including Windows Store App) record will effectively be querying external web services – you probably dont want this to happen right?įor more information on the DNS records required for mobility see this post. record, ALL Lync 2013 clients that find a lyncdiscover. is far more important as all clients now attempt to resolve a lyncdiscover record before moving on to older methods such as SRV. However with Lync 2013 the lyncdiscoverinternal. Many people do not see its worth due to the fact that all mobile client traffic is hair pinned via the external web services whether connected internally or externally. record to be intentionally and unintentionally omitted from internal DNS records. It is quite common for the lyncdiscoverinternal. This record should also only exist externally. should be an A record pointing to the IP address of the external web services which is normally an ISA reverse proxy. should be a CNAME or A record to the Lync Front End server and only exist on the internal network. NOTE: Some clients also continue on to query other records, however this article focuses only on lyncdiscover URL’s. There are 2 records which Lync will query in order: Please let me know if you think I have misunderstood anything 🙂 This is a summary of my understanding of the lyncdiscover records and the processes associated to them.
0 kommentar(er)
