Congfig Mgr, Microsoft Endpoint Configuration Manager

Step-by-Step SCCM 2002 Installation and SCCM 2006 Upgrade Guide

Posted by Jay-R Barrios ⋅ September 23, 2020 ⋅ Leave a comment

This post will show the step-by-step process on how to install Microsoft Endpoint Configuration Manager (current branch – version 2002) as a Standalone Primary Server in a Windows Server 2019 lab environment from scratch and later on we will upgrade it to current branch – version 2006.

Step 1. Primary Site Server Installation Prerequisites

LAB Environment

For the LAB environment I have dedicated an Intel NUC for my ConfigMgr Sever which is joined to my domain that is running on a Windows Server 2019 Hyper-V environment with an Internet connection.

Installation Media

What you need:

Download the iso files from your Visual Studio Subscription or Microsoft Evaluation Center

AD Accounts

For this installation I have created accounts

SCCMAdmin – account to be used for administering ConfigMgr
SQLSvrAgent – account to be used as the SQL Server Account

You can go ahead and create the rest of the required SCCM Accounts

SCCM Network Access Account
SCCM Client Push Install Account
SCCM Domain Join Account (for OSD)
SCCM Admins Group
SCCM SQL Reporting Account (If you’re installing Reporting Services)

Unlike my previous post, Step-by-step SCCM 1902 Installation and SCCM 1906 Upgrade Guide, I already have an existing domain with ConfigMgr running so I’ll go straight and Delegate of Permission to my new ConfigMgr Server (LAB-CM01) and skip the Extend Active Directory Schema for SCCM.

Launch **Active Directory Users and Computers** and on the **View** tab, click on **Advance Features**

Browse for **System > System Management >** Right-click and select Delegate Control and In the Delegation of Control Wizard click Next.

Add the Primary Site Server, **CM01** once the server is added, click Next.

In the Task to Delegate, select **Create a custom task to delegate** click Next.

In the Active Directory Object Type select **This folder, existing objects in this folders, and creation of new objects in this folder** and click Next.

Tick on the 3 permissions **General, Property-specific** and **Creation/deletion of specific child objects**. Under Permissions tick on **Full Control** and click Next.

Configure Windows Firewall

To open TCP port 1433 and 4022 for SQL replication you need to launch the Windows Defender Firewall and Advance Security to do that, press Windows logo key‌, type wf.msc and click on it

In the **Windows Defender Firewall and Advance Security** right-click Inbound Rules, and then click New Rule.

In the Protocol and Ports dialog box, select **TCP**. Select Specific local ports, and then type port numbers **1433** for SQL Server default instance and **4022** for Inter-site communications use the SQL Server Service Broker. Click Next.

In the Action dialog box, select **Allow the connection**, and then click Next.

In the Profile dialog box, select **Domain** and then click Next.

In the Name dialog box, type a profile name,like **SQL ports for ConfigMgr** and then click Finish.

Step 2. Install Web Server (IIS) Role and other Features

In the Primary Site Server we will need to install the follow Roles and Features from the Server Manager:

In the Server Roles, select **Web Server (IIS)**. When prompted to “**Add features that are required for Web Server (IIS)?**” click the Add Features button and click Next.

In Features, select **.NET Framework 3.5 Feature** and **Background Intelligent Transfer Service (BITS)**

Note: BITS – is the technology that allows us to throttle all the network communication that occurs between servers to client where it utilizes idle bandwidth to transfer data.

Still in the Features page, scroll down and select **Remote Differential Compression** (RDC) and click Next.

In the Web Server Role (IIS) > Role Services select the following:

Web Server (IIS)

Web Server
- Common HTTP Features: Default Document, Directory Browsing, HTTP Errors Static Content, HTTP Redirection
- Health and Diagnostics: HTTP logging, Logging tools, Request Monitor, Tracing
- Performance: Static Content Compression
- Security: Windows Authentication
- Application Development: .NET Extensibility 3.5, .NET Extensibility 4.7, ASP.NET 3.5, ASP.NET 4.7, ISAPI Extensions, ISAPI Filters
Management Tools
- IIS Management Console
- IIS 6 Management Compatibility: IIS 6 Metabase Compatibility, IIS 6 WMI Compatibility
- IIS Management Scripts and Tools

Click **Next** and in the **Confirmation** screen click the **Install** button to complete the installation of the Web Server Roles and Features.

