Topic Last Modified: 2011-04-05
In general, Address Book is migrated along with the rest of your topology. However, you might need to perform some post-migration steps if you customized the following in your Microsoft Office Communications Server 2007 R2 environment:
- Set the PartitionbyOU WMI property to group Address Book
entries by organizational unit (OU).
- Customized the Address Book normalization rules.
Grouped Address Book Entries
If you set the PartitionbyOU WMI property to True to create address books for each OU, you need to set the msRTCSIP-GroupingId Active Directory attribute on users and contacts if you want to continue grouping address book entries. You might want to group address book entries to limit the scope of Address Book searches. To use the msRTCSIP-GroupingId attribute, write a script to populate the attribute, assigning the same value for all of the users that you want to group together. For example, assign a single value for all the users in an OU.
Address Book Normalization Rules
If you customized Address Book normalization rules in your Office Communications Server 2007 R2 environment, you must migrate the customized rules to your pilot pool. If you did not customize Address Book normalization rules, you have nothing to migrate for Address Book service. The default normalization rules for Lync Server 2010 are the same as the default rules for Office Communications Server 2007 R2.
|If your organization uses remote call control and you customized Address Book normalization rules, you must perform the procedure in this topic before you can use remote call control. The procedure requires membership in the RTCUniversalServerAdmins group or equivalent rights.|
To migrate Address Book customized normalization rules
Find the Company_Phone_Number_Normalization_Rules.txt file in the root of the Address Book shared folder, and copy it to the root of the Address Book shared folder in your Lync Server 2010 pilot pool.
Use a text editor, such as Notepad, to open the Company_Phone_Number_Normalization_Rules.txt file.
Certain types of entries will not work correctly in Lync Server 2010. Look through the file for the types of entries described in this step, edit them as necessary, and save the changes to the Address Book shared folder in your pilot pool.
Strings that include required whitespace or punctuation cause normalization rules to fail because these characters are stripped out of the string that is input to the normalization rules. If you have strings that include required whitespace or punctuation, you need to modify the strings. For example, the following string would cause the normalization rule to fail:
The following string would not cause the normalization rule to fail: