3.In the MMC console tree, click ADSI Edit (that is, if it is not already selected).
4.On the Action menu, click Connect to.
5.In the Connection Settings dialog box under Select a well known Naming Context, select Schema, and then click OK.
6.Under the schema container, search for CN=ms-RTC-SIP-SchemaVersion. If this object exists, and the value of the rangeUpper attribute is 1008, then the schema was successfully updated and replicated. If this object does not exist or the value of the rangeUpper attribute is not equal to 1008, then the schema was not modified or has not replicated.
Using Setup to Run Forest Preparation
If Active Directory replication of the schema preparation changes has not completed, an error occurs. Wait for replication to complete or force replication before running the Prep Forest wizard.
You might want to decide where to store global settings before starting this procedure. If connectivity to the root domain is unreliable, select the Configuration partition. For details about selecting the location, see .
The Prep Forest wizard requires that you specify the Session Initiation Protocol (SIP) domain to be used for default routing. The default SIP domain is used to construct the server SIP Uniform Resource Identifier (URI), which in the simplest form is <ServerFQDN>@<DefaultSIPDomainFQDN>. The wizard identifies a default SIP domain as follows:
In new deployments, the root domain is always proposed as the default SIP domain.
For existing deployments, if no default SIP domain exists, all existing SIP domains appear as possible options, and the wizard selects one domain randomly as the default routing domain.
If a default SIP domain already exists, the wizard populates the list with all existing SIP domains and selects the default SIP domain.
You must be a member of the EnterpriseAdmins group for the forest root domain to perform this procedure.
For a description of the universal groups and the global settings and objects created by forest preparation, see .
If you are currently using Office Communications Server 2007 and the forest preparation for Office Communications Server 2007 R2 fails, the rollback might remove access control lists (ACLs) that are required for Office Communications Server 2007 to