OK. Finally! All what has to be done is done with regard to prepare the infrastructure for a smooth SCCM 2016 installation, and everything is ready now to proceed with the deployment without any issue with a kind of Next/Next game.
Mount the SCCM 2016 .ISO file and follow the steps.
Obviously, click on Install link
This is a the first server in our simple lab, so we’ll select the Install a Configuration Manager primary site option
Because it is a lab, we’ll select the Install the evaluation edition of this product option to have 180 days evaluation
Accept the License Terms
To avoid this server to connect to Internet to download the prerequisites files, we will select Use the previously downloaded files to use the already downloaded files described in the previous post
The wizard goes through the verification of the prerequisites files
Select the languages that you would like eventually to be displayed in the SCCM admin console
You should select the languages that you client devices use in you environment
Provide an SCCM site code and a name. Site code in my deployment will be NYC, and Site name will be New York Head Office. I’ll also choose to install the ConfigMgr console on the server.
This is a new deployment and no hierarchy has been configured yet, so we’ll choose the Install the primary site as a stand-alone site.
Provide the SQL Server FQDN and the database name that will host the ConfigMgr configuration.
I’ll keep the default data and log files paths, and click on Next
The SCCM SMS Provide is a kind of service that acts like a proxy for the Site Server to access the Site Database. In other words, the Site Server does not communicate directly with the database, but has to pass through the SMS Provider to get access. SMS Provider can be installed either in the same server as the Site Server, or in the Site Database.
Having said that, choosing the where to install the SMS Provider in either location can have its pros and cons. Installing it on the Site Server will not consume resources on the Site Database, which allows better site database performance, but will use system and network resources that could be dedicated to site server operations. On the othe hand, installing it on the SQL Server hosting the Site Database allows it to always be in contact with the Site Database, and offload the SCCM console installed on the Site Server for better performance, but can actually uses system and network resources that could be dedicated to Site Database operations.
In this infrastructure, we will install it on our Site Server NYC-CM1
HTTPS would not be needed as this in only a lab. We’ll go ahead and select Configure the communication method on each site system role, and click on Next
Review the Settings Summary and double check that you have not missed any option, then click on Next
The Prerequisite Check will proceed with the verification of all needed components, to avoid any installation corruption. Once the checking process is done, click on Begin Install to start the SCCM 2016 binaries.
Take a deep breath and go grab a cup of coffee, as the installation will take a bit of time. In my installation, my SCCM had two CPUs and 16GB of RAM, and the instalaltion took approximately 50 minutes.
Installation is finished and some beautiful green ticks appeared on the installation window. Let’s close the installation window and launch the SCCM console
Go to start, and launch the SCCM console.
The server is not connected to internet for the moment. We’ll ignore this warning and click on OK.
Our SCCM 2016 server is now installed and fully functional.
We may enjoy now and test all the features provided by this great tool. In future posts, I will go through some details about the SCCM administration, and the most common tasks that can be achieved with ConfigMgr 2016.
Thanks for reading!