A. I recently had this problem. I had a lab environment in which I repeatedly tried--and failed--to update the schema for SMS by running the command

extadsch.exe

After I ran the command, the log file contained the following information:

<07-12-2004 17:02:49> Modifying Active Directory Schema - with SMS
extensions.
<07-12-2004 17:02:52> DS
Root:CN=Schema,CN=Configuration,DC=savilltech,DC=com
<07-12-2004 17:03:24> Failed to create attribute cn=MS-SMS-Site-Code.
Error code = 8206.
<07-12-2004 17:03:56> Failed to create attribute cn=mS-SMS-Assignment
Site-Code. Error code = 8206.
<07-12-2004 17:04:28> Failed to create attribute cn=MS-SMS-Site-
Boundaries. Error code = 8206.
<07-12-2004 17:05:00> Failed to create attribute cn=MS-SMS-Roaming-
Boundaries. Error code = 8206.
<07-12-2004 17:05:32> Failed to create attribute cn=MS-SMS-Default-MP.
Error code = 8206.
<07-12-2004 17:06:04> Failed to create attribute cn=mS-SMS-Device-
Management-Point. Error code = 8206.
<07-12-2004 17:06:36> Failed to create attribute cn=MS-SMS-MP-Name.
Error code = 8206.
<07-12-2004 17:07:07> Failed to create attribute cn=MS-SMS-MP-Address.
Error code = 8206.
<07-12-2004 17:07:39> Failed to create attribute cn=MS-SMS-Ranged-IP-
Low. Error code = 8206.
<07-12-2004 17:08:11> Failed to create attribute cn=MS-SMS-Ranged-IP-
High. Error code = 8206.
<07-12-2004 17:08:11> Failed to create class cn=MS-SMS-Management-
Point. Error code = 8202.
<07-12-2004 17:08:11> Failed to create class cn=MS-SMS-Server-Locator-
Point. Error code = 8202.
<07-12-2004 17:08:11> Failed to create class cn=MS-SMS-Site. Error code
= 8202.
<07-12-2004 17:08:11> Failed to create class cn=MS-SMS-Roaming-
Boundary-Range. Error code = 8202.
<07-12-2004 17:08:11> Failed to extend the Active Directory schema.

After much investigation, I discovered the reason for the failed schema update: I had many domain controllers (DCs) that weren't running and consequently had replication errors. After I started the other DCs and resolved the replication errors by forcing a replication, the schema update worked perfectly, as you can see in the following log file output:

<07-12-2004 17:09:15> Modifying Active Directory Schema - with SMS
extensions.
<07-12-2004 17:09:15> DS
Root:CN=Schema,CN=Configuration,DC=savilltech,DC=com
<07-12-2004 17:09:18> Defined attribute cn=MS-SMS-Site-Code.
<07-12-2004 17:09:18> Defined attribute cn=mS-SMS-Assignment-Site-Code.
<07-12-2004 17:09:18> Defined attribute cn=MS-SMS-Site-Boundaries.
<07-12-2004 17:09:18> Defined attribute cn=MS-SMS-Roaming-Boundaries.
<07-12-2004 17:09:18> Defined attribute cn=MS-SMS-Default-MP.
<07-12-2004 17:09:18> Defined attribute cn=mS-SMS-Device-Management-
Point.
<07-12-2004 17:09:18> Defined attribute cn=MS-SMS-MP-Name.
<07-12-2004 17:09:18> Defined attribute cn=MS-SMS-MP-Address.
<07-12-2004 17:09:18> Defined attribute cn=MS-SMS-Ranged-IP-Low.
<07-12-2004 17:09:18> Defined attribute cn=MS-SMS-Ranged-IP-High.
<07-12-2004 17:09:18> Defined class cn=MS-SMS-Management-Point.
<07-12-2004 17:09:18> Defined class cn=MS-SMS-Server-Locator-Point.
<07-12-2004 17:09:18> Defined class cn=MS-SMS-Site.
<07-12-2004 17:09:18> Defined class cn=MS-SMS-Roaming-Boundary-Range.
<07-12-2004 17:09:18> Successfully extended the Active Directory
schema.

<07-12-2004 17:09:18> Please refer to the SMS documentation for
instructions on the manual
<07-12-2004 17:09:18> configuration of access rights in active
directory which may still
<07-12-2004 17:09:18> need to be performed. (Although the AD schema has
now been extended,
<07-12-2004 17:09:18> AD must be configured to allow each SMS Site
security rights to
<07-12-2004 17:09:18> publish in each of their domains.)