Join David M. Franklyn for an in-depth discussion in this video Installing an East primary child site, part of Microsoft System Center Configuration Manager Essential Training.
- [Instructor] Now in this demonstration, we're going to install configuration manager and create a new primary site on the sub-domain named East.DaveMCT.com. And this is located in Seoul, South Korea. One of the more important things, when we talked about the prerequisites for installation of configuration manager was using the same account that we used to install the central administration site. So in this case, we need to log into this computer as the DaveMCT, that is, the forest root domain administrator.
So let's go ahead and do that. And we're going to type in directly the name of the domain and the administrator, and then the password. And since we've already mounted the installation DVD for configuration manager, current branch, we'll go ahead and double-click on that. And then click the splash screen. And this will bring up the system center configuration manager splash screen, and we'll go ahead and click install.
And on the Before You Begin page, click next. And note now, we're going install a configuration manager primary site, but we're not going to use the use typical installation options for a stand-alone primary. It's not a stand-alone. We already have the central administration site running on central-cfg1, and we have another primary site running on northam-cfg2, which is the North American primary. And in this case, we're going to be installing the east primary.
So we click nothing else except install a configuration manager primary site. Click next, and the product key. We're going to install the evaluation edition. We're going to accept all the license agreements. And this brings us to the prerequisite download, and if you remember, we have that already downloaded on the northam-cfg2 computer, and there it is, the prereq downloads, it's a share. We'll click next, and again, this takes a couple minutes.
And in the server language selection page, you can select other languages. I'm going to go with the default English. And on the client language selection page, once again, the same. And now, in the site code, we're going to call this new site ES for east site, one. And the site name is going to be the domain name, we're in East.DaveMCT.com. And this is the primary site for that domain.
We're also going to ensure we install the configuration manager console, we do need that. Click next. And now, because we're joining the primary site to an existing hierarchy, and we know our central administration site server is central-cfg1, we type in its name here. And it is the fully qualified domain name we need to put in. So we'll actually put in the domain name also. And now click next. And here in the database information page, it's going to create the database called CM_ES1.
And that would be on this computer. Of course, not on the central, it has a database on the central. But this database will wind up talking to the database in the central, as will the North American server database will talk to the central, and therefore, as we create things here, in the East primary site, these will actually replicate up to the central site, so we can see them in both locations. And the benefit of this is, we can use the central administration site as if it was one big overall system centered configuration manager console for our entire infrastructure.
But we're going to now say next on this, and as I mentioned before, we have set up SQL server to put both the data files and log files on the D drive. We have an additional drive. It's not the system and the boot drive, which is normally C, so we're not going to interfere with the data that's saved there, and the necessary boot and start-up and system files. If we needed to later expand a drive, we can do so to a data drive, but we cannot span, necessarily, our system and boot drives.
So this ensures that we're not going to ever reach a critical place where we run out of disk space. In the case of this, for the D drive, we can expand it. We can also create additional data files for SQL server and put them on other drives. So in this case, notice it is the D drive, we're going to click next. The SMS provider is going to be East-CFG3, click next. And then the client computer configuration settings, we are not going to use HTTPS at this time, so we're just going to configure the communication method on each site system role.
In this case, that will be at first, the management point and the distribution point. So let's click next on that. And in this case, you see for the management point and for the distribution point, both are HTTP, and that's what we want. We're installing both. Click next, and here's our summary. And now when we click next, it will go into the prerequisite check. And again, we don't want to have a failure here. If we have a failure, we have to fix it.
And when we have that we need to go and run the check again. Now previously, we've seen the warnings about memory allocation. That we have for the SQL server. And we already said, the best practice memory is way up there, 96 gigabytes. We have less, but we have an adequate amount to still install configuration manager. The other one we've got, now a new warning, if you will, is to verify the site server permissions to publish in the active directory.
And that means that we've got to have full control permissions to the system management container in the active directory domain. And we did that before in ADSI Edit on the domain controller. Of course, in this case, that system management container is in the domain DaveMCT. We are in the child domain, East.DaveMCT. So let's go ahead and go over to the East domain controller.
And here on the East domain controller, let's go ahead and run ADSI Edit. And now, in ADSI Edit, we'll go ahead and connect to the default naming context, which is for this domain, say okay. And as we expand that, we'll see it's for the East, so we have DC = East, DC = DaveMCT, DC = com. So it uses a DNS structure of naming things.
We're in the top level dot com, and then we're in the DaveMCT domain within that, but we're in a sub-domain called East. We're in a sub-domain of the DaveMCT.com domain. So let's expand that, and now we'll go to our system container. And note, we don't have, repeat: don't have, a system container here for our East domain. So let's go ahead and click here on CN = System, and say new object, and this is going to be a container.
And we're going to say next, and the name of this is going to be System Management, and we're going to say next, and finish. And now that we have the system management container, let's apply some permissions to it. So we're going to right-click it and go to properties. And then to the security tab. And in the security tab, we need to add the security accounts, not only of the East-CFG3 computer, but also the Central, because they are going to talk to each other and write stuff to this container.
When we are done this, we need to go back to the system management container in the forest root domain, and add East-CFG. So let's go ahead and click add here. And then the object types we need to ensure our computers are selected. And we can do multiple computer accounts here, so first let's put east-cfg and check names. And that comes up in capital letters, just to let you see that that is indeed found in the domain.
We're going to click the semi-colon, we're going to change the location to the forest root, and now say central and check names. And there it is, it found it. And then finally, we're going to put in a semi-colon, and put in northam, and check names. So now we see all three computer accounts have been selected, we can say okay. And for each one of these computer accounts, what we want to do is give it full control, so there's this one, the northam.
And scroll up, and we're looking for east and full control, and finally for central, the central computer account, give that full control. Now we're going to click the advanced button to make sure that they can also have full control over any descendant objects. So we're going to do this for each one of these accounts. For east, go to edit, and make sure it applies to in the Applies To drop-down. This object and all descendant objects, okay.
To northam CFG, same thing. And finally, to central. And then okay. And then okay. And finally, okay once more. And we can close ADSI Edit. We're done now on the second domain controller, DC2. The last thing we need to do is go to the root forest domain controller, and in ADSI Edit there, we need to check that all of the computer accounts have full control access over the system management container there.
So let's go ahead and take a look. And here we are now on DC1, which is the forest root domain controller for the forest root DaveMCT.com. So we'll go to ADSI Edit here, and one thing you'll note about ADSI Edit, if you close the console, the ADSI Editor console, while you are at some particular level in a particular naming context, it keeps it open for you the next time you return. So we already see it's at this level of the domain.
So we'll go down now and expand that, and go to the system folder. And then to the system management folder. We'll right-click the system management folder, and go to properties. Now earlier, I did add the computer account for East here. We're just going to verify it. And here it is. And we see it has full control. It's been selected, it has full control. We go to the advanced button, and in East, we can see that it's this object and all descendant objects.
So this is more or less a check. So that looks good. We're going to say okay to that, we're going to say okay again, and close ADSI Edit on DC1. And now we can return to the East-CFG3 computer and finish this set-up of configuration manager. So here we are back on East-CFG3, and as you see, we still have the set-up wizard running. So one of the warnings we got was it needs to be able to publish in the active directory system management container.
We've done that. We've ensured that this will be done. And now, that is just a warning, we can begin the installation. So we'll click Begin Install, and again, depending on the performance factors of your computer, especially the amount of RAM and the speed of your CPU cores, as well as your disk IO and its overall speed, can take anywhere up to an hour. The faster the machine is in all those different aspects, then the quicker this will happen.
But nevertheless, it normally takes anywhere from 20 to 40 minutes. Okay, now we can see that the core set up has completed, and it was a really pretty fast time, but you can see here that some of these steps are still being done. In that case, before we proceed to go to our next step, which is to create a secondary site, we want to make sure that everything has been properly replicated up to the central administration site.
Now this will take some time to do. Generally speaking, 10-15 minutes. Sometimes, if there's a lot of data to transmit, more, but since this is a brand new primary site, there won't be too much. So we can actually close this now and exit out of the install. And now, we'll go and check the central site and see what it has on this particular site we just created. So here we are back on central-cfg1, and what we want to do now is go to the configuration manager console.
And in the console, we want to make sure we're in the administration workspace, under site configuration sites. And since we looked at this last and then closed the console, we see it may need to be refreshed. So let's go ahead and refresh it by clicking the refresh button in the ribbon. And as you can see, we still haven't gotten our ES1 site to show up here because, as we saw when we closed the installer, while the core setup was finished, it still had some tasks to do.
So we'll just wait for that finish and then we should see it here. Okay, it's been a few minutes, and I just tried another refresh, so sometimes closing the console and opening up the console again will cause values to populate that just aren't showing up. So let's give that a try. We'll close the configuration manager console. And now we'll reopen it. And let's go back to administration workspace, site configuration, and sites.
And there it is. Now we see the ES1 site. We see its ES1 site code and its parent, CAS. So this completes this demonstration.
- 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