For stigs on WinSrv2019, Enabled needs to be "1" not "4294967295". It's an annoying change, but it's made the protocol resource a bit useless.
Verbose logs
Resource works, just sets the wrong value and has no override ability. For now I just use the registry dsc resource and scrap protocol from schanneldsc
DSC configuration
protocol
Suggested solution
I'd imagine it's a fairly easy change to move away from the previous 4294967295 value (possibly taken from iiscrypto) and move to 1
Operating system the target node is running
windows server 2019
PowerShell version and build the target node is running
Problem description
For stigs on WinSrv2019, Enabled needs to be "1" not "4294967295". It's an annoying change, but it's made the protocol resource a bit useless.
Verbose logs
DSC configuration
Suggested solution
I'd imagine it's a fairly easy change to move away from the previous 4294967295 value (possibly taken from iiscrypto) and move to 1
Operating system the target node is running
PowerShell version and build the target node is running
SChannelDsc version