Published on

SCCM - Configuration Manager

Authors
  • Name
    Jackson Chen

Prerequisities

  1. Download Configuration Manager 2002 baseline media https://www.prajwaldesai.com/download-sccm-baseline-version-install-media/

For fresh installation or new SCCM server installation, install from Configuration Manager 2002 baseline media.

  1. Download Configuration Manager 2103 baseline media For fresh installation or new SCCM server installation, install from Configuration Manager 2103 baseline media.

  2. Before installation, check the followings on the Configuration Manager

1. Verify that a support Microsoft SQL Server installations available for Configuration Manager
2. Identify the FQDN of the computer that is running Microsoft SQL Server. 
    Note: SCCM license includes local installation of SQL standard edition.
3. Confirm that computers for Configuration Manager site systms meet the minimum system requirements.
4. Read release note and verify links to supported versions and system requirements
  1. Download Configuration Manager pre-requisite files https://www.prajwaldesai.com/download-sccm-prerequisite-files-offline/
1. On system has internet connection, run Configuration Manager installation, and select
    Download required prerequisite files
2. Specify or browse to the download folder, and click Download
3. Copy the pre-requisite files to the Configuration Manager server

Note: Configuration Manager 2002 and 2103 supports Windows Server 2019.

SQL 2017 or SQL 2019 Standard Edition Installation

Install SQL 2017 or SQL 2019 Stanard Edition

Troubleshooting

SQL Server TCP Port Failed When Installing SCCM Baseline Media

when it came time to install the SCCM portion, I kept on getting an SQL Server TCP Port Failed error with a description of Configuration Manager primary site and central administration site require SQL Server Tcp is enabled and set to Static port.

Follow these steps and you should be able to successfully get past this error message.
1. On your SQL server hosting your SCCM database, open SQL Server Configuration Manager.
2. Once open, navigate to and expand SQL Server Network Configuration
3. Select Protocols for <SCCM-SQl-Instance>, on the right pane, select TCP/IP 
4. Right click TCP/IP on the right pane and go to properties
5. Go to the IP Addresses tab.
6. Set all TCP Dynamic Ports to blank.
7. Set all TCP ports to 1433.
8. Press Ok to confirm the dialog box about restarting services.
9. Within SQL Server Configuration Manager, Navigate to SQL Server Services.
10.Restart all SQL services for the SCCM instance.

Download ADK 2004

https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install

  1. Download the Windows ADK for Windows 10, version 2004 Run adksetup.exe and select Download the windows Assessement and Development Kidt - Windows 10 for installation on a separate computer, then specify the download path.

  2. Download the Windows PE add-on for the ADK, version 2004 Run adkwinpesetup.exe, and select Download the Windows Assessment and Deployment kit Windows Preinstallation Environment Add-ons - Windows 10 for installation on a separate computer, then specify the download path

Install ADK 2004

  1. Install Windows ADK for Windows 10, version 2004 Run adksetup.exe as administrators, and select Install Path, or browse to the install path, and install ADK 2004 for windows 10.
# Select the following components
a. Deployment Tools
b. Image And Configuration Desinger (ICD)
c. Configuration Designer
d. User State Migration Tool (USMT)
  1. Install ADK 2004 WinPE Run adkwinpesetup.exe, and select Download the Windows Assessment and Deployment kit Windows Preinstallation Environment Add-ons - Windows 10 to this computer, and specify the installation path.

Select Windows Preinstallation Environment (Windows PE) feature.

Install Windows Update Service (WSUS)

WSUS will be installed on SCCM server with local SQL installation, on role services selction, select

a. WSUS Services
b. SQL Server connectivity
Note: Do not select WID Connectivity

On DB Intance installation section, under Specify an existing server (Machine nam\instance name) to install the WSUS database

<SQL-server-name>\<Instance-name>,<TCP-port>
Click Check connection, to ensure successful SQL connection

Install SQL 2019 Reporting Services

Download SQL 2019 Reporting Services

https://www.microsoft.com/en-us/download/details.aspx?id=100122

  1. Obtain SQL 2019 product key before install SQL 2019 Reporting Services
  2. On Setup Completed, click Close. Will configure SQL Reporting Services after installation of Configuration Manager

Configure Group Policy - Firewall Settings

https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/hierarchy/ports

Configure group policy to all the required TCP ports for configuration manager, TCP 1443 and 4022, and any other required ports

Create the System Management Container

Create system management container only once in each domain that has a primary or secondary site. This will be used to publish data to Active Directory.

Extending Active Directory Schema

1. Locate the extadsch which can be found in SMSSETUP\BIN\X64 of the configuration manager setup media.
2. Hold the shift key on your keyboard and right click extadsch and click on Copy as Path.
3. Launch the command prompt. Right click and click paste and hit enter.
4. You should see the line Successfully extended the Active Directory Schema.

Install Web Server IIS Prerequisites

1. Enable/Install the following features :-

    .Net Framework 3.5 Features [Install all sub features]
    .Net Framework 4.5 Features [Install all sub features]
    BITS
    Remote Differential Compression
2. Enable/Install the following Roles Service
    Common HTTP Features – Default Document, Static Content.
    Application Development – .NET Extensibility 3.5 and 4.5. Select ASP.NET 3.5, ISAPI extensions, ASP.NET 4.5.
    Security – Windows Authentication.
    IIS 6 Management Compatibility – IIS Management Console, IIS 6 Metabase Compatibility, WMI Compatibility and IIS Management Scripts and Tools.

Configuration Manager 2002 Installation

https://www.prajwaldesai.com/sccm-2002-install-guide-using-baseline-media/

The following high level installation steps

1. Mount Configuration 2002 baseline media, and start the installation
Note: Disable or remove antivirus when installing Configuration Manager, then enable or reinstall antivrus.
2. To install a configuration manager primary site, select
    a. Install a Configuration Manager primary site
    b. Untick/deselect "Use typical installation options for a stand-alone primary site
       Note: For test lab, select to use typical installation
3. Enter the Configuration Manager license key, and set software assurance expiration date
4. Accept the license terms
5. On prerequisite downloads window, select
    Use previously downloaded files, and browse to the required folder
6. Keep default English language
7. On Site and Installation Settings
    a. Enter 3 character site code
    b. Enter site name
    c. Specify the installation folder
    d. Select Install the configuration Managemetn console, otherwise
        install the console after installation
        install the configuration management console to managemnt servers
8. On Primary Site Installation window, select Install teh primary site as a stand-alone site
9. On Database information window
    a. Specify the path to the SQL Server data file
    b. path to the SQL server log file
10. On SMS Provider Settings window, enter the SMS provider (FQDN)
    Note: The FQDN name of the SCCM server
11. Client Computer Communication Settings
    a. All site system roles accept only HTTPS communications from clients, or
    b. Configure the communication method on each site system role
       Clients will use HTTPS when they have a valid PKI certificate and HTTPS-enabled site roles are available
12. On Site Sytem Roles window, select
    a. Install a management point, and choose HTTP or HTTPS for client connection
    b. Install a distribution point, and choose HTTP or HTTPS for client connection
13. On Service Connection Point setup
    a. Select Yes, if the configuration manager server has internet connectivity
    b. Select Skip this for now, if the system does not have internet connectivity
    Note: 
        i. We could add Service Connection Point site role after the installation
        ii. If to upgrade from Configuration Manager 2002 to 2103, 
            need to add Service Connection Point role, and select/configure "Offline on-demand connection" 
14. On Settings Summary, review the settings

The installation will take sometime, depending on the system resources, about 15 to 30 minutes

Upgrade from Configuration Manager 2002 to 2103

  1. Backup Configuration Manager
# Configure SCCM bakcup
a. On Configuration Manager console, select Administration, then navigate to Overview -> Site Configuration -> Sites
b. Select Site Maintenance from top menu bar
c. On Site Maintenance window, select Backup Site Server, and ensure it enabled
    1. Select "Backup Site Server", click Edit
    2. Click Set Paths
    3. Select "Network path (UNC name) for site data and database
    4. In Backup destination, enter \\<UNC-path|SCCM-Server>\Backup
d. Access Services, and start SMS_SITE_BACKUP service 
e. Verify SCCM backup has been successfully done
  1. Disalbe all SMS services
a. On Configuration Manager console, select Administration, then navigate to Overview -> Site Configuration -> Sites
b. Select Site Maintenance from top menu bar
c. On Site Maintenance window, select individual service, and click Edit
d. Select No
e. Verify all services have been set to No (Except - Update Application Catalog Tables)
  1. Add Service Connection Point site role
a. From Configuration Manager console, select Administration
b. Navigate to Site Configuration -> Servers and Site System Roles
c. On the right pane, select the <site-server>, right click and select Add site System Roles
d. On Select a server to use as a site system, under Site system Installation Account,
   select "Use the site server's computer account to install this site system"
e. Under system role selection, select Service Connection Point
f. On Service Connection Method, select
    i. Online persistent connection, if system has internet connection
    ii. Offline on-demand connection, if system does not have internet connection
  1. Use the Service Connection Tool for Configuration Manager to download the updatepacks https://docs.microsoft.com/en-us/mem/configmgr/core/servers/manage/use-the-service-connection-tool

Use the service connection tool when your service connection point is in offline mode. You can also use it when your Configuration Manager site system servers aren't connected to the internet. The tool can help you keep your site up to date with the latest updates to Configuration Manager.

