How to Install Microsoft Configuration Manager (SCCM) on Windows Server

Microsoft System Center Configuration Manager is now called Microsoft Configuration Manager, though many administrators still use the name SCCM. To install it on Windows Server, prepare a supported server and SQL database, extract the current-branch media, and run Configuration Manager Setup to create a primary site. This walkthrough covers a single-site evaluation or deployment.

The figures are conceptual screen illustrations for orientation, not captured screenshots. Labels can vary by release.

Version and prerequisites

As of October 24, 2026, Microsoft’s Evaluation Center lists Current Branch version 2509 evaluation media. The evaluation runs for 180 days and needs no product key. Version 2609 is in the early update ring; opt in only if you intend to test it and follow Microsoft’s checklist.

• Use a supported Windows Server 2022 or 2025 edition; check Microsoft’s site server support table.
• Install .NET Framework 4.8, enable .NET Framework 3.5 and Remote Differential Compression, then restart.
• Prepare a supported 64-bit SQL Server. SQL Server 2022 supports the 2509 baseline; SQL Server 2025 support starts with Configuration Manager 2603. The setup account needs administrator rights on the site and SQL servers and SQL sysadmin rights. Keep the site server computer account as SQL sysadmin after setup.
• Install a supported Windows ADK before site setup. Add its separate WinPE add-on only for OS deployment. Microsoft lists ADK 10.1.26100.x for versions 2509, 2603, and 2609. See the site prerequisites, SQL support table, and ADK support table.

Install Configuration Manager

1. Download the evaluation media. Open Microsoft’s Evaluation Center page, register if asked, and download Configuration Manager Current Branch. Confirm the version on the page; the evaluation lasts 180 days.

   

2. Extract the package. Microsoft says to use 7-Zip or WinRAR to extract the downloaded executable. Choose a dedicated folder with enough free space, such as C:\ConfigMgrMedia. The current install path uses Setup.exe, not the old splash.hta launcher.

   

3. Prepare Windows Server. Add .NET Framework 3.5 and Remote Differential Compression in Server Manager, install .NET Framework 4.8, and restart. Use a supported Windows Server release and an account with the permissions above.

   

4. Install SQL Server. Install a supported 64-bit instance and confirm the SQL service is running. SQL Server 2022 is a supported match for the 2509 evaluation baseline. Grant the setup account sysadmin access.

   

5. Install the Windows ADK. Choose an ADK version supported by your Configuration Manager release. Install the separate WinPE add-on if you plan to deploy operating systems. The current support matrix lists ADK 10.1.26100.x for versions 2509, 2603, and 2609.

   

6. Start Setup. From the extracted media, run SMSSETUP\BIN\X64\Setup.exe as an administrator. This launches the Configuration Manager Setup Wizard.

   

7. Choose the site type. Select Install a Configuration Manager primary site. For one site, install it as a stand-alone primary site. A central administration site is unnecessary for a single-site hierarchy.

   

8. Select evaluation or licensed edition. Choose Evaluation edition for a trial, or Licensed edition if you have the required rights. Read and accept the Configuration Manager and prerequisite software license terms.

   

9. Download prerequisite files. Select Download required files and set a local destination, or use a folder populated by Microsoft’s Setup Downloader. For an isolated network, download the files on a connected computer and transfer them securely.

   

10. Set the site identity. Select server and client languages. Enter a unique three-character alphanumeric site code and a descriptive name. Choose the installation folder carefully: you can’t change it after setup, and the path can’t contain Unicode characters or end in spaces.

    

11. Configure the database and client communication. Enter the SQL Server FQDN and instance. By default, the database name is CM_ plus your site code, and the Service Broker port is 4022. The SMS Provider defaults to the site server. Use HTTPS-only with the required PKI certificates, or per-role configuration, which uses Enhanced HTTP; plain HTTP is deprecated.

    

12. Choose servicing mode and run checks. Set the service connection point to Online if it can reach Microsoft; choose Offline for an isolated site and use the Service Connection Tool. Review the setup summary, run the prerequisite check, fix all Failed items, and rerun it. Use ConfigMgrPrereq.log for details, then select Begin Install. Initial configuration may continue after you close the wizard.

    

After installation

Open the Configuration Manager console and check site status before deploying clients. Use Administration > Updates and Servicing to review updates offered for the site. Version 2609 is an early update-ring release and requires version 2503 or later; follow Microsoft’s 2609 checklist before opting in. See Microsoft’s primary site setup guide for the full wizard reference.