Create a backup of the schema master domain controller’s system state using the NTBACKUP utility.

Disconnect the schema master domain controller from the network.

Open the ConfigMgr_ad_schema.ldf file, located in the \SMSSETUP\BIN\I386 directory of the Configuration Manager 2007 installation files, and edit the file to define the Active Directory root domain to extend. All instances of the text DC=x in the file must be replaced with the full name of the domain to extend.

For example, if the full name of the domain to extend is named widgets.microsoft.com, all instances of DC=x in the file should be changed to DC=widgets, DC=microsoft, DC=com.

Use the LDIFDE command-line utility to import the contents of the ConfigMgr_ad_schema.ldf file into Active Directory Domain Services.

For example, this command line will import the schema extensions into Active Directory Domain Services, turn on verbose logging, and create a log file during the import process:
ldifde –i –f ConfigMgr_ad_schema.ldf –v –j <location to store log file>.

To verify that the schema extension was successful, you can review the log file created by the command line used in step 3.

If the extension procedure was successful, reconnect the schema master domain controller to the network and allow it to replicate the schema extensions to the global catalog servers throughout the Active Directory forest.

If the schema extension procedure was not successful, restore the previous system state using the NTBACKUP utility to reverse the schema extension actions before reconnecting the schema master domain controller to the network.

Note
To restore the system state on a Microsoft Windows domain controller, the system must be restarted in Directory Services Restore Mode. For more information about Directory Services Restore Mode, see "Restart the domain controller in Directory Services Restore Mode locally" at http://go.microsoft.com/fwlink/?LinkId=75622.

In the ConfigMgr_ad_schema.ldf file supplied in the Configuration Manager installation source files, locate the section in the file beginning with the following text:

# ---------------------------------------------------------------------
# This section updates an existing MS-SMS-Management-Point class
# by adding four new attributes to the class.  This section
# should always succeed whether the Schema is already extended for SMS 
# 2003 or if it is updated using this file.
# ---------------------------------------------------------------------

Replace the following text from that section with the text provided in step 3 of this procedure.

dn: CN=MS-SMS-Management-Point,CN=Schema,CN=Configuration,DC=x
changetype: modify
add: mayContain
mayContain: mSSMSCapabilities
mayContain: mSSMSVersion
mayContain: mSSMSSourceForest
mayContain: dNSHostName
-

dn:
changetype: modify
replace: schemaupdatenow
schemaupdatenow: 1
-

To allow the existing management point object information stored in the Active Directory schema to be extended for Configuration Manager, the following text should be used to overwrite the existing text in the ConfigMgr_ad_schema.ldf file that was shipped with the Configuration Manager installation source files and displayed in step 2 of this procedure:

dn: CN=MS-SMS-Management-Point,CN=Schema,CN=Configuration,DC=x
changetype: modify
add: mayContain
mayContain: dNSHostName
-

dn:
changetype: modify
replace: schemaupdatenow
schemaupdatenow: 1
-

dn: CN=MS-SMS-Management-Point,CN=Schema,CN=Configuration,DC=x
changetype: modify
add: mayContain
mayContain: mSSMSCapabilities
mayContain: mSSMSVersion
mayContain: mSSMSSourceForest
-

dn:
changetype: modify
replace: schemaupdatenow
schemaupdatenow: 1
-

Save the modified LDIF file and use it to update the existing SMS 2003 schema extensions using the LDIFDE utility.

When you are using the modified LDIF file to extend the Active Directory schema, the –k command-line switch can be used to suppress Display Constraint Violation and Object Already Exists errors.