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
Hello, I´ve updated fully working DSC code by Local Security Policy (GPO), by using GPRegistryPolicyDSC Module.
Verbose logs showing the problem
Machine in Azure DSC is still in-progress status, never finishes the configuration (normally configured in 10min including software installations)
Error from Azure DSC RAW Report: Index was out of range. Must be non-negative and less than the size of the collection. xDSCDiagnostics module points to this particular module.
Suggested solution to the issue
Let the module to finish the configuration and configure the policies accordingly.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
Details of the scenario you tried and the problem that is occurring
Hello, I´ve updated fully working DSC code by Local Security Policy (GPO), by using GPRegistryPolicyDSC Module.
Verbose logs showing the problem
Machine in Azure DSC is still in-progress status, never finishes the configuration (normally configured in 10min including software installations)
Error from Azure DSC RAW Report: Index was out of range. Must be non-negative and less than the size of the collection. xDSCDiagnostics module points to this particular module.
Suggested solution to the issue
Let the module to finish the configuration and configure the policies accordingly.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
The operating system the target node is running
Windows Server 2019 or Windows Server 2019 Core (both contains WMF 5.1 by default), English language.,
Version and build of PowerShell the target node is running
Powershell 5.1
Version of the DSC module that was used
GPRegistryPolicyDsc module version 1.2.0
@johlju @jcwalker @gaelcolas @NicolasBn do you have any clue where the problem is, please?
The text was updated successfully, but these errors were encountered: