address book ocs office communications server force updating communicator. Details how to force a Communicator client to download the address book immediately. Also includes info on the issue with some clients not. OCS R2 Server is generating address book perfectly. .net//01/20/ forcing-address-book-updates-in-communicatorr2/.
|Language:||English, Spanish, Dutch|
|Distribution:||Free* [*Register to download]|
Force the Communicator R2 Address Book to instantly update on both x86 and x64 machines. You can force a refresh by exiting Communicator, deleting that file, the address book is only generated on the OCS server every 24 hours so. Communicator cannot synchronize with the corporate address book of the address book file share and forcing a resync of the address book.
A number of people have been having problems with Communicator not downloading the address book properly or regularly since the July updates. From what I can the issue occurs because of problems merging in compressed address book files. To turn off the use of the compressed address book files you can use a registry entry on the client. The registry key is: The below may wrap in your browser.
Any value other than these results in it defaulting to 1. I wrote about it here: There was also the trick of deleting the GalContacts. The behaviour on this seems to have changed - I think. This seems to be related to the July update if I read this KB correctly: KB The scenario is that you delete the GalContacts files, re-start the Communicator client - and then wait.
It made no difference what the OS was, it was just frustratingly random and difficult to replicate consistently, some clients worked others just plainly refused to play ball.
The issue was caused by CRL certificate revocation list. This key just forces the client to ignore the CRL of the certificate, it will NOT force it to ignore expired certificates and I suggest once you have resolved the certificate issue on the server that this reg hack is removed or returned to its former state.
You are commenting using your WordPress.
You are commenting using your Google account. You are commenting using your Twitter account.
You are commenting using your Facebook account. Notify me of new comments via email.
Notify me of new posts via email. I hope this saves someone some time!
Share this: Twitter Facebook.