How to prepare for sccm interview

Hierarchy topology

Hierarchy topologies range from a single stand-alone primary site to a group of connected primary and secondary sites with a central administration site at the top-level (top-tier) site of the hierarchy.

Microsoft System Center Configuration Manager (SCCM) is a Windows product that enables the management, deployment and security of devices and applications across an enterprise. Amongst other potential uses, administrators will commonly use SCCM for endpoint protection, patch management and software distribution.

Microsoft has Renamed System Center Configuration Manager (SCCM) to Microsoft Endpoint Configuration Manager (MECM)

Neither Intune or SCCM are going away however. Intune is still the cloud service engine that manages all your devices, albeit with a new console (https://devicemanagement.microsoft.com/), formerly known as DMAC “Device Management Admin Console,” now called Endpoint Manager console.

System Center Configuration Manager has evolved since Microsoft originally released it as “Systems Management Server” in 1994. Significant releases include: Systems Management Server 1.0, released in 1994 along with Windows NT Server 3.5.

While SCCM/ConfigMgr admins will have a lot of work for the next 5–8 years, “enterprise management” will be the solution that workers will be asked to fill. This will cover workstations, servers, tablets, kiosks, IoT, mobility, and more, with a variety of products.

Interestingly, SCCM uses WSUS. Many of you already own a license to System Center Configuration Manager as part of Software Assurance and other licensing packages. But don’t immediately assume you should be using SCCM instead of WSUS for patching.

WSUS can meet the needs of a Windows-only network at the most basic level, while SCCM offers an expanded array of tools for more control over patch deployment and endpoint visibility. SCCM also offers pathways for patching alternate OS and third party applications, but on the whole, it still leaves much to be desired.

You need a WSUS Server and integrated with SCCM for deploying patches. You can install WSUS on SCCM server or remotely as well. Below is article to configure WSUS, hope it will help to Install WSUS and add a SUP role. ConfigMgr depends on a WSUS regarding Update Management.

There is no supported way to do patching with ConfigMgr without using the WSUS feature. ConfigMgr leverages WSUS for pulling the update content and metadata from Microsoft Update and allows clients to scan against the WSUS catalog to determine which updates are available.

Go to Administration > Security > Console Connections. Right-click on a user’s console connection and select Start Microsoft Teams Chat.

WSUS database requirements

WSUS requires one of the following databases: Windows Internal Database (WID) Any supported Microsoft SQL Server version. For more information, see Microsoft Lifecycle Policy.

WSUS is a feature of Windows Server. So yes, if you wish to run a WSUS instance, you have to properly license the Windows Server instance it will be running on. Apart from that, no further server licensing is required.

Server roles WSUS requires both the Application Server and the Web Server (IIS) roles installed. Internet Information Services (IIS) is Microsoft’s web server product, and it is installed when the Web Server (IIS) role is installed.

Check Port Connectivity

As we have confirmed that the WSUS server is both listening on TCP ports 8530 and 8531 with appropriate Windows firewall rules, we will now confirm that we can connect to these from the client system.

You can check the Event Viewer on the WSUS server too. Within the WSUS console you can search for computers and view what updates are missing like this: Then you can click the “Updates with errors” link to see what the deal is with those updates.