Lync and OCS - Address Book and User Replicator. Lync and If you were forcing ABS updates it could be related to this issue. 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.
|Language:||English, Spanish, Portuguese|
|Genre:||Health & Fitness|
|Distribution:||Free* [*Registration needed]|
One of it's test is checking the OCS Address book server. Close and reopen Communicator; this should force a hit against the ABS to pull. A very common scenario in OCS and R2 is that client computers do not get updates to the Address Book right away. We generally use abserver. exe –syncnow to force the changes (and only the changes) in AD to. Force Downloading the Address Book in OCS. UPDATE I've made an adm file that you can use with Group Policy to configure the.
These blog entries will talk about the July update for Communicator R2 and how it introduced a random delay of minutes for Communicator R2 to download an updated GalContacts. And yes, these blog entries also talk about a registry entry you can create called GalDownloadInitialDelay and creating a Dword set to 0 in order to force Communicator to do an instant update.
Of course not!
So, Communicator R2 is a bit x86 application. That registry entry works perfectly fine on x86 systems. Well, because when you run x86 applications on a x64 based system, it utilizes a system in Windows called Windows on Windows WOW WOW64 has its own section within the registry called WowNode.
The following registry key works fine:. The above registry key will not work.
We need to utilize the WOWNode part of the registry. The following registry key works for x64 systems:. Please make sure you back up your registry before making changes as making changes to the registry can be harmful to your system if not done properly.
Elan Shudnow:: Great info Elan. Ya, it was driving me mad why it wouldn't work. Thanks, and its really great to point everytime on the differences of x86 and x64 regarding communicator.
Most of these registry hacks were introduced far after RTM, and it seems the official GIGA-CHM will never include or its just in a huge delay a comprehensive list of all these finetunes. I just forgot to say: Hi Mr. Elan, this is Jayden from Temasek Polytechnic, Singapore.
Busbar Solutions Architect Commented: Last modified: Read Article. Some people have phone numbers listed in AD mostly new users , but not everyone.
This particular user test. Once I add them to my contacts in OC, everything seems to work like a champ.
As for sync errors, it is not reporting any issues. Tried it, doesn't seem to make a difference. Cliff Galiher Commented: Execute an abserver. Server will throw them in the application event log, server and R2 break them out into their own event log, so make sure you are looking in the right place. This sounds like the server not updating the OAB on the server.
Experts Exchange Solution brought to you by Your issues matter to us.
Nothing changed, but I ran abserver. Thanks for the help.
It's more than this solution. Get answers and train to solve all your tech problems - anytime, anywhere. Try it for free Edge Out The Competition for your dream job with proven skills and certifications. Get started today Stand Out as the employee with proven skills.
Start learning today for free Move Your Career Forward with certification training in the latest technologies. 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.
Build Your Business on a Solid Infrastructure. Skip to content. Home About. Posted on September 15, by Russ Kaufmann.
Share this: Twitter Facebook. Like this: Like Loading This entry was posted in Office Communications Server.