Author Posts

April 26, 2017 at 10:46 am

Hi,

I have found a bug in DSC and am wondering where to report it.

UserVoice appears to be mostly dead and when I filed it as an Issue on GitHub I was told they were not responsible.

http://stackoverflow.com/questions/43413382/powershell-dsc-credential-decryption-error

April 26, 2017 at 5:59 pm

UserVoice is still the best medium to report issues. On the side note this is a known issue to the PowerShell DSC team so having more votes on uservoice to prioritize would certainly help the team. Here are some already existing threads on decryption issues:
https://windowsserver.uservoice.com/forums/301869-powershell/suggestions/13683843-shared-partial-configurations-configurationnames
https://windowsserver.uservoice.com/forums/301869-powershell/suggestions/18972718-bug-dsc-decryption-across-servers-not-working

April 26, 2017 at 8:32 pm

The second post is by me.

The first one can be handled if you name each partial configuration $partialconfigname.$computername and you put each configuration function in its own file with:
–Begin File–
Param($configname)
Configuration $configname {
...
}
–End File–

The problem I have pointed out is unrelated. If the DSC team is aware then, as has unfortunately become common with DSC, it is completely undocumented