In the previous blog post we looked at the different prerequisites that need to be met, before you can install SCCM 2012 R2. In this blog post we will go through the installation process for a stand-alone Primary site.
At the time of writing the latest version(s) for Microsoft System Center 2012 Configuration Manager are SCCM 2012 SP2 and SCCM 2012 R2 SP1. Both of them actually share the same binaries. When you try to download the evaluation version of SCCM 2012 R2 SP1, you will notice that you can download two files,
SC2012_SP2_Configmgr_SCEP.exe – Includes the binaries for SCCM 2012 SP2 and SCCM 2012 R2 SP1
SC2012_R2_SP1_Configmgr.exe – Utilized to activate the R2 features.
So you first install SCCM 2012 SP2, and if you want to activate R2 features, you can do so by launching splash.hta found in the installation media extracted from SC2012_R2_SP1_Configmgr.exe
1. Install SCCM 2012 SP2
Before you begin, put an empty text file called No_sms_on_drive.sms on the root drive of each drive you don’t want SCCM 2012 R2 to put content on.
1.1 Launch Splash.hta from the ConfigMgr installation media extracted from SC2012_SP2_Configmgr_SCEP.exe
1.3 Click Next
1.4 Leave it at the default selection of Install a Configuration Manager Primary site, click Next
1.5 Enter a product key, or select to install the evaluation edition of SCCM 2012 R2, click Next
1.6 Accept the license terms, click Next
1.7 Accept the license terms for SQL Server 2012 Express, SQL Server 2012 Native Client and Microsoft Silverlight 5, click Next
1.8 I’ve already downloaded the required prerequisite files, so I’m just going to select Use previously downloaded files and provide the path to those files. Otherwise, you have the option to download them, here.
If the server you are installing SCCM 2012 R2 on, does not have an internet connection for whatever reason, you can download these files on a server with an internet connection, by using the setupdl.exe tool, which you can find in the installation media at \SMSSETUP\BIN\X64
1.9 Downloaded prerequisite components will be verified
1.10 Select the supported languages appropriate for your environment. It is possible to change this setting post installation. Click Next
1.11 Select the SCCM 2012 client supported languages appropriate for your environment. It is possible to change this setting post installation. Click Next
1.12 Specify a unique three character site code, provide a site name, and specify the installation folder. Keep the check mark for installing the Configuration Manager console
1.13 Select Install the primary site as a stand-alone site, click Next
1.14 Click Yes to continue. Prior to SCCM 2012 SP1 and SCCM 2012 R2, it was not possible to join a stand-alone primary site to a CAS after the installation. But since those two versions, it is possible to install an empty CAS above the stand-alone primary site.
1.15 The default selections are fine if you are co-locating the SQL server on the site server, and kept the default instance ID when you installed SQL Server. Click Next.
1.16 Specify the appropriate paths, I’m just going to keep the default paths provided by the installation wizard, because I made default selections while installing SQL Server
1.17 SMS Provider will be installed on the site server, so just click Next
1.18 No Public Key Infrastructure has been set up, so just make the selections in the screenshot below, then click Next
1.19 Install the Management Point and the Distribution Point on the site server, and once again since no PKI has been configured, choose HTTP as client connection method for both
1.20 Make your selection, click Next
1.21 Click Next on the Settings Summary page
1.22 A prerequisite check will run. Any errors listed on this page, will have to be fixed before you can continue the installation. As you can see, I received an error regarding WSUS missing on the site server. I will install WSUS when I set up the Software Update Point. Warnings do not prevent you from continuing the installation.
If you want to run a prerequisite check outside of the installation wizard, you can use the Prereqchk.exe tool found in the installation media at \SMSSETUP\BIN\X64. Prereqchk.exe is a stand-alone application, that verifies server readiness for a site server or specific site system roles. You can run Prerequisite Checker at a command prompt and specify specific command-line options to perform only checks that are associated with the site server or site systems that you specified in the command line.
Click Begin Install
1.23 You can click on View Log to view the different tasks the installation is performing. You can find this log file on the root of %systemdrive% , it’s called ConfigMgrSetup.log
You should use CMTrace.exe found in the installation media at \SMSSETUP\TOOLS to view all SCCM related log files. CMTrace formats the logs nicely and also allows monitoring logs in real time as they are written.
1.24 After the installation has completed, you can check which version of SCCM 2012 has been installed by launching the Configuration Manager Console, clicking on the arrow in the top left corner, and selecting About Configuration Manager
2. Upgrade to SCCM 2012 R2 SP1
2.1 Launch splash.hta found in the installation media extracted from SC2012_R2_SP1_Configmgr.exe
2.2 Click Upgrade
2.3 Click Next
2.4 Accept the License Agreement, click Next
2.5 Click Install
2.6 Click Finish
2.7 If you now check which version of SSCM 2012 you are running, you will see that the About Configuration Manager dialog box shows SCCM 2012 R2 SP1
2.8 Validate the status of the site and components selected during the installation of the stand-alone primary site, by starting the Configuration Manager Console. Navigate to the Monitoring Workspace → System Status → Site Status,
and Monitoring Workspace → System Status → Component Status