Skip to main content

Lab 01: Modern Windows 11 Thin-Image OSD Task Sequence Architecture

Architectural Decision: "Thin" vs. "Thick" Imaging​

Legacy "Thick" imaging workflows—where administrators manually install software onto a reference VM, run sysprep.exe /generalize /oobe /shutdown, and capture a monolithic 25GB+ .wim—introduce severe maintenance debt every time an application or cumulative update is released.

Modern enterprise Endpoint Engineering standardizes on a Thin Image Architecture:

  1. Import a clean, unmodified install.wim directly from the Microsoft Windows 11 Enterprise ISO.
  2. Use a modular ConfigMgr Task Sequence to dynamically layer UEFI/GPT disk partitioning, WMI model-targeted driver packages, the ConfigMgr Client Agent, state-based applications, and Active Directory domain join at deployment time.

Implementation Workflow​

Phase 1: WIM Inspection & Content Distribution​

  1. Mount the official Windows 11 23H2 Enterprise ISO and inspect image indexes via PowerShell: 
    Get-WindowsImage -ImagePath "E:\sources\install.wim"
  2. Stage install.wim on the Site Server content share (\\cm01.corp.contoso.com\Sources$\OSD\OS_Images\Windows11_23H2_Enterprise\install.wim).
  3. Import the Operating System Image into Software Library > Operating Systems > Operating System Images, extracting the Windows 11 Enterprise index, and distribute content to Distribution Point CM01 (verifying completion in distmgr.log).

Phase 2: WinPE Boot Image & ConfigMgr PXE Responder​

  1. Configure the Boot image (x64) with command support (F8 WinPE console for ipconfig, diskpart, and CMTrace.exe inspection during testing) and distribute to CM01.
  2. Enable the native ConfigMgr PXE Responder Service (sccmpxe.exe) on the Distribution Point (Enable PXE support for clients, Respond to incoming PXE requests on all network interfaces) without requiring legacy Windows Deployment Services (WDS).

Phase 3: Modular Task Sequence Engineering​

Construct the custom Task Sequence (Deploy Windows 11 23H2 Enterprise - Thin Image) with explicit phase boundaries:

  1. Initialize & Boot to WinPE:
    • Reboot into the assigned x64 WinPE Boot Image.
  2. Format and Partition Disk (UEFI / GPT Guarded):
    • Condition: Task Sequence Variable _SMSTSBootUEFI equals true
    • EFI System Partition: 500 MB FAT32
    • MSR Partition: 128 MB
    • Windows Partition: 99% remaining space NTFS (OSDTargetSystemDrive)
    • Recovery Partition: Remaining space NTFS
  3. Apply Operating System & Network Settings:
    • Apply Windows 11 Enterprise 23H2 x64 (Clean ISO) index.
    • Join corp.contoso.com into target OU OU=Workstations,DC=corp,DC=contoso,DC=com using a least-privilege Domain Join service account (corp\svc_sccm_dj delegated only Create/Delete Computer Objects on the target OU).
  4. Setup Windows and ConfigMgr Client:
    • Bootstrap the client with SMSMP=cm01.corp.contoso.com.
  5. Dynamic Application Layering:
    • Install core enterprise applications via the state-based Application Model (7-Zip, Microsoft 365 Apps for Enterprise, Endpoint Protection) with Continue on error and exit-code 3010 (soft reboot) handling.

Verification & smsts.log Telemetry Locations​

Tracking smsts.log with CMTrace.exe as the Task Sequence transitions across storage phases is essential for OSD troubleshooting:

OSD Execution PhaseActive smsts.log Path
1. WinPE (Before Disk Format)X:\Windows\Temp\smstslog\smsts.log
2. WinPE (After Disk Format)X:\smstslog\smsts.log and C:\_SMSTaskSequence\Logs\Smstslog\smsts.log
3. Full OS (ConfigMgr Agent Active)C:\Windows\CCM\Logs\Smstslog\smsts.log
4. Post-OSD CompletionC:\Windows\CCM\Logs\smsts.log