Microsoft Configuration Manager (SCCM) Tutorial

In Microsoft's Q3 fiscal 2026 filing with the SEC, it reported revenue of $82.9 billion, with Cloud revenue alone exceeding $50 billion. Intune manages 200 million devices on a daily basis and was placed as a Leader in IDC MarketScape for Unified Endpoint Management 2025-26. 

In late 2025, Configuration Manager began annual updates, and in 2026, the most pertinent Endpoint Management skill is being knowledgeable about its functionality in tandem with Intune.

Table of Contents

• What is SCCM and How Does it Work?
• What is Configuration Manager?
• Features
• Architecture
• Cloud Integrations
• Site System Roles
• ConfigMgr vs Intune and Migration Path
• Microsoft MD-102 Certification

What is SCCM and How Does it Work?

SCCM is officially known as Microsoft Configuration Manager, which is an on-premises solution for managing your Windows devices in bulk. SCCM's purpose is to manage operating system deployment, software deployment, patching, compliance, inventory, and reporting for thousands of endpoint devices. SCCM is one product within the Microsoft Intune family of endpoint management products.

How It Works?

The core deployment flow has stayed consistent over the years. You create a package or application in the ConfigMgr console. That content gets distributed to Distribution Points placed across your network. The ConfigMgr client running on each managed device checks in with its Management Point, receives applicable policies, and pulls content from the nearest Distribution Point.

Package → Distribution Point → Client Agent → Policy → Deployment. Whether it is a Windows update, an application install, or a compliance baseline, this same pattern applies.

Modern Content Delivery

The way content reaches devices has evolved in 2026. Traditional "pull from the DP" still works, but modern deployments layer these on top.

• Delivery Optimization enables peer-to-peer sharing between Windows devices. One device downloads the content nearby devices pull chunks from it instead of going back to the DP.
• Microsoft Connected Cache turns your DP into a caching server for cloud content like Microsoft 365 updates, cutting internet bandwidth.
• BranchCache caches content at branch offices so remote sites stop pulling large packages across the WAN repeatedly.
• Peer Cache lets designated clients serve content to other clients in the same boundary group.

Internet Clients

For devices off the corporate network, the Cloud Management Gateway (CMG) is the modern answer. It runs as a service in Azure and lets ConfigMgr clients communicate securely without VPN. Before CMG, you had to expose on-premises infrastructure to the internet. CMG replaced that entirely.

What is Microsoft Configuration Manager?

In essence, this product is the exact same product that SCCM is. There have been a few rebranding cycles. It’s useful to know the naming history because you will encounter each one of these names in the documentation, job ads, and interview questions you come across. It began with Systems Management Server (SMS) way back in the 90’s.

The product was then rebranded in 2007 as System Center Configuration Manager (SCCM) - a name that is often still used today out of habit within the industry. It was then re-branded again in 2019, removing the “System Center” branding.

Finally, in 2022, the product was merged under the umbrella of the "Microsoft Intune" family and became 'Microsoft Configuration Manager'. Same product throughout; just different names applied over the years.

The naming becomes relevant if you are looking for information for job postings or certifications, in which case it would make sense to know the most recent name, but when the topic comes up in conversation, they will all mean the exact same thing.

Features of Configuration Manager

The Six Key Capabilities ConfigMgr Brings to Your Enterprise Windows Device Management

1. Operating System Deployment (OSD)

Provision new machines or refresh existing ones with OS images through task sequences. The task sequences will automate disk partitioning, the OS installation process, the insertion of drivers and applications, and join the device to a domain. ConfigMgr OSD can manageBare-metal OS deployments.

2. Software Updates

Work hand in hand with WSUS to manage the patching for Microsoft and non-Microsoft products. ConfigMgr leverages Automatic Deployment Rules (ADRs) to download, approve, and deploy updates on an automated schedule.

3. Application Management

Design, manage, and distribute applications with detection rules, supersedence, and dependency relationships utilizing the Application Model. Manage different application install methods including MSIs, MSIXs, EXE’s, and scripts. Make apps available for end users to install via the Software Center.

4. Compliance Settings

Design baselines to enforce standards against your Windows clients. Determine whether devices have BitLocker enabled, the firewall is running, and a specific version of antivirus is in place. Identify and automate the correction of devices that do not meet compliance standards.

5. Hardware and Software Inventory

Understand every aspect of your device estate by inventorying hardware specs, installed software, file details, registry keys and more. This information can be used to create collections, custom reports, and license management.

6. Reporting

ConfigMgr builds upon Microsoft’s SQL Server Reporting Services to provide a library of pre-built reports that display the current status of software deployments, client health, patch compliance, hardware and software inventory, and much more. Create customized reports using SQL.

Configuration Manager Architecture

ConfigMgr uses a hierarchical site model. The structure depends on environment size and complexity.

Central Administration Site (CAS). Top level in a multi-site hierarchy. Provides centralized reporting and administration but does not manage clients directly. Single site environments skip it entirely.

Primary Site. Where actual device management happens. Handles clients, inventory, deployments, and daily operations. Supports up to 150,000 clients. Most organizations run one.

Secondary Site. Child of a primary site, deployed in remote locations with limited bandwidth. Provides a local DP and MP so clients communicate locally instead of across the WAN.