NO_SMS_ON_DRIVE.SMS

This is the most common step that has been overlooked, so make sure to create the NO_SMS_ON_DRIVE.SMS to drives that you don’t want SCCM Contents to be created especially on your remote DPs.

Now you can just copy it this file and paste it other drives you need it to be placed

Step 3. Installing and Configuring SQL Server 2019

SQL Server 2019 Installation

In this section we will install and configure the Primary Site’s database server and it’s components.

Go a head an mount the SQL Server 2019 installer and run the **setup.exe**.

In the **SQL Server Installation Center > Installation**, click on the **New Server stand-alone installation or add features to an existing installation**.

In the **Product Key** page, choose for the Evaluation or enter a product key then click Next to continue.

Agree to the **License Terms** then click Next.

My server has internet connection so I’ll check for **Microsoft Update** updates, then click Next.

In the **Install Rules**, make sure that everything pass else rectify by clicking the Status links, as for **Windows Firewall** we’ll ignore the Warning as the required ports for SQL replication was previously configured. We will now and proceed to the **Feature Selection** page.

In the **Feature Selection**, tick the **Database Engine Services** then click Next.

In the **Instance Configuration**, leave the default instance ID, **MSSQLSERVER** click Next to continue.

In the **Server Configuration**, **Service Accounts** tab, make sure to configure **ALL** **SQL services** to run under a domain user account (e.g., LAB\SQLSvrAgent) instead of the local system or network services.

Note: Best practice in Production, the SQL Server Agent and SQL Server Database Engine should each have a domain accounts. For their account’s passwords should be configured not to expire and cannot be changed (so make sure these service accounts are restricted not have an interactive logon rights as well).

in the same window click the Collation tab. Make sure its SQL_Lantin1_General_CP1_CI_AS then click on Next

In the **Database Engine Configuration**, click **Add Current User** or add another user/SCCM Admin groups and click Next.

In the Data Directories make sure to set the databases to the allocated drives and then click on Next.

SQL Server 2019 is ready to install, click the **Install button**.

Note: Notice the Configure file path, you can go to the directory and explore the ConfigurationFile.ini if you’re interested to install SQL Server using the configuration file.

Confirm that the installation is successful, click Close to complete the process.

MS SQL Server Management Studio Installation

Beginning SQL Server 2016 the release of SQL Server Management Studio (SSMS) was a stand-alone install outside of the SQL Server release. That is why we need to do a separate install of the SSMS.

It’s a straight forward install, choose a location and click Install

After the installation is complete you are required to restart the Primary Server.

Configure SQL Server Memory Allocation

Launch the SQL Server Management Studio, Right-click on the CM01 (SQL Server) and select Properties.

In the Server memory options I have set the Minimum and Maximum memory size to 12288 if it’s not set to at least 8192 you’ll have a little warning during the installation of Config Manager. Setting the Memory b/w 2048 to 4096 will still work.

By default the Minimum server memory (in MB) is set to 0 and the Maximum server memory (in MB) is set to 2147483647. I have Set to 0 and 1024. Click OK to close the Server Properties window and complete the SQL configuration.

Step 4. Windows ADK Installation

In any Configuration Manager deployment I strongly recommend to install the lasted Windows 10 ADK in preparation for Windows 10 Operating Systems Deployment with Configuration Manager, the Windows ADK is a required external dependency.

Installing Windows ADK for Windows 10

Download and run the adksetup.exe

The installation is very straight forward, in the **Specify Location** leave the default and click Next.

In the Select the features you want to install, as for this installation we will only select the following:

Deployment Tools
Imaging and Configuration Designer – this can be used later on for provisioning packages.
Configuration Designer
User State Migration Tool

After selecting the features to to install, click Install button.

You’ll get the Welcome screen to Windows 10 ADK once the installation is completed. Click Close to finish the installation.

Installing Windows PE add-on

Starting Windows 10 1809, Windows Preinstallation Environment (PE) has been released separately from the Windows ADK.

To add Windows PE to the ADK installation, we need to download the Windows PE add-on and run the included installer after installing the ADK.

Similarly to Windows ADK the WinPE Add-on is a straight forward install. Download and run the adkwinpesetup.exe

In the **Specify Location**, click Next.

There’s nothing else to select in the **Select the features you want to install** other than Windows PE. Click the Install button to complete the installation.

Step 5. Microsoft Endpoint Configuration Manager (current branch – version 2002) Installation

Finally after all the preparation we are now ready to the install ConfigMgr 2002. Go and mount the ISO and run the Setup.exe.

Download Required Prerequisite Files

Optional: We can download the required prerequisite files prior to the installation of Configuration Manager. This is usually done if your server is in an isolated network.

In the ConfigMgr installation screen click **Install**

Select **Install a Configuration Manager primary** and tick the **Use typical installation options for stand-alone primary site** box.
A pop-up box will appear, read through and click on the Yes button.

In the **Product Key**. select an option and click on Next.

In the **Product License Terms**, tick all the 3 boxes and click Next.

For the **Prerequisite Downloads** we’ll be using the **Use previously downloaded file** option and point it the folder where we downloaded the files.

In the **Site and Installation Settings** , enter a 3 character site code and site name that normally pertains to the site location and click Next.

In the **Diagnostic and Usage Data** click Next.

In the **Service Connection Point Setup** in this example, we will select the **Yes, let’s go connected (recommended)** as my server has internet connectivity, if you’re server is in an isolated network select the **Skip this for now** option.

Click the Next button for the final Prerequisite Check.

In the **Prerequisite Check** page, make sure there’s no problem found and if there is fix it first before clicking the **Begin Install** button.

After clicking the **Begin Install** you’ll be brought to the Install page to see the over all progress. You may want to grab a coffee or a burger and fries at this point (you deserve it) and come back after an hour.

Congratulations you have successfully installed Microsoft Endpoint Configuration Manager (current branch – version 2002)

Don’t configure the Configuration Manager server yet as we will update it first to version 2006 in the next step.

Step 6. Configuration Manager 1906 Upgrade Installation

Before we begin to upgrade our ConfigMgr 2002 to 2006 you may want go through on the what’s new in version 2006 of current branch https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/changes/whats-new-in-version-2006

Support for Configuration Manager current branch versions

Also its good to get to know about the Servicing Support/end of support dates for Configuration Manager versions from this link: https://docs.microsoft.com/en-ca/sccm/core/servers/manage/current-branch-versions-supported

SCCM 1906 Prerequisite Check

Launch theConfigMgr console and go to Administration > Updates and Servicing and verify that the Configuration Manager 2006 is in Ready to install State. (This will appear if your ConfigMgr is connected to the internet for sometime)

Right-Click **Configuration Manager 2006** and click **download**

Click OK and check back after a few minutes

When the Status is Ready to install go ahead and **Run prerequisite check**

You will see that the Status is now **Checking prerequisites**.

You can check the progress by opening the C:\ConfigMgrPrereq.log with CMTrace.

Once done, the status should tell you that **Prerequisite check passed**

Select and right-click the **Configuration Manager 2006** and **Install Update Pack**

ConfigMgr 2006 Update

The Configuration Manager Updates Wizard will launch

In the **Features**, select the feature you need to install, in my case the check boxes are pre-selected already I just needed to click Next.

Note: if you don’t want to select any of the features you can always enable it later, from the ConfigMgr console Administration workspace > Updates and Servicing > Features.

In the **Client Update Options**, I will select **Upgrade without validating** as I don’t have any active client yet.

In the **License Terms** tick and accept the license terms box and click Next and in the **Summary** click on Next.

Click Close and go back to the SCCM Console to monitor the progress of the update.

In the **Monitoring** workspace > **Updates and Servicing Status** you can see that the status is **Installing,** go and right-click on the **Configuration Manager 1906** and select **Show Status** to further view the detailed status.

It will take something for the installation to complete. Once completed, click the OK button to close the Status window.

Back in the ConfigMgr console the Status should reflect as well.

No long after you will get a notification that “**A new version of the console is available…. ”** go and click on the **Install the new console version** link.

The SCCM console will close and go through the installation process.

You can view the progress from the log files C:\ConfigMgrAdminUISetup.log and C:\ConfigMgrAdminUISetupVerbose.log and after the installation is completed the new SCCM Console will automatically launch.

In the console, go and verify that the ConfigMgr version is now in **2006**.

Now you are ready to configure ConfigMgr 2006 and perform Software Deployment Services and Operating System Deployment with the lab that we’ve just built. Thanks for taking time to read this post.

LAB.DEMO

Search

Step-by-Step SCCM 2002 Installation and SCCM 2006 Upgrade Guide