Managing Server State using Configuration as Code
summary
PowerShell Team rewrites the Local Configuration Manager as a tiny C++ service that installs in seconds and runs cross‑platform, shipping as a ~60 MB bundle with an LCM under 10 MB core, dropping WMI/MI for an HTTP REST endpoint and adding native C++ resources alongside PowerShell and Python support. The project targets Azure scale (used across update management and security center), catalogs 1218 DSC resources, and plans staged open sourcing with an alpha→beta→GA pipeline.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 2:34Team Overview
- 4:17LCM
- 5:22DLC
- 7:44Installation
- 9:00DAC Resources
- 11:57DSC Resources
- 15:50Res API
- 21:39Questions
- 29:25Blog Post
- 32:49Parallel Execution
- 35:34Provider Model
- 37:57Jason
- 42:29DSC
related talks
01h 17mDevOps, Desired State, and Microsoft Windows
44mDesired State Configuration v3
25mThe Cultural Battle To Remove Windows from Windows Server
51mDSC v3: Evolving Declarative Configuration for Modern Systems
01h 21mBeyond the Prompt: Leveraging MCP and PowerShell for Custom LLM Actions
44mHow AWS Managed Services uses PowerShell
45mSet up your dev machine in record time with WinGet and Desired State Configuration
45mDesired State Configuration (DSC) Version 3