Lync 2013 brings a clean fresh look to the non metro version of the client. The Metro verison is geared more towards tablets with touch interface. I was troubleshooting Lync autodiscovery issues for a client and went to verify the registry to see if Lync was able to get autodiscover information in the first place.
In Lync 2010, the registry URL was:
HKCUSoftwareMicrosoftCommunicator<SIP URI>Autodiscovery
That apparently has been changed in Lync 2015, as I was unable to find the registry for my client in there. The new path where Lync caches autodiscovery information is:
HKEY_CURRENT_USERSoftwareMicrosoftOffice15.0Lync<<SIP URI>Autodiscovery
Nice to know that they finally updated the name to Lync (and not communicator like Lync 2010), however the key is still called “Autodiscovery”. This is the information it retrieves from Exchange servers in the environment and the url it tries is(in that order):
• https://<smtpdomain>/autodiscover/autodiscover.xml
• https://autodiscover.<smtpdomain>/autodiscover/autodiscover.xml
• Autodiscover SRV record
As you can see the URL is “autodiscover” and not “autodiscovery” however since previous versions, Lync product team have named the key “autodiscovery” in registry.
Lync stores the below information in registry once it successfully retrieves autodiscover information from Exchange CAS servers:
One of the difference between Exchange 2007 & Exchange 2010 autodiscover method is the use of SOAP or XML in the request. Lync client first sends an unauthenticated GET to the above autodiscover URLs to retrieve the version of Exchange. Once it knows the version of exchange it will send the appropriate request SOAP for Exchange Server 2007 (X-SOAP-Enabled) or XML for Exchange Server 2010 (X-WSSecurity-Enabled). Exchange 2013 users SOAP as well. Versions before Exchange 2007 did not have the autodiscover feature.
-Shah
Has anyone nceiotd that after applying the latest lync updates to your edge servers you can now login with any user without a password? This started happening in our test environment after applying the update. I have checked with one of my peers who also runs a lync environment and he is having the same issue. He did not notice it until I pointed it out. You still have to type in a password for your director and front end pools. This is happening on our edge pool.