SCCM (System Center Configuration Manager) Interview Questions

This section covers frequently asked SCCM interview questions.

1. What is SCCM?

SCCM (System Center Configuration Manager), also known as ConfigMgr, is a Microsoft tool for managing and monitoring computers and other devices within an organization. It helps manage software deployments, operating systems, patches, and more.

2. Key Features of SCCM.

• Software deployment and management
• Operating system deployment
• Patch management
• Desired Configuration Management (DCM)
• Asset tracking
• Reporting and analytics
• Remote control

3. SCCM Boundaries.

SCCM boundaries define network locations (IP subnets, Active Directory sites, etc.) to help organize and manage devices within your infrastructure. They help the SCCM server efficiently target devices for management tasks.

4. Site Types in SCCM 2007.

• Parent Site
• Child Site
• Primary Site
• Secondary Site

5. Site Types in SCCM 2012.

• Primary Site
• Secondary Site
• Central Administration Site (CAS)

6. Central Administration Site (CAS).

The CAS is the top-level site in an SCCM hierarchy. It manages all other sites and clients within the hierarchy.

7. What is a Site Server?

A site server is a computer where the SCCM software is installed.

8. Primary Site vs. Secondary Site.

9. Child Site in SCCM.

A child site is a lower-level site in the hierarchy that reports to a parent site.

10. Client Deployment Methods in SCCM.

• Client push installation
• Logon script installation
• Software update point-based installation
• Group Policy-based installation
• Manual installation

11. WSUS (Windows Server Update Services).

WSUS is used to manage and distribute Microsoft software updates to Windows computers.

12. Limiting Collections.

When creating a new collection, you specify a limiting collection. The new collection will only contain devices that are also members of the limiting collection.

13. BITS (Background Intelligent Transfer Service).

BITS is used for efficient background transfers of data between the SCCM server and clients. It's commonly used for client installation and software updates.

14. 64-bit OS and Configuration Manager Console.

Yes, the SCCM console (though 32-bit) can run on a 64-bit operating system.

15. SUP (Software Update Point).

A SUP is a site system role responsible for distributing software updates. It typically requires WSUS to be installed on the same server.

16. Prerequisites for Software Update Point.

• Windows Update Agent
• Windows Installer
• Network load balancing (optional)
• Site server communication
• WSUS (Windows Server Update Services)
• BITS (Background Intelligent Transfer Service)

17. Package Refresh vs. Package Update.

18. SMS Provider in SCCM.

The SMS Provider provides access to the SCCM database. It uses WMI (Windows Management Instrumentation).

19. Discovery Methods in SCCM.

• Active Directory discovery
• Network discovery
• Heartbeat discovery

20. Content Library in SCCM.

The content library stores a single instance of each file needed for software deployments. It optimizes storage space and reduces redundancy.

21. Ports Used in SCCM.

(This section would list the ports used by SCCM for communication, including HTTP, HTTPS, SMB, and other ports.)

22. Client Deployment Methods (Repeated from earlier).

Manual installation, client push, upgrade, logon script, group policy, software update point.

23. Types of Senders in SCCM.

• Standard Sender
• Courier Sender

24. Deployment Share in SCCM.

A deployment share is a repository of content (applications, OS images, drivers, etc.) used for software distribution.

25. Server Locator Points.

Server Locator Points help clients locate management points, especially when Active Directory is unavailable.

26. Migrating Objects from SCCM 2007 to SCCM 2012.

(This section would list the migratable objects.)

27. SCCM vs. WSUS.

28. Types of Senders (Repeated from earlier).

Standard sender and courier sender.

29. SCCM Console.

The SCCM console is the primary interface for managing and monitoring the SCCM infrastructure.

30. Important Site System Roles.

(This section would list important site system roles, such as management point, distribution point, PXE service point, reporting point, and more.)

31. Application Detection Methods.

• Registry-based detection
• File system-based detection
• Custom detection methods
• Windows Installer-based detection

