Mockpreps
🧑💼
🪴
Login now and master your exams with Mockpreps’ mock tests!
Top Interview Questions
System Center Configuration Manager (SCCM), now officially known as Microsoft Endpoint Configuration Manager (MECM), is a comprehensive systems management platform developed by Microsoft. It enables organizations to efficiently manage large numbers of computers, servers, and mobile devices from a centralized console. SCCM plays a critical role in enterprise IT environments by helping administrators deploy operating systems, applications, updates, and security policies while maintaining compliance and system health.
SCCM is widely used in organizations that operate Windows-based infrastructures, although it also supports macOS, Linux, and mobile devices. It integrates closely with other Microsoft technologies such as Active Directory, Windows Server Update Services (WSUS), Azure Active Directory, and Microsoft Intune, making it a powerful solution for modern device management.
SCCM was initially introduced as Systems Management Server (SMS) in the 1990s. Over time, it evolved into System Center Configuration Manager and later rebranded as Microsoft Endpoint Configuration Manager. With the rise of cloud computing and mobile workforce needs, SCCM has been enhanced with co-management capabilities that allow it to work alongside Microsoft Intune. This evolution ensures SCCM remains relevant in hybrid and cloud-first environments.
SCCM consists of several key components that work together to manage endpoints efficiently:
Site Server
The site server is the central component of SCCM. It hosts the SCCM services, processes client data, and manages overall site operations. It communicates with other site systems and the SCCM database.
SCCM Database
The database, hosted on Microsoft SQL Server, stores all configuration data, inventory details, policies, and client information. SCCM relies heavily on this database for reporting and management.
Management Point (MP)
The management point facilitates communication between SCCM clients and the site server. Clients retrieve policies and send inventory and status information through the management point.
Distribution Point (DP)
Distribution points store content such as applications, software updates, operating system images, and scripts. Clients download required content from DPs to reduce network load on the site server.
Client Agent
The SCCM client agent is installed on managed devices. It enables communication with the SCCM infrastructure and executes tasks such as software installation, update deployment, and inventory reporting.
Software Update Point (SUP)
The SUP integrates with WSUS and is used to manage and deploy Microsoft updates and patches.
SCCM collects detailed hardware and software inventory from managed devices. Hardware inventory includes CPU, memory, disk space, and peripherals, while software inventory tracks installed applications and versions. This information helps administrators make informed decisions about upgrades, compliance, and capacity planning.
SCCM enables centralized deployment of applications across the organization. Administrators can deploy software silently, schedule installations, and target specific user or device collections. Applications can be configured with detection methods, dependencies, and supersedence rules.
One of SCCM’s most powerful features is Operating System Deployment. It allows administrators to deploy Windows operating systems using task sequences. OSD supports bare-metal installations, in-place upgrades, and OS refresh scenarios, making it ideal for large-scale rollouts.
SCCM provides robust patch management capabilities through integration with WSUS. Administrators can synchronize updates, create deployment packages, and control update installation schedules. This ensures systems remain secure and compliant with organizational policies.
SCCM integrates with Microsoft Defender to provide endpoint protection. It also supports configuration baselines and compliance settings, enabling administrators to enforce security standards and detect configuration drift.
SCCM includes built-in remote control functionality, allowing IT teams to remotely assist users. This feature is essential for troubleshooting and providing support in distributed environments.
SCCM supports a hierarchical architecture designed to scale with organizational needs:
Central Administration Site (CAS): Used in large environments to manage multiple primary sites.
Primary Site: Manages clients directly and handles core management tasks.
Secondary Site: Used to manage clients in remote locations with limited bandwidth.
Small organizations often operate with a single primary site, while large enterprises may implement a CAS and multiple primary sites for scalability.
Collections are logical groupings of devices or users in SCCM. They are used to target deployments, updates, and policies. Collections can be static (manually managed) or dynamic (based on queries). Proper collection design is crucial for efficient SCCM operations.
SCCM provides extensive reporting through SQL Server Reporting Services (SSRS). Administrators can generate reports related to inventory, compliance, software usage, and deployment status. Monitoring dashboards help track site health, component status, and client activity.
Modern SCCM environments often use co-management, where SCCM and Microsoft Intune work together to manage devices. This hybrid approach allows organizations to leverage cloud-based management while retaining on-premises control. Features such as Cloud Management Gateway (CMG) enable internet-based device management without requiring VPN connectivity.
Centralized endpoint management
Improved security and compliance
Reduced manual administrative effort
Efficient software and patch deployment
Scalable architecture for enterprises
Strong integration with Microsoft ecosystem
Despite its strengths, SCCM has some challenges:
Complex initial setup and maintenance
Requires skilled administrators
Dependence on SQL Server and Windows infrastructure
Higher infrastructure and licensing costs compared to lightweight tools
However, these challenges are often outweighed by its powerful capabilities in large environments.
Managing thousands of corporate endpoints
Automated OS deployment in enterprises
Centralized patch management
Software license tracking
Compliance enforcement in regulated industries
Answer:
SCCM (System Center Configuration Manager) is a Microsoft tool used to manage computers and servers in an organization. It helps administrators deploy software, install updates, manage operating systems, monitor hardware/software inventory, and ensure security compliance.
SCCM is now part of Microsoft Endpoint Configuration Manager (MECM).
Answer:
SCCM is used to:
Deploy software automatically
Manage Windows updates and patches
Install operating systems remotely
Monitor hardware and software inventory
Enforce security policies
Reduce manual work in large environments
Answer:
The main SCCM components are:
Site Server – Central server that manages SCCM operations
Site Database – Stores SCCM data (uses SQL Server)
Distribution Point (DP) – Stores content like applications and updates
Management Point (MP) – Communication point between clients and server
SCCM Client – Installed on managed devices
Answer:
An SCCM site is a logical boundary that manages clients, resources, and policies.
Types of SCCM sites:
Primary Site – Manages clients directly
Secondary Site – Used for remote locations
Central Administration Site (CAS) – Used in large hierarchies
Answer:
The SCCM client is a software agent installed on each computer.
It communicates with the SCCM server and performs tasks like:
Software installation
Patch installation
Inventory reporting
Policy enforcement
Answer:
SCCM client can be installed by:
Client Push Installation
Manual installation
Group Policy
Software Update Point
Imaging during OS deployment
Answer:
A Distribution Point is a server that stores content such as applications, updates, and OS images.
Clients download content from the nearest DP to reduce network traffic.
Answer:
The Management Point acts as a communication bridge between the SCCM client and server.
It sends policies to clients and receives status messages.
Answer:
A Collection is a group of devices or users used for:
Software deployment
Patch deployment
Reporting
Types of collections:
Device Collection
User Collection
Answer:
Software deployment is the process of installing applications automatically on multiple computers using SCCM.
It can be:
Available – User installs manually
Required – Automatically installs on deadline
Answer:
| Application | Package |
|---|---|
| User-based deployment | Device-based deployment |
| Supports detection method | No detection method |
| Supports dependencies | No dependencies |
| Modern method | Traditional method |
Answer:
A detection method is used to check if software is already installed on a client before installing it again.
It prevents duplicate installations.
Answer:
Patch management ensures systems are updated with the latest security and feature updates.
Steps include:
Synchronizing updates
Creating update groups
Deploying updates
Monitoring compliance
Answer:
WSUS (Windows Server Update Services) is used by SCCM to download and manage Windows updates.
SCCM integrates with WSUS to provide advanced patch management.
Answer:
SUP is an SCCM role that integrates WSUS with SCCM to manage software updates.
Answer:
OSD is the process of installing Windows operating systems remotely using SCCM.
It includes:
Boot images
OS images
Task sequences
Answer:
A task sequence is a set of automated steps used to deploy OS, drivers, software, and configurations.
Answer:
Hardware Inventory collects information like:
CPU
RAM
Disk
BIOS
Network details
Answer:
Software Inventory tracks installed applications and executable files on client systems.
Answer:
A boundary defines a network location such as IP range or Active Directory site.
Answer:
Boundary Groups are used to:
Assign Distribution Points
Assign Management Points
Optimize content download
Answer:
Compliance settings ensure systems follow company policies, such as registry settings or security rules.
Answer:
SCCM uses SQL Server Reporting Services (SSRS) to generate reports like:
Software deployment status
Patch compliance
Hardware inventory
Answer:
Common SCCM ports:
80 / 443 – Client communication
445 – Client push
1433 – SQL Server
Answer:
SCCM integrates with Microsoft Intune for cloud-based management of devices.
Answer:
The SCCM Console is the graphical interface used by administrators to manage SCCM tasks.
Answer:
Client health ensures the SCCM client is installed, running, and communicating properly.
Answer:
Logs help troubleshoot SCCM issues. Important logs include:
ClientIDManagerStartup.log
LocationServices.log
PolicyAgent.log
AppEnforce.log
Answer:
Content distribution copies applications, packages, and updates from the site server to Distribution Points.
Answer:
Freshers should know:
Windows OS basics
Active Directory
Networking basics
Patch management
Software deployment concepts
Answer:
Client Push Installation is a method where the SCCM server automatically installs the SCCM client on computers in the domain.
Requirements:
Admin credentials
Client push enabled
Firewall ports open
Computer reachable
Answer:
FSP helps track client installation failures when a client cannot communicate with the Management Point.
Answer:
PXE (Preboot Execution Environment) allows computers to boot from the network and install OS without using USB or DVD.
Answer:
A Boot Image contains Windows PE and is used to start the system during OS deployment.
Answer:
An OS Image is the actual Windows operating system file (WIM) that gets installed on the computer.
Answer:
Driver packages contain hardware drivers required during OS deployment for different models.
Answer:
A Maintenance Window defines allowed time when SCCM can install software or updates on devices.
Answer:
ADR automatically creates and deploys software updates based on predefined rules.
Answer:
Software Metering tracks how often an application is used in an organization.
Answer:
Endpoint Protection integrates antivirus and malware protection into SCCM.
Answer:
It allows admins to assign permissions based on job roles.
Answer:
SCCM hierarchy is the structure of SCCM sites, such as CAS, Primary, and Secondary sites.
Answer:
A Site System Role is a function assigned to a server, such as:
Distribution Point
Management Point
Software Update Point
Answer:
Heartbeat Discovery checks if SCCM clients are active and reachable.
Answer:
It discovers users, computers, and groups from Active Directory.
Answer:
Boundary types include:
IP Subnet
IP Range
Active Directory Site
IPv6 Prefix
Answer:
Client policy defines how often the client checks with the server for updates and deployments.
Answer:
BITS (Background Intelligent Transfer Service) controls bandwidth usage while downloading content.
Answer:
Peer Cache allows clients to share content with other clients, reducing DP load.
Answer:
BranchCache allows content sharing between clients in the same network location.
Answer:
SMP stores user data and settings during OS deployment.
Answer:
UDA links users with their primary devices.
Answer:
Client Notification allows admins to remotely trigger actions like policy refresh.
Answer:
Software Center is the client-side portal where users install applications.
Answer:
Co-management allows managing devices using SCCM and Intune together.
Answer:
CMG allows SCCM to manage internet-based clients.
Answer:
It is the process of downloading update metadata from Microsoft.
Answer:
It defines how often updates are synced from Microsoft.
Answer:
Supersedence allows replacing older applications with newer versions.
Answer:
Dependencies ensure required software installs first.
Answer:
The Content Library stores all deployment content.
Answer:
Client cache temporarily stores downloaded content on the client machine.
Answer:
Defines how SCCM retries failed installations.
Answer:
It connects SCCM to Microsoft cloud services.
Answer:
SCCM upgrades include:
Pre-requisite check
Backup
In-console update
Answer:
Check:
Client status
Logs
Boundaries
DP content
Policy refresh
Answer:
Tracks application installation results.
Answer:
Shows DP and MP assignment.
Answer:
Tracks policy download and execution.
Answer:
Checks whether the SCCM client is working properly.
Answer:
SCCM architecture consists of multiple components working together to manage endpoints.
Key components:
Site Server – Core server hosting SCCM services
SQL Server – Stores configuration, inventory, status, and reporting data
Management Point (MP) – Client communication for policy and status
Distribution Point (DP) – Stores content like apps, updates, OS images
Software Update Point (SUP) – Integrates WSUS for patching
Clients – Endpoints managed by SCCM
In enterprise environments, SCCM is deployed using CAS + Primary + Secondary sites for scalability.
Answer:
CAS (Central Administration Site) is used only in very large environments (more than 150,000 clients).
Purpose:
Centralized administration
Reporting across multiple primary sites
Database replication
CAS does not manage clients directly.
Answer:
| Primary Site | Secondary Site |
|---|---|
| Manages clients directly | Does not manage clients |
| Has SQL database | Uses SQL Express |
| Used for administration | Used for bandwidth control |
| Supports MP and DP | Supports DP only |
Answer:
Client communication flow:
Client contacts Management Point
Receives policy
Downloads content from Distribution Point
Reports status back to MP
Data stored in SQL Database
Communication happens over HTTP/HTTPS.
Answer:
Boundary defines a network location (IP range, AD site)
Boundary Group assigns site systems (DP/MP) to boundaries
Real-time example:
If boundaries are not configured correctly, clients may download applications from wrong DPs, causing slow downloads.
Answer:
Content distribution copies data from site server to DPs.
Troubleshooting steps:
Check distmgr.log
Verify DP disk space
Validate boundary group
Redistribute content
Check DP status in console
Answer:
| Application | Package |
|---|---|
| Detection method | No detection |
| User-centric | Device-centric |
| Supports dependencies | No dependencies |
| Modern deployment | Legacy |
Real-time:
Applications are used for MSI/EXE software, packages for scripts and legacy apps.
Answer:
Detection method checks if an application is already installed.
Importance:
Prevents reinstallations
Ensures accurate compliance
Helps with remediation
Answer:
WSUS synchronization
Software update filtering
Create Software Update Group
Deploy updates
Monitor compliance
Troubleshoot failures
Answer:
ADR (Automatic Deployment Rule) automates patch deployment.
Usage example:
Monthly Windows patching
Auto-create SUG
Auto-deploy to test and production collections
Answer:
Check WUAHandler.log
Check UpdatesDeployment.log
Verify maintenance window
Check reboot settings
Confirm boundary & DP
Answer:
OSD includes:
PXE boot
Boot image (WinPE)
Task sequence
OS image
Drivers
Applications
Domain join
Used for new builds and refresh scenarios.
Answer:
PXE allows network boot.
Common issues:
DHCP not configured
WDS service stopped
Boot image not distributed
Boundary misconfiguration
Answer:
A task sequence is an automated workflow.
Types:
New computer
Refresh
Replace
In-place upgrade
Answer:
Best practice:
Use Driver Packages
Model-based driver management
Avoid driver auto-apply
Use WMI queries
Answer:
Defines when deployments are allowed.
Importance:
Prevents business disruption
Controls reboot timing
Used for servers mostly
Answer:
Tracks application usage.
Use case:
License optimization
Unused software removal
Answer:
Co-management allows SCCM and Intune to manage devices together.
Benefits:
Cloud management
Remote device management
Modern workplace support
Answer:
CMG (Cloud Management Gateway) manages internet-based clients without VPN.
Answer:
Client-side:
AppEnforce.log
AppDiscovery.log
LocationServices.log
PolicyAgent.log
UpdatesDeployment.log
Server-side:
distmgr.log
mpcontrol.log
smsexec.log
Answer:
Client health ensures agent functionality.
Fix methods:
Client repair
Reinstall client
Clear cache
Reset WMI
Answer:
Peer Cache: Client shares content
BranchCache: Network-level caching
Used to reduce WAN traffic.
Answer:
Allows controlled access using:
Security roles
Scopes
Collections
Answer:
Backup database
Run prerequisite check
Install in-console update
Monitor logs
Upgrade clients
Question: Application deployed but not installing?
Answer approach:
Check collection membership
Policy refresh
Boundary & DP
Detection method
AppEnforce.log
Answer:
SQL maintenance
Proper boundary design
Content cleanup
DP load balancing
Hardware sizing
Answer:
HTTPS uses PKI certificates
Required for internet clients
More secure
Answer:
Uses SSRS.
Customization:
SQL queries
Modify RDL files
Role-based access
Answer:
Application deployment
Patch monitoring
Client troubleshooting
OSD support
Reporting
Upgrade planning
Answer:
Proper boundary design
Test deployments first
Monitor logs
Keep SCCM updated
Document changes
Answer:
Best practices:
Use Active Directory Sites as boundaries
Avoid IP subnets unless required
Create separate boundary groups for each location
Assign local DPs to boundary groups
Enable fallback only if needed
Proper boundary design prevents slow downloads and wrong DP selection.
Answer:
Steps:
Check ClientIDManagerStartup.log
Verify MP in LocationServices.log
Trigger machine & user policy
Restart SMS Agent Host
Check boundary & boundary group
Answer:
Possible reasons:
Wrong detection method
Application supersedence issue
Cached old content
Incorrect install command
Check AppDiscovery.log and AppEnforce.log.
Answer:
Check distmgr.log
Verify DP status
Check disk space
Redistribute content
Validate DP certificate (HTTPS)
Answer:
Client Push: Automated, admin credentials required
Manual: ccmsetup.exe used
Client push is preferred for domain-joined systems.
Answer:
Separate server collections
Use maintenance windows
Test patches in pre-prod
Use ADRs
Monitor reboot status
Answer:
Possible reasons:
WSUS sync failed
Updates not downloaded
Maintenance window missing
Client WUA issue
Boundary issue
Check WUAHandler.log and UpdatesDeployment.log.
Answer:
Client cache stores downloaded content.
Management:
Configure cache size
Clear cache via control panel
Delete CCMCACHE folder if needed
Answer:
Validates DP content integrity.
Used when:
Content download fails
Hash mismatch errors
Corrupted packages
Answer:
Features:
Site server HA
SQL Always On
Multiple MPs
Multiple DPs
Ensures minimum downtime.
Answer:
SCCM console monitoring workspace
Site status
Component status
SQL performance
Alerts
Answer:
WMI stores client configuration and inventory data.
If WMI is corrupted:
Client fails
Inventory fails
App install fails
Answer:
Steps:
Stop SCCM services
Rebuild WMI repository
Reinstall SCCM client
Answer:
| In-Place Upgrade | Refresh |
|---|---|
| Upgrade OS without wipe | Wipes OS and reinstalls |
| Keeps apps and data | Fresh install |
| Used for Windows 10 → 11 | Used for rebuilds |
Answer:
Enable HTTPS
PKI certificates
RBAC
Limit admin access
Firewall hardening
Answer:
Includes:
Database cleanup
Backup tasks
Reindexing
WSUS cleanup
Answer:
Check InventoryAgent.log
Verify hardware inventory schedule
Reset inventory cycle
Answer:
CMPivot is a real-time query tool to retrieve live data from clients.
Answer:
Boundary groups
Peer Cache
BranchCache
Secondary sites
Answer:
Root causes:
Missing storage drivers
Corrupt OS image
DP content missing
Check smsts.log.
Answer:
Used to test new client versions before full rollout.
Answer:
Uses PKI certificates for:
Client authentication
Secure communication
Internet-based clients
Answer:
Check mpcontrol.log
Verify IIS
Check SSL binding
Restart IIS services
Answer:
Safely removes unused site roles and cleans database references.
Answer:
Used when migrating:
Old SCCM versions
New hierarchy
Hardware refresh
Answer:
Restart SMS Agent Host
Reset policy
Clear cache
Check SCClient.log
Answer:
Used to replace:
Old Java versions
Old browsers
Automatically uninstall old version and install new one.
Answer:
Index maintenance
Cleanup obsolete data
Monitor SQL IO
Answer:
SCCM: On-prem, deep control
Intune: Cloud, mobile-first
Co-management: Best of both
Question: Patch installed but system not rebooted?
Answer:
Check restart settings
Maintenance window
User deferral policy
UpdatesDeployment.log
