# Lync 2013 Client Autodiscover Cache Lync 2013 brings a clean fresh look to the non metro version of the client. The Metro version 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: HKCUSoftwareMicrosoftCommunicatorAutodiscovery 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<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:///autodiscover/autodiscover.xml - https://autodiscover./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 ### Author: Hemang Shah ### CEO, Logic V As the CEO of Logic V Inc., Hemang Shah is responsible for running all facets of the business. Hemang is an accomplished IT executive with over 10 years experience in the IT industry. Before founding Logic V Inc., Hemang has worked as Microsoft Practices Lead at Long View Systems, prior to that he was a Senior IT Infrastructure Consultant at Calgary based Compugen. Hemang also worked as Technical Accounts Manager at Microsoft. Hemang holds Microsoft Certified Solutions Expert (MCSE) certificate. Hemang has been helping small and medium business clients to attain their IT infrastructure goals for over a decade. Logic V Inc. was founded with the goal of bringing reliable technology management and advanced technologies to small and medium businesses.