You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Details of the scenario you tried and the problem that is occurring:
We are using this module in order to configure the WinRM HTTPS listener in an unorthodox manner-- utilizing a self-signed certificate with the same "Hostname" across all machines. This has worked well for us!
What I have discovered is that if we the HTTPS listener is already configured with a different certificate/hostname, the DSC resource will not overwrite the existing listener with the specified hostrname/thumbprint.
The DSC configuration that is using the resource (as detailed as possible):
In this case, we are using DSC within Chef-- but the same action occurs when using vanilla DSC:
Details of the scenario you tried and the problem that is occurring:
We are using this module in order to configure the WinRM HTTPS listener in an unorthodox manner-- utilizing a self-signed certificate with the same "Hostname" across all machines. This has worked well for us!
What I have discovered is that if we the HTTPS listener is already configured with a different certificate/hostname, the DSC resource will not overwrite the existing listener with the specified hostrname/thumbprint.
The DSC configuration that is using the resource (as detailed as possible):
In this case, we are using DSC within Chef-- but the same action occurs when using vanilla DSC:
In order to replicate:
Configure WinRM HTTPS listener with a self-signed certificate:
Then use DSC to try to overwrite those values:
DSC will complete successfully and indicate everything is up to date, but will not overwrite the existing listener with the new values.
Version of the Operating System and PowerShell the DSC Target Node is running:
Server 2016, PowerShell 5.1
Version of the DSC module you're using, or 'dev' if you're using current dev branch:
2.2.0.84
Any help is greatly appreciated-- thanks for your excellent work on this module!
The text was updated successfully, but these errors were encountered: