Lync Server 2010, just like previous versions of OCS, has new Active Directory schema that needs to be loaded before you can install any server roles. In Lync Server 2010 the new schema is split up into four different files:
These files can be found on the installation media in \Support\Schema. Running the SchemaPrep step as part of the install will automatically import the changes contained in these files into Active Directory. If you would like to manually import the schema into Active Directory, via ldifde, you need to make sure to apply the schema in a specific order:
Remember that no matter whether if you are migrating from a previous version of OCS or installing Lync Server 2010 in a greenfield environment, you need to apply all four schema files.
The following are the new attributes that are added to your Active Directory schema during SchemaPrep:
This attribute is used to store name value pairs.
Urn of the owner for the application contact.
This attribute is used to store name value pairs for target policies on OCS user.
This attribute used in split domain topology and contains an Fqdn.
This attribute contains Device ID of the Private Line Device.
The xml blob contains audio conferencing provider information for a user.
The ExternalSchema.ldf file contains two changes. It changes the thumbnailphoto attribute to replicate to the global catalog for the address book service. It also adds the ms-Exch-UC-Voice-Mail-Settings attribute to AD.
The ServerSchema.ldf file contains most of the attribute changes for Lync Server 2010.
This schema file contains all the previous attributes for OCS 2007 R2. This is mainly used in a greenfield deployment where the RTC attributes don't already exist.
The VersionSchema.ldf file is the last file to be run. All this schema file does is to set the ms-RTC-SIP-SchemaVersion attribute to the Lync Server 2010 version (1100).
Any issue with applying this do a environment running LCS currently?
A better questions to ask would be, "How are you going to migrate the users to Lync?". Since there is not direct migration path from LCS 2005 to Lync Server 2010, I would start there and decide upon the best option for migrating your users and updating clients.
Is there a 3rd party product that goes beyond what technet.microsoft.com/.../gg429725.aspx & msRTCSIP-GroupingID provides for Lync 2010 which would prevent them from using email contact information or manual entry of contact or phone number information. Please let me know at Lowell.Livingston@acgov.org or firstname.lastname@example.org - Thanks!