Failed to extend the Active Directory schema for SCCM

Introduction

Installation of configuration manager requires to extend Active Directory Schema with required schema objects to support SCCM implementation in your environment. Recently I have been working SCCM 2012 SP1 deployment in a lab for some testing and ran into a problem with AD schema extension.I have seen this error in the past and this error might have been documented on many other blog sites as well.

Note: You always need to run SCCM schema extension cmdlets on AD domain controller holding FSMO roles.

Failed to Extend AD Schema for SCCM Error

Below is the error message received during the AD schema extension for SCCM.

<11-10-2017 11:03:46> Modifying Active Directory Schema – with SMS extensions.
<11-10-2017 11:03:46> DS Root:CN=Schema,CN=Configuration,DC=MSExpertTalk,DC=COM,DC=PK
<11-10-2017 11:03:46> Failed to create attribute cn=MS-SMS-Site-Code.  Error code = 8224.
<11-10-2017 11:03:46> Failed to create attribute cn=mS-SMS-Assignment-Site-Code.  Error code = 8224.
<11-10-2017 11:03:46> Failed to create attribute cn=MS-SMS-Site-Boundaries.  Error code = 8224.
<11-10-2017 11:03:46> Failed to create attribute cn=MS-SMS-Roaming-Boundaries.  Error code = 8224.
<11-10-2017 11:03:46> Failed to create attribute cn=MS-SMS-Default-MP.  Error code = 8224.
<11-10-2017 11:03:46> Failed to create attribute cn=mS-SMS-Device-Management-Point.  Error code = 8224.
<11-10-2017 11:03:46> Failed to create attribute cn=MS-SMS-MP-Name.  Error code = 8224.
<11-10-2017 11:03:46> Failed to create attribute cn=MS-SMS-MP-Address.  Error code = 8224.
<11-10-2017 11:03:46> Failed to create attribute cn=mS-SMS-Health-State.  Error code = 8224.
<11-10-2017 11:03:46> Failed to create attribute cn=mS-SMS-Source-Forest.  Error code = 8224.
<11-10-2017 11:03:46> Failed to create attribute cn=MS-SMS-Ranged-IP-Low.  Error code = 8224.
<11-10-2017 11:03:46> Failed to create attribute cn=MS-SMS-Ranged-IP-High.  Error code = 8224.
<11-10-2017 11:03:46> Failed to create attribute cn=mS-SMS-Version.  Error code = 8224.
<11-10-2017 11:03:46> Failed to create attribute cn=mS-SMS-Capabilities.  Error code = 8224.
<11-10-2017 11:03:46> Failed to create class cn=MS-SMS-Management-Point.  Error code = 8202.
<11-10-2017 11:03:46> Failed to create class cn=MS-SMS-Server-Locator-Point.  Error code = 8202.
<11-10-2017 11:03:46> Failed to create class cn=MS-SMS-Site.  Error code = 8202.
<11-10-2017 11:03:46> Failed to create class cn=MS-SMS-Roaming-Boundary-Range.  Error code = 8202.
<11-10-2017 11:03:46> Failed to extend the Active Directory schema, please find details in “C:\ExtADSch.log”.

First step that i have always performed with my troubleshooting is to review the logs generated in C:\ExtADSch.Log file. Reviewing the logs, i found that the issue is being caused because the Schema Extension process was being initiated on the DC which does not hold the AD FMSO role.

How to Fix It?

To fix this issue, you always need to run SCCM schema extension cmdlets on a DC running AD FSMO role (Schema Master). To find out which server holds the FSMO role, you can run the following cmdlet.

C:\> netdom /query fsmo

Hope this helps you to mitigate some of your schema extension issues with SCCM implementation.


Also published on Medium.

Leave a Reply

Your email address will not be published. Required fields are marked *