Open nawijesi opened 3 years ago
The logs were not showing exactly which security options setting was causing this issue on the client. So through the process of elimination we pinpointed the cause to this security options policy:
Network_security_Configure_encryption_types_allowed_for_Kerberos = 'AES128_HMAC_SHA1','AES256_HMAC_SHA1','RC4_HMAC_MD5'
Running the security options locally on the Windows 10 Client had no issues. The error was only occurring through Azure automation state configuration
The error handling needs to be improved for SecurityOptions as if one fails, the failure does not appear properly on logs.
Details of the scenario you tried and the problem that is occurring
Running the SecurityOptions configuration on Windows 10 clients fails when connecting Windows 10 client to Azure automation state configuration (running this security options locally on the client works fine with 0 issues)
Verbose logs showing the problem
DSC Configuration 'RegistrationMetaConfigV2' completed with error(s). Following are the first few: Cannot bind argument to parameter 'ReferenceObject' because it is null. The PowerShell DSC resource '[SecurityOption]SecurityOptions' with SourceInfo '::299::5::SecurityOption' threw one or more non-terminating errors while running the Set-TargetResource functionality. These errors are logged to the ETW channel called Microsoft-Windows-DSC/Operational. Refer to this channel for more details. The SendConfigurationApply function did not succeed.
Suggested solution to the issue
The DSC configuration that is used to reproduce the issue (as detailed as possible)
The operating system the target node is running
Windows 10 Clients on the image Windows 10 Enterprise . Version 20H2.
Version and build of PowerShell the target node is running
Powershell 5
Version of the DSC module that was used
Latest