8 votessurvey · 1 comment · PowerShell » Desired State Configuration (DSC) · Flag idea as inappropriate… · Admin →
Thanks for you feedback! I What types of things do you find yourself needing to manage in the meta-config after initial deployment? This is not to take away from the need for this, I want to better understand how you and other customers are / want to use it.
We too have this issue but Arie makes a point about fundamentally changing the way the MOFs are created. If you have the same configuration applied to lots of different machines or at least partially. Consider using a partial configuration, would mean you would only need to update 1 MOF for shared changes
Thanks for the feedback! I have personally heard this request from a number of customers. IMHO having the ability to use GMS accounts would be a quite useful in DSC configurations. If this is an important feature for you as well, vote it up so that we can appropriately prioritize it as we move forward.
This is something that has to be implemented in the resource. I can't see a way that DSC can overcome this. I implemented it a while ago into the then xSqlServer resource. https://github.com/PowerShell/SqlServerDsc/pull/285
98 votes14 comments · PowerShell » Desired State Configuration (DSC) · Flag idea as inappropriate… · Admin →
We totally understand that a robust Pull server / central management solution is something that is critical to your success with DSC. We have invested quite heavily in Azure Automation DSC (AA DSC) to fill many of these needs. With that said, I would be very interested to understand if the AA DSC solution does not work for you (and other customers) and why? Vote and comment if this is important to you.
Also interesting feedback on our ‘bad ideas’. Thanks!
The protocol is public. Which means anyone can build their own PullServer. In fact their is already an OpenSource project https://duckduckgo.com/l/?kh=-1&uddg=https%3A%2F%2Fgithub.com%2Fpowershellorg%2Ftug that provide exactly that functionality