Join David M. Franklyn for an in-depth discussion in this video Installing a site hierarchy, part of Microsoft System Center Configuration Manager Essential Training.
- In this demonstration, we're going to install the central administrative site via the stand-alone primary site expansion. So, the first thing we need to do is go to the force root domain controller and add the new computer accounts, that are going to be new site servers in this case. We're going to have to put them into the ownership or full control of the system management folder in the active directory. So, we're going to Tools and we're going to go to ADSI Edit.
In ADSI Edit, we need to add a naming contact, so we're going to say Connect to, and then in this case we want to connect to, in the connection settings, the default naming context and then expand the default naming context. Expand through the domain name and then go down to the system folder and find the system management folder. And what we want to do in the system management folder is right click it and go to Properties and then the Security tab.
So, in this case you see the NORTHAM-CFG2$, which is the computer account for our stand-alone primary server, has full control of this folder. We need to add the same for the other two computers. The first will be the CENTRAL-CFG1 and the second will be the EAST-CFG3. So, let's click Add on that. For our object types we need to select Computers. We can say OK. In the first case we can simply type central, and then Check Names.
Because the East is in another subdomain, we can change the location to that subdomain by going to Locations and expanding through to the East.DaveMCT.com subdomain, or child domain. And then type in a semicolon and just the east-c and Check Names. And as you see, it found it. And we'll say OK to that. In both cases, both computer accounts. I'm looking for central.
Both of them have to have full control. And we still need to go to the Advanced and make sure that Descendant Objects are also checked. So we go to Advanced and select CENTRAL-CFG and then Edit. And notice it's only this object. We need that to be this object and all descendant objects. And do the same thing for the EAST-CFG3 computer account. And then, say OK to all open windows and we can now close the ADSI Edit window.
Now we need to go over to the NORTHAM-CFG2 computer and add these new server computer accounts to the local administrators group. So, here on NORTHAM-CFG2 we go to the server manager tools. And then to our Computer Management item. And then Computer Management. In the console tree expand Local Users and Groups and then select Groups.
And in the Details Pane double click the Administrators group. And in this case we need to add the computer accounts. We're going to add, actually, all three of them here just so that they all can trade data with each other. So, we can say Object Types and select Computers. Say OK to that, and for the DaveMCT domain we actually have two. We start off by putting in the Northam computer account, Check Names. We can put a semicolon, and then add the central computer account, or at least the first few letters of it.
Check Names. And then a semicolon, but we need to change the location in the domain to the East domain and then add the East computer which is named EAST-CFG3. Now that we have all of them, we can click OK. And then OK again. And that step is done. At this point, we're going to go ahead and do the installation of the configuration manager as a new central administration site on CENTRAL-CFG1.
Here we are on CENTRAL-CFG1, and it's very important when we install Configuration Manager to always do it as the domain administrator account. The administrator account shown here in the sign-in page would be for the local administrator account. So, we're going to go to other user and type in the name of the domain, make it explicit, and administrator for the account and the password of Pa55w.rd and then click Enter.
We're now going to go in the taskbar to File Explorer. And in File Explorer, you see we've already inserted the DVD for the installation media for Configuration Manager. Double click it and click the splash.hta to bring up the splash screen. Click OK. And the splash screen comes up. And from here we can click Install. And it brings up the Before You Begin page. We'll click Next on that.
And now what we're going to do is install a Configuration Manager central administration site. So, we're going to choose that option radio button and click Next. We're going to then in the Product Key page click install the evaluation edition of this product and then click Next. On the Product License Term page we'll accept all of the licenses, checks. Again, you might want to look at these license terms by expanding them.
And now, we have the downloaded prerequisite files available to us still on Northam, so we can put in the actual UNC to that path by first selecting use previously downloaded files and typing it in. So, that is going to be on northam-cfg2 backslash, and there it is. The PreReqDownloads item, and click Next.
Now, it will verify all these and it can take a few minutes to do so. You will note there's not as many as there were previously, there were 54 files. Here, for the central administration site, we only have 15 that it needs to review. This takes us next to the Server Language Selection page. You can see English has been selected but no other languages. If you have additional languages or a language you want to add, as you scroll through it you'll see the choices. You can select any or all of those.
I'm going to click Next. And now we come to the Client Language Selection. And it is set up the same way and the same factors apply. I will click Next. And now we're going to give it a site code. And in this case, it's going to be a central administration site. So, I'm going to use the site code CAS. And then the site name. We're going to call this the Davemct.com Central Administration Site.
Notice the Configuration Manager console will also be installed. We want to have that, so do not uncheck it, and click Next. And now, we can specify. We have a section to specify whether this central administration site is going to be in a brand new hierarchy of sites or is it expanding an existing stand-alone primary site. And we are actually doing that. We already have Northam as an existing primary site, so we're going to click that and now put in the fully qualified domain name of that computer at northam-cfg2.davemct.com and then click Next.
And the SQL server instance is chosen here. So, it's going to create on this very same computer that is Central-CFG, it's going to use the SQL server installation that it has, it's going to use the default instance. So, we're not going to change anything there, and it's going to create a database called CM_CAS for the site name. Notice also that port 4022 is the server's broker port, needs to be open. It will make communications between the two databases.
I will click Next. In this case, I have purposely put the SQL server database files on another drive on this system. So, in that case, it's the D: drive. This can be a good idea, a central administration site can have a lot of data in the databases. For many servers the boot and system drive, also known as the C: drive, is smaller than other additional data drives you can put in the system.
If we run out of space on the C: drive, it can be a very unpromising situation for us. So, by putting the database original files, both the data files and the log files, onto a different drive, we can then expand it if we need to or even move other files to other drives. We don't have the restriction of this being on boot and system drive and causing problems for us with all the stuff that's already installed there.
So, we're going to click Next and now we provide the SMS provider fully qualified domain name for this computer and it's filled out already so we can click next. For the Diagnostic and Usage Data page simply click Next. For the Service Connection Point, previously on the stand-alone we didn't create one because we knew we would have to remove it. In this case, we are now going to put the service connection point on Central.
So, we have it here. Yes, let's get connected. Click Next. And at this point, everything's ready to go. And it's going to run another prerequisite check for us, so we click Next. What we're looking for here is no failures. If we have a failure, we have to stop, fix it, and then run the check again through the Run Check button. We can expect to see warnings and in this case, again, the warning is about memory. It would like a little more for best practices, but in our case it is sufficient and we will click Begin Install.
And at this point, the installation will start. It can take several minutes, again, depending on the performance factors of any particular server that you have. It can be quicker, it can be slower. My experience, given the performance factors I have on most computers, is about from half an hour to 50 minutes. So, 30 to 50 minutes. It could very well finish earlier than this. But that is a ballpark figure because, again, it depends on different factors on that computer, how much RAM it has, how fast the processor is, how many cores it has.
It can just take a longer or shorter period of time based on that. Also, the disk IO back and forth, communications between the actual data that's put on the disk and the processes that are running to create it. So, what we're looking for is after several minutes we should see the setup complete. So, we'll wait for that. And now it is finished. So, this one took 22 minutes and it tells us the core setup is completed.
So, we can close the Configuration Manager setup wizard. And also close the splash screen. And now we can close File Explorer. One thing you should note about installing a CAS site, especially when you're expanding from a stand-alone primary site, is once it's installed, once that CAS site is installed, it goes and finds that stand-alone primary site which is now a child site, and tells it to start feeding it stuff from its database and it creates those database objects on that central administration site.
So, it takes a while to do that, and during that time if you try to open up the Configuration Manager console, it will tell you it's in read-only mode because it's in this maintenance mode of doing all this functionality. So, the best thing to do is let that run for a while. So, we won't open up the Configuration Manager console until approximately 15 minutes after we've closed the Completed screen. And we're at that point now, so what we're going to do is go to the Start menu, and we see the Configuration Manager console.
We click it, and it opens for the first time. Now, you may get a popup that says it's still in the maintenance window time. In our case, we waited enough time. One thing I do like to do here, like I did before in creating the stand-alone site, is to go to the taskbar and pin Configuration Manager Console to the taskbar so we can get to it at any time. But note we have all of our various workspaces.
We want to go to the administration workspace. This is the most interesting area for us and then go to Site Configuration in the console tree, expand that and go to Sites. And here we can see that we now have CAS as a central administration site, but also NA1 as the primary site, which previously was a stand-alone, now showing as a child of the CAS. So, that's what we wanted to see, and that's the way it should be. One other thing we can do is check the monitoring workspace and go to Site Hierarchy and you will see a map, actually, of the sites and their status.
Here, the alert status of both of them is OK. If we go to our System Status and then Site Status, we can see everything looks good here. If we go to our Component Status, everything looks good here. Now, there are some additional components that are added for a CAS and sometimes those still take time to run. Some of these database notification where the servers will talk to each other using that, the configuration monitor, and the hierarchy.
But, again, they're just warnings waiting to be completed. And that's how you actually create a central administration site and a site hierarchy within Configuration Manager current branch.
- 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