Microsoft System Center Configuration Manager (SCCM), now known as Microsoft Endpoint Configuration Manager (MECM), is a powerful platform for centralized management of devices across an enterprise. It allows IT administrators to deploy operating systems, applications, updates, and enforce security compliance efficiently.
In this comprehensive guide, we’ll walk you through:
- SCCM prerequisites
- Installation steps
- Post-installation configurations
- Best practices
1. Prerequisites for Installing SCCM
Setting up SCCM requires thorough planning and an environment that meets all technical prerequisites.
Hardware Requirements
Component | Minimum Requirement |
---|---|
Processor | 2.0 GHz dual-core (or better) |
RAM | 8 GB (small environments) / 16+ GB (medium-large) |
Disk Space | 250 GB+ (varies with deployment size) |
Network | 1 Gbps NIC |
Software Requirements
- Operating System:
- Windows Server 2019 or 2022 (latest updates applied)
- SQL Server:
- SQL Server 2019 or 2022 Standard/Enterprise (with latest CU)
- Must be on the same domain and supported build for SCCM
- .NET Framework:
- .NET Framework 4.8
- Windows ADK (Assessment and Deployment Kit):
- Install Windows ADK + Windows PE Add-on for your version of Windows 10/11
- Windows Server Roles:
- Active Directory Domain Services (ADDS)
- DNS
- DHCP (optional for PXE boot)
- WSUS (Windows Server Update Services)
SCCM Account Requirements
- SCCM Admin Account – Local admin on SCCM server
- SQL Service Account – Domain user with local admin on SQL Server
- SCCM Network Access Account – For client deployment and content access
2. Preparing Your Environment
Step 1: Extend Active Directory Schema
To support client discovery and publish site data:
\\<SCCM Server>\SMSSETUP\BIN\X64\extadsch.exe
Check extadsch.log
in the root of C:\ for confirmation.
Step 2: Install and Configure SQL Server
- Use a dedicated drive for SQL DB and logs
- Enable SQL Server authentication and mixed mode
- Configure SQL Server memory limits for performance
- Ensure SQL Server collation is
SQL_Latin1_General_CP1_CI_AS
Step 3: Install Windows ADK + WinPE Add-on
Download and install:
- Deployment Tools
- Windows PE Add-on
Step 4: Install Windows Server Features
Open PowerShell as Administrator:
Install-WindowsFeature Web-Server, Web-Windows-Auth, Web-ISAPI-Ext, Web-Metabase, BITS, RDC, WSUS, NET-Framework-Features -IncludeManagementTools
3. Installing SCCM (MECM)
Step 1: Mount the SCCM ISO
Download the latest SCCM ISO from Microsoft Volume Licensing Service Center (VLSC) or Eval Center.
Step 2: Run the Setup
Navigate to splash.hta
and launch the installer.
Step 3: Choose Installation Type
Select “Install a Configuration Manager Primary Site”
Step 4: Provide Product Key or Use Eval
Step 5: Prerequisite Downloads
Allow the installer to download the required files.
Step 6: Site Configuration
- Site Code: e.g., “C01”
- Site Name: “CupsDeeps ConfigMgr Site”
- Installation path: Recommended separate drive (e.g., D:)
Step 7: Database Configuration
Point to the SQL Server and instance installed earlier.
Step 8: SMS Provider Settings
Select the local SCCM server for hosting the SMS Provider role.
Step 9: Configure Communication Settings
Choose HTTPS or HTTP depending on whether you plan to deploy PKI certificates.
Step 10: Setup Summary & Installation
Review and start installation. Monitor progress logs at:
C:\ConfigMgrSetup.log
C:\ConfigMgrAdminUISetup.log
4. Post-Installation Configuration
1. Configure Discovery Methods
Go to Administration > Hierarchy Configuration > Discovery Methods:
- Enable Active Directory System Discovery
- Enable Group Discovery and User Discovery
2. Configure Boundaries and Boundary Groups
Set IP ranges or AD sites to define boundaries and associate them with distribution points.
3. Install and Configure Site System Roles
Under Administration > Servers and Site System Roles, add:
- Management Point (MP)
- Distribution Point (DP)
- Software Update Point (SUP)
4. Configure Software Update Point
- Integrate WSUS with SCCM
- Synchronize updates
- Select classifications (e.g., Critical, Security)
- Select products (e.g., Windows 11, Office 365)
5. Create Device Collections
Use WQL queries to create dynamic collections for targeting deployments.
Example:
select * from SMS_R_System where SMS_R_System.OperatingSystemNameandVersion like "%Workstation%"
5. Client Deployment and Monitoring
Client Installation Methods
- Group Policy
- Client Push
- Manual installation (
ccmsetup.exe
) - Software Update Point
Monitoring Client Health
Go to Monitoring > Client Status to check:
- Client installation success
- Communication status
- Endpoint protection
6. Best Practices for SCCM Configuration
- Separate SCCM database and log files to different drives
- Regularly back up the SCCM site
- Enable maintenance tasks: DB reindexing, delete aged data
- Use role-based access control (RBAC) for secure administration
- Monitor site status and logs regularly
Conclusion
Setting up SCCM can seem complex, but following the structured steps outlined above ensures a stable and scalable deployment. Once configured, SCCM empowers organizations to automate OS deployments, patch management, and software distribution—all from a central console.
Need help optimizing your SCCM setup or automating deployments? Reach out to our expert team at CupsDeeps—where IT meets deep innovation.