Before you begin, you can use a text editor, such as Windows Notepad, to review all of the Active Directory schema extensions that will be modified for Office Communications Server. The Schema.ldf file, which contains the Active Directory schema extensions, is located in the \Setup\amd64 folder on the Office Communications Server 2007 R2 Standard Edition CD or the Office Communications Server 2007 R2 Enterprise Edition CD.
The Office Communications Server schema extensions are replicated across all child domains, which impacts network traffic. Run schema preparation at a time when network usage is low.
|The Prep Schema wizard must access the Schema Master, which
requires that the remote registry service is running and that the
remote registry key is enabled. If the remote registry service
cannot be enabled on the Schema Master, you can run the wizard
locally on the Schema Master. For details about registry remote
access, see Microsoft Knowledge Base article 314837, "How to Manage
Remote Access to the Registry," at
ADSI Edit is an Active Directory Domain Services administration tool that you can use to verify that the Prep Schema wizard ran successfully. For Windows Server 2003, ADSI Edit is included with the Support Tools. For Windows Server 2008, this tool is included with the Remote Server Administration Tools (RSAT).
For Windows Server 2003, Support Tools are available from the
Windows Server 2003 CD in the \SUPPORT\TOOLS folder, or you
can download them from Windows Server 2003 Service Pack 2 32-bit
Support Tools at
For Windows Server 2008, the RSAT package is copied to the server by default when you install Windows, but it is not installed by default. You install individual tools by using Server Manager. ADSI Edit is included under Role Administration Tools, Active Directory Domain Services Tools, Active Directory Domain Controller Tools. For details about installing Remote Server Administration Tools, see Installing Remote Server Administration Tools for Windows Server 2008.
To prepare the schema of the current forest
Log on to a server in your forest as a member of the SchemaAdmins group and with Administrator rights on the Schema Master.
From the Office Communications Server installation folder or CD, run SetupEE.exe (for Enterprise Edition server consolidated configuration) or SetupSE.exe (for Standard Edition server) to start the deployment tool.
Click Prepare Environment.
Click Prepare Active Directory.
At Prep Schema, click Run.
On the Welcome to the Schema Preparation Wizardpage, click Next.
Do one of the following:
Default: Schema files are located in the same directory as
Browseand navigate to the directory where the schema files
- Click Default: Schema files are located in the same directory as Setup.
On the Ready to Prepare Schemapage, verify your current settings and then click Next.
On the Schema Preparation Wizard has completedpage, click View Log.
Under the Actioncolumn, expand Schema Prep, look for <Success>Execution Result at the end of each task to verify that schema preparation completed successfully, close the log, and then click Finish.
Wait for Active Directory replication to complete or force replication to all the domain controllers listed in the Active Directory Sites and Servicessnap-in for the forest root domain controller. Force replication between the domain controllers in all Active Directory sites to cause replication within the sites to occur within minutes.
Manually verify that schema preparation ran successfully and that the schema changes replicated to root domain and child domains, as described in the following procedure.
To manually verify schema preparation and replication
Log on to a member server as a member of the EnterpriseAdmins group.
Open ADSI Edit by clicking Start, clicking All Programs, clicking Administrative Tools, and then clicking ADSI Edit.
Tip: Alternatively, you can run adsiedit.mscfrom the command line.
In the MMC console tree, click ADSI Edit(that is, if it is not already selected).
On the Actionmenu, click Connect to.
In the Connection Settingsdialog box under Select a well known Naming Context, select Schema, and then click OK.
Under the schema container, search for CN=ms-RTC-SIP-SchemaVersion. If this object exists, and the value of the rangeUpperattribute is 1008, then the schema was successfully updated and replicated. If this object does not exist or the value of the rangeUpperattribute is not equal to 1008, then the schema was not modified or has not replicated.