I just love some of these off the wall oddities when it comes to OCS and Lync. The user was promoted, but his new job title was not showing up properly on his contact card in Communicator. It was just irritating me to no end that I wasn’t seeing the right title. When the user came back and downloaded the new address book, everything started to work perfectly.
FYI, I have run into the same issue in Lync as well. Yes, somehow the user’s data from their Communicator client stopped everyone else in the company from seeing the correct title.
If you are an administrator ready to deploy Office 2013, you can make the above change also via Group Policies.
In this case, you’ll need to load the Lync Policy Template which is included in the Office 2013 Administrative Templates.
In the option of Communicator, the option “Update my presence based on my Calendar information” is checked but that doesn’t seem to work either. The bad new is; Communicator 2007 R2 isn’t compatible with Office 2013.
The good news is; You can still make Lync 2013 work with Communications Server 2007 R2. To make Lync 2013 connect to Communications Server, add the following Registry key: Key: Officially, this isn’t a supported configuration for Lync (connecting to Communications Server 2007 R2) but it works nonetheless.
Because Step #1 in the process happens by default every minute then any recent changes in AD should already be imported into the SQL database.
The Contact Card is another way to access some of your important business tasks.
The card displays basic data for the contact, including job title and department, phone numbers, and the person's scheduled events on the calendar.
Research showed the following: I still saw the old title.
It appears that Communicator uses the information that is stored in SQL over the information in the Address Book data files.