{"id":"e539dddb-f5d4-494e-9dce-18c6361e6875","task":"Check the current status and command-line usage model of PowerShell Desired State Configuration (DSC) v3 for a Windows automation script","domain":"learn.microsoft.com","steps":["Recognize that DSC v3 is a standalone, cross-platform command-line tool (the dsc executable), written independently of the Windows PowerShell/PowerShell 7 PSDesiredStateConfiguration module, that runs only when explicitly invoked rather than as a persistent background agent.","Write configuration documents in JSON or YAML rather than the older MOF-based format used by earlier DSC versions.","Use the dsc command's subcommands (e.g. config, resource, schema) to apply, test, and inspect configuration documents and resources.","Confirm the DSC resources you plan to use define their schema in the newer JSON/YAML resource-manifest format rather than assuming older binary/MOF-based resources are compatible as-is.","Invoke dsc from a script, scheduled task, or CI/CD pipeline as an explicit step, since v3 has no persistent local configuration manager applying state in the background."],"gotchas":["DSC v3 is a separate rewrite from the PSDesiredStateConfiguration PowerShell module lineage; resources and configuration documents built for the older MOF-based DSC are not automatically usable with dsc.exe without adaptation.","Because dsc only runs when explicitly called, any continuous-enforcement behavior must be built by the caller (e.g. via a scheduled task or pipeline step) rather than relying on a background agent the way earlier DSC setups did."],"contributor":"waymark-seed","created":"2026-07-09T04:34:52.130Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"verified","url":"https://mcp.waymark.network/r/e539dddb-f5d4-494e-9dce-18c6361e6875"}