We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When testing, if the Key property contained 'HKEY_LOCAL_MACHINE' in the string, the resource always returned compliant.
RegistryPolicyFile 'AllowInputPersonalization' { Ensure = 'Present' Key = 'HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\InputPersonalization' TargetType = 'ComputerConfiguration' ValueName = 'AllowInputPersonalization' ValueType = 'DWord' ValueData = '0' }
Although the value of 'Key' should not contain this additional text, it was unexpected for TEST to return 'Compliant'.
It's possible a string is matching in an unexpected way?
2016
7.1 (guest config)
latest
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Details of the scenario you tried and the problem that is occurring
When testing, if the Key property contained 'HKEY_LOCAL_MACHINE' in the string, the resource always returned compliant.
RegistryPolicyFile 'AllowInputPersonalization' {
Ensure = 'Present'
Key = 'HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\InputPersonalization'
TargetType = 'ComputerConfiguration'
ValueName = 'AllowInputPersonalization'
ValueType = 'DWord'
ValueData = '0'
}
Although the value of 'Key' should not contain this additional text, it was unexpected for TEST to return 'Compliant'.
Suggested solution to the issue
It's possible a string is matching in an unexpected way?
The operating system the target node is running
2016
Version and build of PowerShell the target node is running
7.1 (guest config)
Version of the DSC module that was used
latest
The text was updated successfully, but these errors were encountered: