My Favorite DSC Feature Suggestions on UserVoice (upvote!)

PowerShell for Admins

Hopefully, you're aware that Microsoft is moving to UserVoice for accepting feature requests and bugs. DSC in particular has 30-odd suggestions at present, and I thought I'd run through some of my fav's. Log in and up-vote the ones you like, or add comments to expand the discussion!

  • Add Maintenance Windows Awareness to DSC/LCM. This is one of mine, but it came from several customer suggestions.
  • Change the Pull Server database to SQL Server. Broadly, this is a great idea. In theory, you should be able to modify the web.config file and direct it to a SQL Server already, but nobody knows the database schema that the pull server expects.
  • Refactor the LCM's validation logic. This is another of mine, and it's crucial. Right now, only the LCM can validate multiple partial configs and tell you if there's a validation problem like a duplicate key. This means our only possible point of failure is the target node, which is the worst possible place for that to be. Factoring the logic out would let us built a pull server that could combine multiple configurations server-side, and spit out a combined, pre-validated MOF for the target to consume. We could also use the configuration logic to manually combine and validate MOFs in a test or RSoP mode, perhaps with a cmdlet.

There's plenty more - have a look, vote for ones you like, and add your own suggestions! And there's a lot more besides DSC in there - see anything that you think is important?

One Response to " My Favorite DSC Feature Suggestions on UserVoice (upvote!) "

  1. Justin King says:

    Is there a suggestion limit? I ran into that with SCCM… Guess I’ll find out.
    The big one for me involves the pull server and its lack of tool features to help initial configuration, most notably how poorly it handles client registration and certificates when compared to things like puppet open source which is equally free. I know it’s a framework, but it’s just too dry right now