Hi.

We are having an issue with some of our users overseas. They are using Lync 2013 on a computer that's essentially identical to the computers used across the organization. We are having trouble with EWS, so we are attempting to pre-populate the autodiscovery key under HKCU\Software\Microsoft\Office\15.0\lync\~SIP~\. The key is being populated successfully, but when Lync 2013 is launched, the key is automatically removed. Why is this happening, and more importantly, how can we force Lync to always use the autodiscovery key that we're creating so that EWS and other services function normally?

Thanks,

Have you tried removing write permissions to the key for all users and groups? If it's read only, Lync can't kill it. Not sure if it will help but worth a shot. What EWS issues do you have that you'

I wouldn't be too keen on editing the registry keys to remedy an EWS issue, feels too much like treating a symptom and not the root cause (of course I don't know the details of the issue).

Perhaps tell us about the EWS issue and we could assist in finding a suitable remedy.

ExternalTimeToLive & InternalTimeToLive are by default 24 Hours (18 in Hex format). When the cache expires the Autodiscovery key is deleted from the HKLM! By setting these values differently you extend the cache (43800 Hours = 5 Years = ab18 HEX)

"InternalTimeToLive"=dword:0000ab18

"ExternalTimeToLive"=dword:0000ab18

Accordingly your Autodiscovery key will not be deleted.

I did that and it is removed after like 5 minutes

Perhaps you have cmdlet set on the Lync server overriding the values? With a Set-ClientAccessServer for example?

http://blogs.technet.com/b/saleesh_nv/archive/2013/03/14/lync-2013-unified-contact-store-ucs-troubleshooting-tips.aspx

Perhaps you have cmdlet set on the Lync server overriding the values? With a Set-ClientAccessServer for example?

http://blogs.technet.com/b/saleesh_nv/archive/2013/03/14/lync-2013-unified-contact-store-ucs-troubleshooting-tips.aspx

• Proposed as answer by Hourlier Laurent 21 hours 33 minutes ago

Perhaps you have cmdlet set on the Lync server overriding the values? With a Set-ClientAccessServer for example?

http://blogs.technet.com/b/saleesh_nv/archive/2013/03/14/lync-2013-unified-contact-store-ucs-troubleshooting-tips.aspx

• Proposed as answer by Hourlier Laurent Thursday, April 23, 2015 9:53 AM