<02-25-2012 14:03:45> Modifying Active Directory Schema - with SMS extensions. <02-25-2012 14:03:46> DS Root:CN=Schema,CN=Configuration,DC=BOA,DC=CO,DC=IN <02-25-2012 14:03:46> Failed to create attribute cn=MS-SMS-Site-Code. Error code = 8224. <02-25-2012 14:03:46> Failed to create attribute cn=mS-SMS-Assignment-Site-Code. Error code = 8224. <02-25-2012 14:03:46> Failed to create attribute cn=MS-SMS-Site-Boundaries. Error code = 8224. <02-25-2012 14:03:46> Failed to create attribute cn=MS-SMS-Roaming-Boundaries. Error code = 8224. <02-25-2012 14:03:46> Failed to create attribute cn=MS-SMS-Default-MP. Error code = 8224. <02-25-2012 14:03:46> Failed to create attribute cn=mS-SMS-Device-Management-Point. Error code = 8224. <02-25-2012 14:03:46> Failed to create attribute cn=MS-SMS-MP-Name. Error code = 8224. <02-25-2012 14:03:46> Failed to create attribute cn=MS-SMS-MP-Address. Error code = 8224. <02-25-2012 14:03:46> Failed to create attribute cn=mS-SMS-Health-State. Error code = 8224. <02-25-2012 14:03:46> Failed to create attribute cn=mS-SMS-Source-Forest. Error code = 8224. <02-25-2012 14:03:46> Failed to create attribute cn=MS-SMS-Ranged-IP-Low. Error code = 8224. <02-25-2012 14:03:46> Failed to create attribute cn=MS-SMS-Ranged-IP-High. Error code = 8224. <02-25-2012 14:03:46> Failed to create attribute cn=mS-SMS-Version. Error code = 8224. <02-25-2012 14:03:46> Failed to create attribute cn=mS-SMS-Capabilities. Error code = 8224. <02-25-2012 14:03:46> Failed to create class cn=MS-SMS-Management-Point. Error code = 8202. <02-25-2012 14:03:46> Failed to create class cn=MS-SMS-Server-Locator-Point. Error code = 8202. <02-25-2012 14:03:46> Failed to create class cn=MS-SMS-Site. Error code = 8202. <02-25-2012 14:03:46> Failed to create class cn=MS-SMS-Roaming-Boundary-Range. Error code = 8202. <02-25-2012 14:03:46> Failed to extend the Active Directory schema, please find details in "C:\ExtADSch.log".

one other issue i faced on one of the client they trying to run the schema update from child domain make sure it is run on forest root domain with schema admin rights.Syed Kasif

Did you check the ExtADSch.log which is mentioned above. Please check the account with which you were extending the schema and make sure that the account was not removed from the schema admins group and Domain Admin groups. Please check if the fsmo roles is assigned to the DC by running the command netdom /query fsmo.Sabrina TechNet Community Support

I have the exact same error described here, however I am a member of Schema Admins. I have also tried to log onto the DC as administrator with the same results. Any Ideas? DC Functional level is Windows Server 2008 R2

What does the log file say? Being on a DC makes no difference because the changes can only be made on the schema master so running the tool on the site server, a client, or a DC still initiates a connection to the schema master. The only time I've ever seen it fail is if you have replication issues in the forest or the schema master is unreachable.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

I found out my issue, I was setting this up in a test lab and only had one of the two domain controllers up, replicatoin wasnt working so I just ended up turing on the other DC and let them replicate, once they did this I was able to update the schema.

thanks very much i did the same as you suggested and brought the second DC online, then the extadsch.exe could successfully extend the schema now i've installed SCCM 2012 without issues. i appreciate your helpMGA2008