Set up normalization rules on Microsoft Active Directory
A reverse look-up of a directory number to username does not work under these conditions:
the user is not provisioned for E.164 in Active Directory and
Active Directory phone number normalization rules are not set up
Under these conditions, the application identifies the call as coming from an extension number, and the username will not display in Microsoft Lync.
Therefore you must set up the correct normalization rules for the Active Directory address book on the Microsoft Lync server to enable the Microsoft Lync user to see the name of the calling party in the popup window that displays when the call is made.
You must provide a normalization rule file for extension dialing. See the sample normalization rules topic for an example.
Before You Begin
The CA-signed certificate for Microsoft Lync must be on the Microsoft Lync PC to achieve correct certificate distribution for address book synchronization. If a common CA is used to sign certificates, for example Verisign or RSA, the CA certificate may already come installed on the PC.
Ensure that normalization is enabled in Lync Server. To do this, open the Lync Server Management Shell and enter the following command:Get-CsAddressBookConfiguration
If the UseNormalizationRules value is set to True, normalization is enabled. If the UseNormalizationRules value is set to False, enter the following command to enable normalization:
Locate the ABFiles subdirectory in the Lync Server's shared directory that was configured during initial server deployment. Select Topology Builder > File Stores to identify the file server FQDN and share name. The path is as follows: \\<Server FQDN>\<Share Folder>\1-WebServices-1\ABFiles
Navigate to the following sample file: C:\Program Files\Microsoft Lync Server 2010\WebComponents\Address Book Files\Files\Sample_Company_Phone_Number_Normalization_Rules.txt
Make a copy of the Sample_Company_Phone_Number_Normalization_Rules.txt file and save it as Company_Phone_Number_Normalization_Rules.txt in the ABFiles directory.
You must save the Company_Phone_Number_Normalization_Rules.txt file in the ABFiles directory, and not where the actual address book files are saved.
Open the Company_Phone_Number_Normalization_Rules.txt file in Notepad and remove regex code like [\s()\-\./]* . Microsoft Lync Server ignores non-telephony related digits and only analyzes the continuous 0-9 numerical digit patterns. However it does recognize the + prefix.
In Lync Server Management Shell, enter the following command to import the new settings in the Company_Phone_Number_Normalization_Rules.txt file and apply them to numbers stored in the address book files: Update-CsAddressBook
With the default server/client settings, the Address Book is not immediately updated. To ensure that the Address Book is updated with the latest users added to the Active Directory, you must force the update on the server side and then force Microsoft Lync to pull down the latest files to update its local GalContacts.db file.
On Lync Server 2010, enter the following command in the Lync Server Management Shell:Update-CsAddressBook
This command triggers the Lync Server to synchronize current Active Directory information in the SQL database into the downloadable client and device address book files.
Wait five minutes for the synchronization process to complete.
With Administrator priveledges on Microsoft Lync, enter the following command in the Windows Command Prompt:reg add HKLM\Software\Policies\Microsoft\Communicator /v GalDownloadInitialDelay /t REG_DWORD /d 0 /f
This command forces Microsoft Lync to immediately download the address book.
Check whether the GalContacts.db and GalContacts.db.idx files exist on Microsoft Lync. If they do exist, delete them from the user's profile directory.
Exit Microsoft Lync. Do not just sign out.
Start the Microsoft Lync client and sign in again.
Verify that the updated GalContacts.db and GalContacts.db.idx files have been downloaded.
Perform a search for the new users and verify that their usernames display in Microsoft Lync.