12 votessurvey · 3 comments · PowerShell » Desired State Configuration (DSC) · Flag idea as inappropriate… · Admin →
Any suggestion on how to fix the web.config for this? You were mentioning here you fixed it Matt?
This is still not fixed with WMF 5.1
I like the idea. That would solve a few problems. Anyway, I think we should be able to run an "action" not only after setting a dsc resource but also before setting it. Like, If I needed to replace a service executable, I could do something like this:
Name = 'SNMP'
StartupType = 'Automatic'
Path = "myPackage.exe"
BeforeSet = @(
AfterSet = @(
# in the xService dsc resource there will be a cmdlet like:
param($Action, [the other resource parameters])
# execute $Action
Can you take a look below and leave a comment to let me know if the workaround is sufficient for your purposes? If so, I will close this item. If not, I will keep it marked as survey.
Yes the workaround is sufficient for my particular purposes.
Thanks for having a look into this.Luigi Grilli shared this idea ·
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!
I totally agree with Justin and Sebastian.
AA DSC doesn't work for us because our machines are not connected to the internet for security reasons.
There are also bugs in the v2 pull server and the feedback I received on that has been poor. Github projects (in particular the ones from Microsoft) attract more people and issues receive more attention and comments.
Also the webapi is not documented and some webapi calls has been removed from v1 and there is no way to tell what is currently working.
To be more precise, what should be opensourced in my opinion should be the entire content of the PSDesiredStateConfiguration module, in particular the .net dlls.
36 votesinvestigating · 5 comments · PowerShell » Desired State Configuration (DSC) · Flag idea as inappropriate… · Admin →
I'm actually experiencing this problem and opened a ticket on github.
In my case the ESENT db of my pull server grows by 300MB a day with only 5 nodes configured. The suggestion that I received is that it's safe to delete the files. So I guess some scheduled task will do.
In my opinion there should be an option to limit the size of the db and after that it should start to roll logs.