Join David M. Franklyn for an in-depth discussion in this video Installing a Configuration Manager primary site, part of Microsoft System Center Configuration Manager Essential Training.
- [Instructor] So now that we've checked both the domain infrastructure prerequisites and the prerequisites on the primary site server itself, we can actually install NorthAm CFG2 as the primary server. So we're going to go to File Explorer, and in File Explorer you'll see we have on the E drive, the installation media, and we simply double click the splash.hta in the root of the installation media, say OK to this open the file popup, and the Microsoft System Center Configuration Manager installation applet appears.
So we're going to click Install. And now we get the System Center Configuration Manager Setup Wizard. And you'll note, we actually have the applet to install, and then the wizard as a separate window. So in the beginning, in the Before You Begin page, it tells you some things you need to be aware of like SQL Server is installed on this computer or available to this computer, and that you know the fully qualified domain name of this computer or the computer running SQL Server, actually both of them, so you can make that type of connection.
In our case, SQL Server is running on the same computer that we're going to install the primary site server on. So let's go ahead and click Next here, and here are options to install. So we can install this as a Configuration Manager primary site or we can install it as a central administration site. Later in the course, we'll actually do that. So we're going to install this as a Configuration Manager primary site, but we're going to install it as a stand-alone.
Later, we'll extend the site to include the central administration site. It's important that you know how to do this because depending on the size of your enterprise and the bandwidth you have for your enterprise overall, you could probably in most cases, with very modern, fast network connections and wider network connections, get by, even on a global scale, of having only a single stand-alone primary site. It can handle up to 150,000 client devices.
However, when there is limited bandwidth in locations, it may take a lot of time to get instructions to clients in those locations and also return information to the management point from the clients. So in that case, you would have additional, either primary sites or even child secondary sites, depending on the bandwidth requirements and whether there's an IT organization in that location. But in our case, we're going to do a typical installation here which is to use the typical installation options for a stand-alone primary site.
So we're going to go ahead and click Next. And it tells us in the popup that later on we can expand the site into a hierarchy with a central administration site. Do you want to continue? And we'll say Yes, since we can do that later on. And we're just going to install the evaluation edition of this product for the purposes of this course and click Next. And we have to accept the license agreements. There are four of them. Of course, it behooves you to read them in every case.
For brevity's sake, we won't here. Click Next, and now we need to provide a download location at this point to ensure that there are all the prerequisites necessary, not to install Configuration Manager, but to install various specific things within it, we need to provide a download file location for it. So in our case, if you click Browse, you see it just shows the Desktop. So what we're going to do is just go to File Explorer, and in File Explorer we'll go to a drive, and we're going to create a new folder, and this folder we're going to call it PreReqDownloads.
Now can put that in as a drive path which is accessible locally to this machine, but later on, when we install Configuration Manager on other servers, we could actually point back to this location as a network share if we share it. So let's go ahead and do that. So we'll click Enter here. Now we'll right click PreReq and say Share with, Specific people. We'll add the Everyone group to Read and say OK, and then we'll say Share.
And it has now shared it in accordance with this particular universal naming convention, \\NORTHAM-CFG2\ PreReqDownloads. We'll say Done to that. We can now close or minimize Explorer and put that actual path in here now. And there it is, and then click Next. And at this point it will download all the cabinet files necessary for the various components to be installed. There are many of them, so it will take approximately 10 minutes or so to do this download and then checking of these files.
Because we actually put this to a network share that other potential site servers can get to, it will skip the 10 minute download for those other servers and come back here and check them directly which will benefit us in the amount of time it takes to do the installation. And once we get to the last file, as we are at now, it will verify and then take us automatically to the next page. And now we're at the Site and Installation Settings page.
And here we will add our site code. Now this is something you need to make up for your site that is intuitive enough for you to use but only accepts three characters, and you cannot use any Microsoft reserve character like SQL or WMI. So in our case, we're going to call this NA for North America, that's where our domain resides, one, for the first primary site in North America. And for the site name, we're going to use DaveMCT.com North American Primary.
We're going to set the default installation folder path and also, by default it installs a Configuration Manager console. So unless you don't want a console, and you should, you don't want to uncheck that box, and then click Next. And the Diagnostic and Usage Data is just some information with hyperlinks on it that you can go to to read further about what type of data Microsoft may collect or not, then click Next. Now in this case, we can setup a Service Connection Point.
Because we are later on going to expand this into a central administration site, and when we do so we have prerequisites for that, one of these is the individual primary site that already exists cannot be a service connection point, we're going to skip this for now. If you only were going to install a primary site, a stand-alone primary site and nothing else, then obviously you want a service connection point. That way, clients can find the service connection and the management point and the distribution point.
But in our case, we're going to skip it because we're going to add this to the central administration site later. So Skip for now, click Next. And now we have our Settings Summary, and it shows all the values that we've previously chosen. We're going to click Next and then it will do another installation prerequisite check. Click Next. And as long as there's no failures here, we can proceed. If there are any failures, we need to correct them and then click the Run Check button again.
Warnings are typical in some cases. It prefers to have, for example, in the warning showing right now, more memory for the SQL Server. But we have as much memory as we can hold on this computer, so that's acceptable for us. And we're going to now say Begin Installation. Notice that that doesn't appear. It doesn't become enabled until it's gone through this check and there are no failures. Warnings again are acceptable, so now we're going to click Begin Install, and now it will install.
This process takes a long time, anywhere from 40 to 50 minutes on average in my experience. Depending on the performance of your particular computer you're installing it on, it can take longer or shorter. So let's say the window would be 30 minutes to a full hour. But again, my experience has been 40 to 50 minutes. Okay, as you can see, the core setup has completed.
So it has finished correctly. All the various components have been installed. We can now close the System Center Configuration Manager Setup Wizard, and close the splash screen. In our next demonstration, we'll come back in and do the post-installation configuration tasks.
- 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