Skip to main content

Lab 00: Enterprise Standalone Primary Site Baseline Architecture (SCCM / MECM)

Overview​

Microsoft Endpoint Configuration Manager (ConfigMgr / SCCM) remains the cornerstone of enterprise Windows systems management—orchestrating operating system deployment (OSD), patch compliance, software distribution, and Intune co-management.

This architecture lab documents the build-out of a Standalone Primary Site (PR1) on Windows Server 2022, including Active Directory schema preparation, System Management container delegation, SQL Server 2022 collation & memory tuning, and IP Address Range boundary group design.

Lab Topology & Addressing​

HostnameRoleOperating SystemIPv4 AddressSubnet MaskDefault GatewayDNS
DC01AD DS, DNS, DHCP, Enterprise CAWindows Server 202210.10.10.10255.255.255.010.10.10.1127.0.0.1
CM01Primary Site Server (PR1), MP, DP, SUP, SQLWindows Server 202210.10.10.20255.255.255.010.10.10.110.10.10.10
CLIENT01Managed Enterprise WorkstationWindows 11 23H2 Enterprise10.10.10.101 (DHCP)255.255.255.010.10.10.110.10.10.10

Implementation Phases​

1. Active Directory Schema Extension & Delegation (DC01)​

  1. Extend the Active Directory schema using extadsch.exe from the ConfigMgr installation media and verify Successfully extended the Active Directory schema in C:\ExtADSch.log.
  2. In adsiedit.msc, create the CN=System Management container under CN=System.
  3. Delegate Full Control permissions on CN=System Management (applied to This object and all descendant objects) to the site server computer account CM01$ so the Primary Site can publish Management Point (SMS-MP-PR1-*) and Site (SMS-Site-PR1) records directly to AD.

2. Site Server Prerequisites & SQL Server 2022 Tuning (CM01)​

  1. Install required IIS, BITS, and Remote Differential Compression features via PowerShell: 
    Install-WindowsFeature -Name Web-Server, Web-Windows-Auth, Web-WMI, Web-Metabase, BITS, BITS-IIS-Ext, RDC, NET-Framework-45-Features, NET-WCF-HTTP-Activation45 -IncludeManagementTools
  2. Install Windows ADK for Windows 11 and the Windows PE Add-on.
  3. Deploy Microsoft SQL Server 2022 with strict ConfigMgr requirements:
    • Instance Collation: SQL_Latin1_General_CP1_CI_AS (mandatory to avoid prerequisite failures and character-sorting corruption).
    • Memory Allocation: Cap SQL Server Maximum Server Memory at 12,288 MB (leaving dedicated headroom for SMSExec.exe and IIS worker processes).
  4. Install the WSUS role backed by the local SQL Server instance to support the Software Update Point (SUP).

3. Boundary Group Architecture (Why IP Address Ranges Beat Subnets)​

  1. Configure a Boundary of type IP Address Range (10.10.10.1 – 10.10.10.254) rather than an IP Subnet boundary.
  2. Associate the boundary with Boundary Group BG-HQ-Corporate, enable Site Assignment (PR1), and bind CM01 as the local Distribution Point and Management Point.
[Architectural Insight: Why Avoid IP Subnet Boundaries?]

In enterprise networks utilizing CIDR supernetting (such as /22 or /23), Windows client network adapters can report classful subnet IDs in WMI. If ConfigMgr evaluates a /24 Subnet ID that does not match the client's calculated Subnet ID, boundary evaluation fails silently and the client falls back to default site resources or refuses content download. IP Address Ranges evaluate the client's raw IPv4 address numerically, eliminating subnet mask ambiguity completely.

4. Client Bootstrap & Log Verification (CLIENT01)​

  1. Deploy the ConfigMgr client agent via Client Push or explicit bootstrap: 
    ccmsetup.exe /mp:cm01.corp.contoso.com SMSSITECODE=PR1 SMSMP=cm01.corp.contoso.com
  2. Validate end-to-end health across the ConfigMgr log chain:
    • %windir%\ccmsetup\logs\ccmsetup.log → ccmsetup is exiting with return code 0
    • C:\Program Files\Microsoft Configuration Manager\Logs\MPcontrol.log → Http test request succeeded (status code 200)
    • ClientIDManagerStartup.log & LocationServices.log → Confirm AD/MP lookup and site code PR1 registration.