Downloading the Address Book in Lync 2013

The location of the Address Books within Lync 2013 are different to that of previous iterations of the product. In this blog I look at where the files are now stored, and also how to affect the download delay for the Address Books. If you wish, you can set the address books to download immediately for example - very useful for testing.

====
Quite a while ago I wrote an article about how to force download the Address Book in Communicator 2007 R2. You can see the original article here.

Force Downloading the Address Book in OCS

If you were testing machines and new installations it could be a handy way to avoid the wait time to get your address books refreshed. The default behaviour induces a delay on the client to stop everybody hitting your address book location all at once.

Anyways, with Lync 2013 this registry location has changed from what it was for OCS 2007 R2. It still does the same thing, and it’s still a handy way of reducing your wait times for your address books - it’s just in a different place. It’s here:

HKCU\Software\Policies\Microsoft\Office\15.0\Lync

...and is still a 32 bit DWORD Value of:

GalDownloadInitialDelay

Setting it a zero will force a download of your address book as soon as you sign in.

Note that it is also possible to set this machine wide by referring to the HKLM subkey rather than HKCU which is specific to this user of course. So the full path would be:

HKLM\Software\Policies\Microsoft\Office\15.0\Lync

If you set both, the Local Machine setting appears to take precedence.

If you want a quick way to set these values, copy and paste these to an elevated DOS Prompt. Personally, I’d stay with using HKCU rather than setting on a whole machine:

Machine Wide Setting
reg add HKLM\Software\Policies\Microsoft\Office\15.0\Lync /v GalDownloadInitialDelay /t REG_DWORD /d 0 /f

User Specific Setting
reg add HKCU\Software\Policies\Microsoft\Office\15.0\Lync /v GalDownloadInitialDelay /t REG_DWORD /d 0 /f

NOTE: The above may appear wrapped for readability.





blog comments powered by Disqus