Join David M. Franklyn for an in-depth discussion in this video Ensuring domain prerequisites, part of Microsoft System Center Configuration Manager Essential Training.
- [Instructor] Alright, so now we're going to check our prerequisites for our configuration manager primary site installation. We're going to start off by checking the domain level prerequisites, and it's important that we login each time as a domain administrator. So we need to be explicit on that. I'm here on the domain controller, DC1, and we're going to login to that computer using our password of capital PA55W.RD.
And this will bring up server manager. And the first thing we're going to check is our domain functional level. So let's go ahead to tools and bring up the active directory users and computers console. And in this console we simply right click the domain name and say raise domain functional level. And as you see, the current domain functional level is 2012 R2. We could raise it to 2016, we don't need to. Remember that our functional level should be at 2008 as a minimum, so we're good here.
I'm going to cancel that. Also, let's check to see if we our system management container. So we're going to go to the view and in the view menu select the advanced features. We'll expand now our domain and we see the folder named system, let's expand that, and we're looking for the system management folder. And there is no system management folder in this area at this time so we'll have to make one. So we're going to minimize this and now we're going to go to another tool called ADSI edit.
That stands for the active directory services interface editor, and open that up. Now when we open it up, here we see in the console tree we have no context yet in it. So we need to go ahead and add our context. So the first thing we're going to do is right-click ADSI edit and say connect to. And in the connection, what we're going to do now is check first before we get in and make the system management container, let's go in to check to see if the schema has been extended.
So in the select a well known naming context, we're going to use the dropdown menu and select schema. And then say okay. And in the console tree, we expand schema, and then choose CN equals schema and the rest of the configuration domain controller equals Dave MCT domain controller equals com. Expand that, and in the details pane in the middle, you'll get a whole bunch of attributes and classes that the schema is based on.
There are thousands of them. These are listed alphabetically, so we want to scroll down and find the one that is labeled CN=ms-SMS. Those are the schema objects for configuration manager. So, we see CN=MS-SQL. And CN=ms-SPP, and see CN=ms-RRAS, and the very next thing alphabetically is CN=ms-SPP.
So we can tell that we do not have SMS and we do not have the schema extended. So what we're going to do now is extend the scheme then we'll come back to ADSI edit and check to see that the configuration manager schema objects have now been added, and then we can go ahead and make our system management folder. So what we'll do here, minimize, and now go to file explorer. And in file explorer, we see we have the installation media for system center.
We're going to expand that. We're going to expand SMSSETUP, and we'll expand the BIN directory, B-I-N, and then finally x64. And in the x64 we need to select that and scroll down and we're looking for a program called extadsch.exe. And here it is right here. This is the program that allows us to extend the schema.
So we go up to the URL bar in file explorer, click it, and then right-click and copy the path. We can now close file explorer. And now we go to the start menu, right-click it and select command prompt admin. And we're going to type in the letter d because that holds our installation media and now we can type in cd space and now simply paste in the path.
And here now that we have the full path, we can type in the name of the program, ext and just hit the tab key to complete it, and that is the full name of the program and now we'll press enter. And as you see it reports back that it successfully extended the schema. So let's go ahead now and close the command prompt and reopen ADSI edit, and what we want to do here is selecting the same schema path. Go ahead and refresh.
And now scroll down and see if we have the active directory schema objects for configuration manager. And there they are. So we have CN SMS, we have quite a few of them have been added. So that proves that we've extended the schema. So now we can go on to making our system management container. So what we're going to do now is in ADSI edit, in the console tree, right-click it again and say connect to, but this time we're going to choose the default naming context.
And in the default naming context, we'll go ahead and expand that, expand the name of our domain, expand CN=system, and as you can see, as before, there is no system management folder or container, so we're going to make one. We right-click in the console tree, CN=system, and then select new and finally object. And the create object wizard comes up. And in the create object wizard we're going to select container and then say next and give it a name and a value of system management, and say next.
And we're not going to create extra attributes for it so we can finish. And now you will see we should have the system management folder. Now at this point, and we can do this from the active directory users and computers or we can do it here, and since we're already here, we'll do it here, which is to give permissions to the computer that is going to be running configuration manager full control of this folder. So we can right-click the folder in the console tree, that is the CN=systemmangement, and go to properties.
And in properties, go to security. And what we need to do now is add the computer account. So click add. And when we click add, it brings up the select users, computers, service accounts or groups window, and right now it's set to just select users, groups, or built-in security principals, so we want to click on object types and check computers so we can also select computer accounts. And now, in the enter the object name to select, we'll go ahead and type in northam, which is the name of our computer, cfg2, and click check names.
And you'll see, it comes up, it found it in the active directory, we'll say okay, and now, selecting northam, we're going to give it full control, but we're not done because we have to change what it has full control of. It's not just this folder. So we click the advanced button and in advanced we're going to select northam cfg and then press the edit button. And these are all the specific permissions that a configuration manager computer needs to have but note that it applies to this object only which is the container.
So we want it to be this object and all descendant objects. So in the dropdown list applies to, we'll select that, and then say okay. And then we can say okay again, and finally okay a third time. We can now close ADSI edit. So that completes all the steps we need to do to check the prerequisites for the domain infrastructure. In this case, we had a couple of things that were not present so we've added them, and now we can go over to the configuration manager site server and check the prerequisites there.
- Planning and deploying a standalone primary site
- Ensuring domain and site server prerequisites
- Planning and expanding a standalone primary site
- Planning and deploying a multiple-site hierarchy
- Planning resource discovery and client deployment
- Managing content and replicating data in Configuration Manager
- Configuring Internet and cloud-based client management
- Advanced monitoring
- Upgrading to Configuration Manager current branch