32. Inventory in SCCM.

• Software Inventory: Collects information about installed software.
• Hardware Inventory: Collects information about hardware components.

33. BDP (Boundary Data Point) in SCCM.

A Boundary Data Point (BDP) in SCCM (System Center Configuration Manager) refers to a specific network boundary used for identifying and managing devices within a network environment. Boundaries play a crucial role in determining how devices are located and how content is delivered to them in the SCCM architecture.

Function of a Boundary Data Point in SCCM

In SCCM, boundaries are used to define network segments or locations where clients are deployed. These boundaries help SCCM to determine which distribution points and management servers clients should connect to. A Boundary Data Point is a network location that helps in associating clients with the appropriate content source based on their geographical location or network segment.

How Boundary Data Points Are Used

• Client Location: SCCM uses boundaries to locate clients and assign them to specific boundary groups for optimized content delivery.
• Content Delivery: Boundaries ensure that clients connect to the nearest distribution point or server, reducing the impact on network traffic and speeding up the deployment process.
• Management: Boundaries also help SCCM determine which management server a client should communicate with, ensuring optimal performance in large distributed environments.

34. Branch Distribution Points (BDPs).

BDPs (Branch Distribution Points) are used for efficient software distribution in branch offices with limited bandwidth. They act as a cache for content downloaded from a standard distribution point.

35. Site Systems and Site System Roles.

A site system is a server or shared folder hosting SCCM services. A site system role is a specific function (like a management point or distribution point) provided by a site system.

36. Fallback Status Point.

A fallback status point provides an alternative way for clients to report their status to the SCCM server, especially when other communication paths are unavailable. It uses unauthenticated HTTP, posing security risks.

37. What is a Site Server? (Repeated from earlier).

A site server is the computer where the SCCM software is installed. It's the core of the SCCM infrastructure.

38. Services Required for Client-Server Communication.

• Computer Browser
• Windows Installer
• SMS Agent Host
• WMI (Windows Management Instrumentation)
• BITS (Background Intelligent Transfer Service)

39. Asset Intelligence in SCCM.

Asset Intelligence helps track software licenses and usage within your organization. It uses hardware inventory data to identify and report on software licenses.

40. Deployment Share (Repeated from earlier).

A deployment share is a network location containing the files (OS images, applications, etc.) needed for deployments.

41. Out-of-Band Management in SCCM.

