Schema
Microsoft Office Communications Server 2007 and Microsoft Office Communications Server 2007 R2 will reach end of support on January 9, 2018. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.
Before beginning this procedure, review all Active Directory extensions that will be modified for Office Communications Server using a text editor such as Notepad. (This step is optional, but it can be useful in an Enterprise environment.) The Schema.ldf file is located in the root folder of the installation CD. Office Communications Server schema extensions are replicated across all child domains, which impacts network bandwidth.
Note
For details about preparing schemas, see Office Communications Server 2007 R2 Active Directory Guide in the Deployment documentation.
Preparing the Schema
Run SchemaPrep at a time when network utilization is low. SchemaPrep must access the Schema Master. To access the Schema Master, the remote registry service must be running with the remote registry key enabled. To prepare the schema of the current forest, you should log on to a computer in the Active Directory domain with Schema Admins credentials and administrator credentials on the Schema Master as follows.
LCSCmd.exe /Forest /Action:SchemaPrep [/ldf:<folder where the .ldf file is located>]
Such as:
LCSCmd.exe /Forest /Action:SchemaPrep
Use the CheckSchemaPrepState action to verify that Schema Prep completed successfully.
Check Schema State
Use the CheckSchemaPrepState action to check Active Directory schema state. The syntax for the CheckSchemaPrepState action follows.
LCSCmd.exe /Forest[:<forest FQDN>] /Action:CheckSchemaPrepState
Such as:
LCSCmd.exe /Forest /Action:CheckSchemaPrepState
Before the schema has been prepared, the log file generated by CheckSchemaPrepState will show a Schema Prep State of None. After the schema has been successfully prepared, the Schema Prep State will be Office Communications Server 2007 R2.