Setup the internal and external URL, including HTTPSand Basic Authentication If you define them, you have a reminder what is configured, more like a comment Identity 'autodiscover (default Web site)' It would be enough is you configure simply: What is IMPORTANT, is the Authentication, you must set it the Basic Authentication, so the SSL configuration will take part. Meaning, if they are defined or not, it will not change the Autodiscover behavior, since they are NOT USED within Exchange. If you set the URL's, it will NOT HAVE AN IMPACT. Therefore it is not necessary and not Best-Practise defining them! The AutodiscoverVirtualDirectoy URL are supposed for Microsoft's optional use only. Set-AutodiscoverVirtualDirectory -Identity 'autodiscover (default Web site)' -ExternalURL '' -InternalURL '' -BasicAuthentication $true
Setup the internal and external URL, including HTTPS and Basic Authentication external, Autodiscover is identified by DNS entry.internal, Autodiscover is identified by DNS entry.The correct discovery process is like ( LYNC): cached URL in the Outlook profile (new for Outlook 2013).SCP lookup (only if client is domain joined).The correct discovery process is like ( OUTLOOK): You'll receive an error if you specify the URLs. in Exchange 2007/2010 you are able defining those parameters, in Exchange 2013 they are even documented in TechNet, but they simply don't exist anymore. So split DNS is recommended (at least for Autodiscover)Īutodiscover will never use the internalURL and externalURL. your Active Directory domain, sure you can have internally another EWS published, but Autodiscover use by Lync identifies still the xml file via the users SIPDOMAIN. If you use internally another domain, e.g. domain.name SRV 0 0 443 exchangeserver(CAS)Į A exchangeserver (CAS) You need PER SMTP Domain 3 DNS Record, internally (Split DNS) and on the external DNS Server, 2x for Autodiscover and 1x for EWSĪutodiscover. Presence Information based on your Outlook Calendar. Therefor Exchange Web Service are not connected deployed and several Lync Integration Features are not working, e.g. Very often you find in Lync/ Exchange deployments an issue, where the Lync configuration show up with empty: Just remember, identify if you have DNS Split configuration, different internal and external DNS names and what are your SMTP and SIP Domains. Generally it is necessary to understand how DNS must be implemented: There is always confusion in how Lync is crawling Exchange Web Services (EWS). Generally, I'll write a new blog article, since the conversion history over multiple device and other service have change with Skype for Business 2015 Server. This blog entry is valid for Lync 2010, Lync 2013 and Skype for Business Server.
0 kommentar(er)
