skip to content »

Ocs contact card not updating

ocs contact card not updating-83

Yes, this is old news and there’s about 462 blog entries (ok, that’s a made up number, but there are a lot) about how to force Communicator 2007 R2 to do an Address Book (Galcontacts.db) update.These blog entries will talk about the July 2009 update for Communicator 2007 R2 and how it introduced a random delay of 0-60 minutes for Communicator 2007 R2 to download an updated Gal to prevent the network from getting hammered by so many clients downloading an updated Gal all at the same time.

ocs contact card not updating-63ocs contact card not updating-83ocs contact card not updating-53

Well that is mostly correct, as it required 3 of the above resolutions in the correct order to resolve the issue. To create the issue this seems to be the process of events.The objective of this blog article is to explain how this process works now in Lync Server 2010.Overall the process is generally the same, but with a few minor changes that impact both how it is configured and how normalization functions.In Lync 2013, support for high-resolution photos for users.This topic describes how Lync client gets and displays user photos, where the images are stored, the limitations for each image source, and how user photos are used by different Lync services.Refer to the documentation for a description of the built-in generic normalization rules.

Use the ABServer -dump Rules command to see all the rules that Address Book Server is currently configured with.” It looks like this: If you press the path in the event propertis or browse to the file location in your server (always in the same place, in the same name), you will see the following: What you get here is a list of the users and they’re phone numbers you thought were ok. Well, Lync expects all the phone numbers in your AD to be in the E.164 format, meaning they should be 1-111-11111111 etc. If you continue reading in event 21034, you’ll see the following: “Either create a Company_Phone_Number_Normalization_file in the output location and make sure it covers all cases found in your Active Directory deployment or fix the invalid phone number(s) in the Active Directory record(s).” You get a free advice – you don’t throw it away, do you?

None of these were the fix for my issue and I’ll explain my resolution in detail later in this article.

There is a similar fix included in the 2013 February CU, KB2798145, however this was applied and did not resolve the issue.

If they’re not like this (as the example above shows us), you will have to normalize them if you want Lync to publish them. What Lync actually tells you, is to create a file called “Company_Phone_Number_Normalization_Rules.txt” in the root of the AB folder of your Lync shared folder (Not in a sub folder, not by a different name, EXACTLY this one) – like it shows you here: In this file, you must enter normalization rules according to your country code and other variables.

I used to freak out when I heard normalization rules, but fortunately the guys at Lync made it quite simple for us: I use the Lync Server Control Panel to generate and test my normalization rules.

The local Lync Address Book will override information kept in the Lync Address Book Services Web Query (ABS-WQ).