(This section would explain out-of-band management, which allows managing devices even when they're not connected to the main network, often utilizing alternative communication methods.)

42. Database Replication in SCCM.

SCCM uses database replication (typically with SQL Server) to synchronize data across multiple sites in a hierarchy.

43. Improved HTTP Site System.

(This section would explain the enhanced security features of the improved HTTP site system, often involving certificate-based authentication.)

44. Internet-Based Client Management.

Internet-based client management allows you to manage clients that are not directly connected to your internal network, typically using a cloud management gateway (CMG).

45. Heartbeat Discovery Mode.

Heartbeat discovery is a method where clients periodically send signals to the SCCM server to update their status.

46. DPM (Data Protection Manager) in SCCM.

DPM is used for data backup and recovery within the SCCM infrastructure.

47. Asset Tracking in SCCM.

Asset tracking involves monitoring and managing hardware and software assets in your organization, often for inventory and licensing purposes.

48. Application Database Web Service Point.

The application database web service point provides application catalog data to clients.

49. Internet-Based Client Management vs. DirectAccess.

50. Network Discovery Mode.

Network discovery scans a network segment for devices with IP addresses.

51. Shared Distribution Points.

Shared distribution points are used for content distribution between SCCM sites during migrations or other scenarios where content needs to be transferred between different locations.

52. All Unknown Computers Collection.

This collection contains devices that are not yet managed by SCCM.

53. SMS Provider (Repeated from earlier).

The SMS Provider allows access to the SCCM database via WMI.

54. State Migration Point.

A state migration point is used to migrate user state data during operating system deployments. It captures and restores user settings and files.

55. Patch Management.

Patch management is the process of deploying and managing software updates (patches) to fix vulnerabilities and keep software current.

56. Global Condition Option.

The global condition option allows you to apply conditions to application deployments that affect when and to which machines the application gets deployed.

57. Updating Deployment Software in SCCM.

(This section describes the steps for updating software deployments within the SCCM console.)

58. Client Policy in SCCM.

Client policy defines how frequently clients check in with the SCCM server for updates and tasks.

59. Native vs. Mixed Mode in SCCM.

60. Software Metering in SCCM.

Software metering tracks the usage of software on managed devices.

61. Installing Applications in Software Center.

The Software Center is the interface where users can install applications deployed by SCCM.

62. Key Features Migrated from SCCM 2007 to SCCM 2012.

(This section would list the migrated features.)

63. NAP (Network Access Protection) in SCCM.

NAP helps control network access based on device health and configuration.

64. Advantage of .NET 4.7 in Configuration Manager.

Improved console performance and features.

65. WOL (Wake-On-LAN) in SCCM.

WOL allows remotely waking up computers to receive updates or perform tasks.

66. Branch Cache in SCCM.

Branch cache optimizes bandwidth usage by caching content in branch offices.

67. "Software" Definition in SCCM.

Includes software updates, applications, scripts, drivers, and configuration items.

68. Unique Task Sequence Names.

Task sequence names in SCCM don't have to be unique.

69. Deployment Share (Repeated from earlier).

A deployment share stores the files for deploying OS images and applications.

70. Intune Integration with SCCM.

Intune and SCCM (System Center Configuration Manager) can be integrated to provide a unified solution for managing both mobile devices and traditional endpoints in an enterprise environment. This integration allows organizations to take advantage of Intune's mobile device management (MDM) capabilities while leveraging SCCM's more extensive desktop management features.

Key Features of Intune and SCCM Integration

The integration of Intune with SCCM enables seamless management of mobile devices and computers across platforms. Key features include:

• Unified Endpoint Management (UEM): Manage all endpoints, including mobile devices (iOS, Android) and desktops (Windows, macOS), through a single console.
• Mobile Device Management (MDM): Intune adds MDM capabilities, allowing for the management and securing of mobile devices and apps, while SCCM continues to manage desktop devices.
• Conditional Access: Ensure that only compliant devices can access corporate resources by enforcing security policies, such as device encryption and password requirements.
• App Deployment: Both Intune and SCCM work together to deploy applications across various devices, ensuring the correct software is available on all endpoints.
• Policy Configuration: Intune allows administrators to configure and enforce security and compliance policies across mobile devices, while SCCM enforces policies for desktops and laptops.

How the Integration Works

In SCCM, you can configure Intune integration through the Cloud Management Gateway (CMG). This setup allows Intune to manage mobile devices while SCCM manages other devices. The integration also enables the hybrid approach where both systems work in tandem, ensuring that all devices in the organization, whether mobile or desktop, are properly managed.

Benefits of Intune and SCCM Integration

• Flexibility: Provides flexibility to manage devices in various environments, including on-premises, cloud, or a hybrid setup.
• Enhanced Security: Ensures that both mobile and desktop devices are compliant with security policies and access corporate resources securely.
• Simplified Management: Integrates device management for both mobile and traditional endpoints into a single interface, streamlining the administrative process.
• Cost Efficiency: Reduces the need for multiple management solutions by leveraging the combined capabilities of Intune and SCCM.

Intune's Functionality.

Intune, integrated with SCCM, extends management capabilities to mobile devices and cloud-connected Windows systems. Key functionalities include:

• Autopilot: Automates the enrollment and setup of new Windows devices.
• Mobile App Management: Deploying and managing mobile applications.
• Mobile Device Management: Enrolling and securing mobile devices within the organization.
• Managing External Devices: Managing devices outside the corporate network.