# Prerequisites
1. The site has a service connection point, and you configure it for an Offline, on-demand connection.
2. Run the tool from a command prompt as an administrator. There's no user interface.
3. You run the tool from the service connection point and a computer that can connect to the internet. 
    Each of these computers needs to have a x64-bit OS, and have the following components:
    a. Both the Visual C++ Redistributable x86 and x64 files. 
    By default, Configuration Manager installs the x64 version on the computer that hosts the service connection point. 
    To download this component, see Visual C++ Redistributable Packages for Visual Studio 2013.

    b. Starting in version 2107, this tool requires .NET version 4.6.2, and version 4.8 is recommended. 
    In version 2103 and earlier, this tool requires .NET 4.5.2 or later. For more information, Site and site system prerequisites.
4. The account you use to run the tool needs the following permissions:
    a. Local administrator on the computer that hosts the service connection point
    b. Read permissions to the site database
5. You need a method to transfer the files between the computer with internet access and the service connection point. 
    For example, a USB drive with sufficient free space to store the files and updates.

Process to create the preparation cab file

Carry out the following steps on the Configuration Manager

1. On the Configuration Manager server, access Configuration Manager 2002 baseline media,
2. copy the folder ServiceConnectionTool to C:\TEMP, 
    where
    \SMSSETUP\TOOLS\ServiceConnectionTool\
3. Run the command from a command prompt as an administrator
    cd C:\TEMP\ServiceConnectionTool\
    #> ServiceConnectionTool.exe -prepare -usagedatadest C:\TEMP\USB\UsageData.cab

Download the updatepacks

1. Copy the UsageData.cab to USB
2. Copy ServiceConnectionTool folder with all required files to USB
3. On the internet connection system, run the tool from a command prompt as an administrator
    ServiceConnectionTool.exe -connect -usagedatasrc D:\USB -updatepackdest D:\USB\UpdatePacks

 Note
    When you run this command line, you might see the following error:
    Unhandled Exception: System.UnauthorizedAccessException: Access to the path 'C:\Users\jqpublic\AppData\Local\Temp\extractmanifestcab\95F8A562.sql' is denied.
    You can safely ignore this error. Close the error window to continue.

Import the updatepacks to Configuration Manager

After download the updatepacks, import the updatepacks to the Configuration Manager

1. Run the tool from a command prompt as an administrator
    cd C:\TEMP\ServiceConnectionTool\
    #> ServiceConnectionTool.exe -import -updatepacksrc D:\USB\UpdatePacks

2. Verify log files for updatepacks importing error
    a. ServiceConnectionTool.log
    Each time you run the service connection tool, it writes to this log file. 
    The path of the log file is always the same location as the tool. 
    This log file provides simple details about the tool usage based on the parameters you use.
    Each time you run the tool, the tool replaces any existing log file.

    b. ConfigMgrSetup.log
    During the Connect phase, the tool writes to this log file at the root of the system drive. 
    This log file provides more detailed information. 
    For example, what files the tool downloads, and if the hash checks are successful.

Download the Configuration Manager update

1. After successfully importing the updatepacks, navigate to Updates and Servicing from Configuration Management console.
2. Select the available latest Configuration Manager upgrade verion on the right pane
3. Click Download from the top menu bar
4. Refresh and wait till the update becomes Ready to Install

Run prerequisite check

# SCCM & SQL server installed in the same server
1. When the update is ready to install, select the Configuration Manager update version
2. Click Run prerequisite from the top menu bar
3. Click show status to verify the progress
4. Verify logs
    a. dmpdownloader.log
    b. hman.log
5. Fix any issue and then install the update


# SCCM database host on SQL AlwaysOn Availability Group
1. Access SQL Server Management Studio (SSMS)
2. Navigate to the AlwaysOn Availability Group, edit the properties
3. Under Availability Replcas section
    a. In Failover Mode, set both Primary and Secondary server Failover Mode to MANUAL
        Note: After SCCM upgrade, change them back to Automatic
    b. In Readable Secondary, select "Yes" for the secondary
        Note: Set secondary Readable to No after upgrade if required.

# Ready to Install
1. Run prerequisite check until all the errors and warnings have been addressed
2. Verify the latest Configuration Manager state is "Ready to Install"

Configuration Manager 2103 Installation

1. Access Configuration Manager console
2. Select Administration, then expand Overivew -> Updates and Servicing
3. Selecct the required Configuration Manager version that is in Ready to Install state
4. Click Install Update Pack
5. Monitor the install status
6. Verify hman.log

Upgrade/Install the Configuration Manager console on management server

# Configuration Manager console alrady installed
1. Open Configuration Manager console
2. It will prompt to upgrade
3. Continue the upgrade

# Install Configuration Manager on the management server
1. Copy "ConsoleSetup" folder to the management server
2. Run cmd as Administrator, then run ConsoleSetup.exe, or
    msiexec.exe /i  AdminConole.ini
Discuss on Twitter • View on GitHub