<\/p>\n
This is the first post in a multi-part series about the new release of DSC.<\/em><\/p>\n We’re pleased to announce the General Availability of Microsoft’s Desired State Configuration (DSC)<\/strong>\nversion 3.0.0.<\/strong><\/p>\n This version marks a significant evolution in cloud-native configuration management\nfor cross-platform environments. DSC is a declarative configuration and orchestration platform that\ndefines a standard way of exposing settings for applications and services. It’s a tool for managing\nsystems and applications by describing what they should look like rather than how to make it that\nway. DSC simplifies system, service, and application management by separating what to do from how to\ndo it.<\/p>\n With DSC, you can:<\/p>\n Windows PowerShell 5.1 includes PowerShell Desired State Configuration (PSDSC). We refer to as\nclassic DSC, which encompasses PSDSC v1.1 and v2. However, DSC can use any classic DSC resources\nthat exist today, including the script-based and class-based PSDSC resources. You can use PSDSC\nresources in DSC with both Windows PowerShell and PowerShell.<\/p>\n The release of DSC is a major change to the DSC platform. DSC differs from PSDSC in a few important\nways:<\/p>\n DSC follows semantic versioning. The first release of DSC, version 3.0.0, is a Stable release.<\/p>\n The first release of DSC, version Always update to the latest patch version of the release you’re using.<\/p>\n As I mentioned at the top of this post, this was the first in a series of posts about the new DSC. For the subsequent posts:<\/p>\n Now you are ready for the next post: Get Started with Desired State Configuration v3.0.0 (DSC)<\/a><\/p>\n For more information about Desired State Configuration v3.0 (DSC), visit the\nDSC documentation<\/a>. We value your feedback. Stop by our GitHub repository<\/a> and let us\nknow of any issues you find.<\/p>\n Jason Helmick<\/p>\n Sr. Product Manager, PowerShell<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" This post announces the release of Microsoft Desired State Configuration v3.0.0. We discuss the features and benefits of DSC and how it differs from PowerShell DSC.<\/p>\n","protected":false},"author":7527,"featured_media":13641,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[3197],"class_list":["post-20702","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-powershell","tag-powershell-dsc"],"acf":[],"blog_post_summary":" This post announces the release of Microsoft Desired State Configuration v3.0.0. We discuss the features and benefits of DSC and how it differs from PowerShell DSC.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/20702","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/users\/7527"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/comments?post=20702"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/20702\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media\/13641"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media?parent=20702"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/categories?post=20702"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/tags?post=20702"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Benefits of DSC<\/h2>\n
\n
\n
Differences from PowerShell DSC<\/h2>\n
\n
Features of DSC<\/h2>\n
\n
dependsOn<\/code> keyword to define the order those groups are applied in a configuration.<\/li>\nMicrosoft.Dsc\/Assertion<\/code> (a special group resource) to validate the\nenvironment before running the configuration.The DSC repository has an example<\/a> that shows how you can use an assertion to manage a\nresource that should only run on a specific operating system.<\/li>\nMicrosoft.DSC\/Include<\/code>\nresource.The DSC repository has an example<\/a> that shows how you can use the Microsoft.Dsc\/Include<\/code>\nresource to reuse a separate configuration document file, enabling you to compose a complex\nconfiguration from smaller, simpler configuration documents.<\/li>\ndsc resource export<\/code><\/a> command to get\nevery instance of that resource on a machine. Use the dsc config export<\/code><\/a> command to look up\na set of resources and return a new configuration document containing every instance of those\nresources.<\/li>\nSupport lifecycle<\/h2>\n
3.0.0<\/code>, is a Stable release. Patch releases update the third\ndigit of the semantic version number. For example, 3.0.1 is a patch update to 3.0.0. Stable releases\nreceive patches for critical bugs and security vulnerabilities for three months after the next\nStable release. For example, version 3.0.0 is supported for three months after 3.1.0 is released.<\/p>\nNext steps<\/h2>\n
\n
Call to action<\/h2>\n