Automating the world one-liner at a time…
Customers want to be able to allow individual teams to author the portions of the configuration for which they are responsible, and then use the DSC Local Configuration Manager to merge the partial configurations and help to resolve conflicts among the partial configurations. That would help to reduce the administrative overhead for managing configurations, reduce the potential for errors, and allow teams to be flexible about making updates to the configuration on their own schedule. DSC now has that capability.
Customers have told us that they need to be able to get more information about the state of a machine that is managed using DSC. In response, we have introduced a new cmdlet that is meant to begin addressing the issue.
A new property, PSDSCRunAsCredential, is now available to specify a user credential that should be used to execute all work performed by a DSC resource.
This capability is being introduced as a common property that can be used even for existing resources.
After software ships, it is harder to introduce changes. There is a risk that any change could break something for customers who are using the current codebase. If you can get feedback while in preview it is usually easier to make changes. For this reason we are asking anyone who can take a moment to validate new features and functionality, to please share their feedback.