Site Database. SQL Server database storing all configuration, inventory, deployment status, and reporting data. Every primary site has one.

Cloud Integrations

Four cloud integration points connect ConfigMgr to the modern management world.

• Co Management: Manage Windows devices with both ConfigMgr and Intune simultaneously. The ConfigMgr client stays installed, the device enrolls in Intune, and you pick which tool handles which workload. Shift compliance to Intune while keeping OSD with ConfigMgr. Each workload moves independently at your own pace.
• Tenant Attach: Upload ConfigMgr device records to the Intune admin center. Devices stay managed by ConfigMgr, but you see them in the cloud console and can take real time actions: run queries, apply endpoint security policies, view device timeline. Cloud visibility without changing how devices are managed.
• Cloud Attach: Microsoft's term for enabling both co-management and tenant attach together. This is the recommended baseline configuration for every ConfigMgr environment in 2026.
• Cloud Management Gateway (CMG): The modern replacement for legacy internet client management. Runs as a service in Azure, acts as a secure proxy between internet-based clients and on-premises site systems. Devices at home or on the road stay managed, patched, and compliant without VPN. For any organization with remote workers, CMG is essentially mandatory.

If you want guided, hands-on practice with these cloud capabilities, MindMajix's SCCM Training program covers co-management setup, tenant attach, CMG deployment, and the full Intune migration path with lab environments.

Site System Roles

Two roles are essential in every ConfigMgr deployment.

1. Management Point (MP): How clients communicate with the site. The MP receives inventory, status messages, and state information from clients. It sends back policy assignments and content location details so clients know what to install and where to find it. Every primary site needs at least one. Larger environments run multiple for load balancing.

2. Distribution Point (DP): Where content physically lives. Applications, OS images, driver packages, update files. Clients pull what they need from the nearest DP. Place them strategically based on network topology. Branch offices with slow links get their own local DP. In 2026, DPs can also serve as Microsoft Connected Cache servers, caching cloud content locally to reduce bandwidth.

ConfigMgr vs Intune and Migration Path

This is the number one question learners ask in 2026. The short answer: it is not either/or. It is a spectrum.

When ConfigMgr Is the Better Fit?

Complex OS deployment with custom task sequences. Large on-premises environments with 100,000+ devices and established infrastructure. Locations with limited or unreliable internet. Scenarios requiring deep software distribution with complex detection rules. Organizations with heavy investment in existing task sequences and packages.

When Intune Is the Better Fit?

Cloud-first organizations where most devices are internet-connected. Remote and hybrid workforces where devices are rarely on premises. BYOD scenarios. New deployments starting from scratch in 2026. Organizations using Windows Autopilot for zero-touch provisioning.

The Migration Path:

Microsoft does not recommend a hard cutover. The path is gradual, through co-management.

Step 1. Cloud attach your environment. Turn on tenant attach and co-management. Cloud visibility without disrupting current operations.

Step 2. Shift workloads to Intune one at a time. Start with compliance policies and device configuration. Keep complex workloads like OSD with ConfigMgr.

Step 3. Provision new devices through Autopilot and Intune. Existing devices stay on ConfigMgr with co-management.

Step 4. Over time, reduce the ConfigMgr footprint as more devices move to Intune. Some organizations eventually decommission ConfigMgr. Many large enterprises run both for years.

The key point for any interview or real project: this is a gradual transition, not a rip-and-replace. Most environments in 2026 sit somewhere in the middle.

Visit here to learn more about Microsoft Intune Training

Microsoft MD-102: Endpoint Administrator Certification

If you work with Windows devices, Intune, or ConfigMgr, this is the credential to get.

What It Replaced?

The MD 100 and MD 101 examinations have been retired by Microsoft since September 30, 2023. Instead, MD 102 will combine both in a single exam that mirrors how endpoint management is handled in the cloud: connected, policy-driven, and identity-aware.

Details of the Exam:

• Full Name: Microsoft 365 Certified: Endpoint Administrator Associate
• Exam Code: MD 102
• Fee: $165 USD (~4,800 in India)
• Question Count: 40 to 60
• Time Duration: 100 minutes
• Pass Score: 700 out of 1,000
• Exam Format: Taken at a Pearson VUE exam location or online proctored.
• Exam Renewal: Annual (free online assessment)

Exam Domains:

• Deploy Windows Client (25 to 30%) covers Autopilot, provisioning packages, in-place upgrades.
• Manage Identity and Compliance (15 to 20%) covers Entra ID, Conditional Access, compliance policies.
• Manage, Maintain, and Protect Devices (40 to 45%) covers Intune configuration, endpoint security, update rings, Defender for Endpoint.
• Manage Applications (10 to 15%) covers app deployment, app protection policies, and the Microsoft Store.

Note: A restructured five-domain version launches July 24, 2026, adding automation, monitoring, and reporting. Study the current four-domain outline if testing before that date.

Is It Worth It?

This certification is used in over 45,000 job openings. Pay scales for this credential are from $85,000-$145,000. An individual with experience using Intune usually requires 4-8 weeks of dedicated study. An individual with zero Intune experience plans 8-12 weeks.

Related Article: SCCM Interview Questions And Answers