Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED SCCM Extending schema

Status
Not open for further replies.

Kirankr31

Active Member
Messages
32
Reaction score
1
Points
6
Hello All,

I have uninstalled SCCM 2012 , Now I am planning to install it again with the same Hostname. Do I need to re-create the System Management container and assign the rights. But before that I have started the setup to Install SCCM 2016 with the same Hostname and extended schema. Please find the below logs and suggest me about it. Most of the entries it says already exits. Please help.

<09-05-2017 18:48:22> Modifying Active Directory Schema - with SMS extensions.
<09-05-2017 18:48:22> DS Root:CN=Schema,CN=Configuration,DC=xxxxxxx,DC=local
<09-05-2017 18:48:22> Attribute cn=MS-SMS-Site-Code already exists.
<09-05-2017 18:48:22> Attribute cn=mS-SMS-Assignment-Site-Code already exists.
<09-05-2017 18:48:22> Attribute cn=MS-SMS-Site-Boundaries already exists.
<09-05-2017 18:48:22> Attribute cn=MS-SMS-Roaming-Boundaries already exists.
<09-05-2017 18:48:22> Attribute cn=MS-SMS-Default-MP already exists.
<09-05-2017 18:48:22> Attribute cn=mS-SMS-Device-Management-Point already exists.
<09-05-2017 18:48:22> Attribute cn=MS-SMS-MP-Name already exists.
<09-05-2017 18:48:22> Attribute cn=MS-SMS-MP-Address already exists.
<09-05-2017 18:48:22> Attribute cn=mS-SMS-Health-State already exists.
<09-05-2017 18:48:22> Attribute cn=mS-SMS-Source-Forest already exists.
<09-05-2017 18:48:22> Attribute cn=MS-SMS-Ranged-IP-Low already exists.
<09-05-2017 18:48:22> Attribute cn=MS-SMS-Ranged-IP-High already exists.
<09-05-2017 18:48:22> Attribute cn=mS-SMS-Version already exists.
<09-05-2017 18:48:22> Attribute cn=mS-SMS-Capabilities already exists.
<09-05-2017 18:48:23> Class cn=MS-SMS-Management-Point already exists.
<09-05-2017 18:48:23> Located LDAP://cn=MS-SMS-Management-Point,CN=Schema,CN=Configuration,DC=xxxxxxx,DC=local
<09-05-2017 18:48:24> Successfully updated class LDAP://cn=MS-SMS-Management-Point,CN=Schema,CN=Configuration,DC=xxxxx,DC=local.
<09-05-2017 18:48:24> Class cn=MS-SMS-Server-Locator-Point already exists.
<09-05-2017 18:48:24> Located LDAP://cn=MS-SMS-Server-Locator-Point,CN=Schema,CN=Configuration,DC=xxxxx,DC=local
<09-05-2017 18:48:25> Successfully updated class CN=Schema,CN=Configuration,DC=xxxxx,DC=local.
<09-05-2017 18:48:25> Class cn=MS-SMS-Site already exists.
<09-05-2017 18:48:25> Located LDAP://cn=MS-SMS-Site,CN=Schema,CN=Configuration,DC=xxxxx,DC=local
<09-05-2017 18:48:26> Successfully updated class LDAP://cn=MS-SMS-Site,CN=Schema,CN=Configuration,DC=xxxxxxx,DC=local.
<09-05-2017 18:48:26> Class cn=MS-SMS-Roaming-Boundary-Range already exists.
<09-05-2017 18:48:26> Located LDAP://cn=MS-SMS-Roaming-Boundary-Range,CN=Schema,CN=Configuration,DC=xxxxxxx,DC=local
<09-05-2017 18:48:26> Successfully updated class LDAP://cn=MS-SMS-Roaming-Boundary-Range,CN=Schema,CN=Configuration,DC=xxxxxx,DC=local.
<09-05-2017 18:48:26> Successfully extended the Active Directory schema.

<09-05-2017 18:48:26> Please refer to the ConfigMgr documentation for instructions on the manual
<09-05-2017 18:48:26> configuration of access rights in active directory which may still
<09-05-2017 18:48:26> need to be performed. (Although the AD schema has now be extended,
<09-05-2017 18:48:26> AD must be configured to allow each ConfigMgr Site security rights to
<09-05-2017 18:48:26> publish in each of their domains.)
 
Now I am planning to install it again with the same Hostname - Use a different host name and site code.

Do I need to re-create the System Management container and assign the rights - You need not create system management container again. Just delegate the new site server full control on system management container.
 
The extension schema is already done, you don't need extended it again unless you want using a new version for SCCM.

You can already view the log recording during the uninstall operation: C:\.... (System partition) to verify if the uninstall was successful or not.
If you want use the same machine and reinstall SCCM, you need to verify the prerequisites for SCCM (ADK, System Management container with permissions...).
 
Status
Not open for further replies.
Back
Top