Prepping Prod AD for SCCM 201211 May 2012 6 min read.
As already presented, I am going to be implementing a Central Administration Site, along with a single primary site in my production environment. This initial build will use two instances from the pre-existing SQL Cluster, and 3 machines, one dedicated to the Central Site and the others for the Primary site. As this is production, the Active Directory and Certificate Services are already in place, however we will need to extend the Schema for Configuration Manager, and create its Container in the System OU. All my servers are created with Windows 2008 R2 Server with SP1 and current Hot Fixes installed, and functioning members of the production domain.
As the primary site will be leveraging my Domain controllers which are located in each of the branch offices as the local Distribution Point, all of which will be part of the Primary Site, I need to provide the Primary Site access to these systems.
The best way I could find for doing this was to add the Computer Account of the Primary Site Server, to the Domain Administrators group in my Active Directory. This permission then enables site roles to be deployed as required using the Primary Servers account, secure in the knowledge that this account has the necessary permissions to configure the roles required on the domain controllers automatically, with out any additional manual intervention.
SCCM has the ability to use AD as a database for locating other servers which are part of the SCCM environment, however to enable this functionality, a container needs to be created in the _System _OU_ _called _System Management** **_and then delegated permission to the SCCM Servers to update this container.
Create the Container
Launch the **ADSI Edit **tool (Start –> Run –> adsiedit.msc), and Connect to the Default Naming context on your Active Directory Domain; ensure you are using an account with privileges (for example Domain Administrator), so that you can create the System Management container.
Expand the Default Naming Context –> DC=xxx,DC=xxx,DC=xxx branch. Locate and right click on the container named CN=System, on the context menu select New -> Object
The Create Object _dialog will be presented, in the _Select a class list, choose the option Container and click Next
On the second page, in the Value text box, enter System Management and then click on Next
Finally, we just need to click on Finish to complete creating the new container.
You can now close the **ADSI Edit **tool
Delegate permission to the container
Launch the **Active Directory Users and Computers **tool (Start –> Run –> aduc.msc), ensure you are using an account with privileges (for example Domain Administrator), so that you can delegate permission to the System Management container.
Expand the System branch. Locate and right click on the container named System Management, on the context menu select Delegate Control…
The Delegation of Control Wizard is presented, click Next. On the User or Groups page, click Add.
In the Browse Dialog, click the button Object Types, select Computers and click OK. In the server name field enter the names of the System Centre 2012 servers which will be installed and configured as the Site Servers, then click on Check Names, and finally click OK. Back on the User or Group page click Next
On the Tasks to Delegate page, Choose Create a Custom Task to Delegate, click Next
On the Active Directory Object Type page, select the option This folder, existing objects in this folder and creation of new objects in this folder and click Next
On the Permissions page, enable the check box next to all 3 permission types
- Creation-deletion of specific child objects
In the permissions list box, enable the check box FULL CONTROL, then click Next
And Finally, read the summary, and click on Finish
That’s that done, now close out of ADUC.
Important reminder – As you add new site servers repeat this task – or just create an AD Group and delegate it the permissions needed, and be sure to keep that group up to date with each new site server change you make
Last step in the AD perp work is the Schema. this is very simple, but you must have the correct permissions to do this, and since this is the Schema, if you have procedures in your organisation for applying these type changes, be sure to follow them!
Logon to a Domain Controller (not mandatory, but a good practice) with an account that has privileges to extend the AD schema. Next, Launch a Command Shell, with administrative privileges (right click on command, and select _run as administrator _from the context menu)
Now, Navigate to your SCCM 2012 Media, and into the folder _SMSSetupBinx64. _From here we will run the utility Extadsch.exe
Assuming you have the correct permissions, and all runs to plan, you will see similar to the following presented:
<05-01-2012 04:05:04> Modifying Active Directory Schema - with SMS extensions.
<05-01-2012 04:05:04> DS Root:CN=Schema,CN=Configuration,DC=corpnet,DC=liox,DC=org
<05-01-2012 04:05:05> Defined attribute cn=MS-SMS-Site-Code.
<05-01-2012 04:05:05> Defined attribute cn=mS-SMS-Assignment-Site-Code.
<05-01-2012 04:05:06> Defined attribute cn=MS-SMS-Site-Boundaries.
<05-01-2012 04:05:06> Defined attribute cn=MS-SMS-Roaming-Boundaries.
<05-01-2012 04:05:06> Defined attribute cn=MS-SMS-Default-MP.
<05-01-2012 04:05:06> Defined attribute cn=mS-SMS-Device-Management-Point.
<05-01-2012 04:05:06> Defined attribute cn=MS-SMS-MP-Name.
<05-01-2012 04:05:06> Defined attribute cn=MS-SMS-MP-Address.
<05-01-2012 04:05:06> Defined attribute cn=mS-SMS-Health-State.
<05-01-2012 04:05:06> Defined attribute cn=mS-SMS-Source-Forest.
<05-01-2012 04:05:06> Defined attribute cn=MS-SMS-Ranged-IP-Low.
<05-01-2012 04:05:07> Defined attribute cn=MS-SMS-Ranged-IP-High.
<05-01-2012 04:05:07> Defined attribute cn=mS-SMS-Version.
<05-01-2012 04:05:07> Defined attribute cn=mS-SMS-Capabilities.
<05-01-2012 04:05:07> Defined class cn=MS-SMS-Management-Point.
<05-01-2012 04:05:07> Defined class cn=MS-SMS-Server-Locator-Point.
<05-01-2012 04:05:07> Defined class cn=MS-SMS-Site.
<05-01-2012 04:05:07> Defined class cn=MS-SMS-Roaming-Boundary-Range.
<05-01-2012 04:05:08> Successfully extended the Active Directory schema.
<05-01-2012 04:05:08> Please refer to the ConfigMgr documentation for instructions on the manual
<05-01-2012 04:05:08> configuration of access rights in active directory which may still
<05-01-2012 04:05:08> need to be performed. (Although the AD schema has now be extended,
<05-01-2012 04:05:08> AD must be configured to allow each ConfigMgr Site security rights to
<05-01-2012 04:05:08> publish in each of their domains.)
Now we can focus on getting the servers installed, that’s going to take a bit longerTags: AD · SCCM · WS/SC Previous Post: Deploying SCCM 2012 Next Post: SCORCH Best Practices–Going Live