-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
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
WindowsEventLog: Add parameter to set RestrictGuestAccess registry key #338
Comments
To confirm, the proposal would result in the MOF changing like this:
Setting a value of This should be easy enough, although would need to ensure the appropriate registry path exists (which is what the Registry resource takes care of). |
Confirmed: that's exactly what I'm looking for |
Working on other updates to this resource. Will update as part of the PR with the other issues. |
Details of the scenario you tried and the problem that is occurring
Add a parameter to set the "RestrictGuestAccess" registry value for Windows Event Logs
Verbose logs showing the problem
N/A
Suggested solution to the issue
Add RestrictGuestAccess to WindowsEventLog so it can be set within the resource and not separately using the Registry resource
The DSC configuration that is used to reproduce the issue (as detailed as possible)
The operating system the target node is running
Server versions 2008/R2, 2012/R2, 2016, and 2019
Version and build of PowerShell the target node is running
WMF 5.1
Version of the DSC module that was used ('dev' if using current dev branch)
8.2.0.0
The text was updated successfully, but these errors were encountered: