Skip to content
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

Conflicting settings (reg value) between DotNetFramework and InternetExplorer #1270

Closed
ImperatorRuscal opened this issue Oct 26, 2023 · 1 comment

Comments

@ImperatorRuscal
Copy link

ImperatorRuscal commented Oct 26, 2023

A setting is present in both DotNetFramework (V-225224) and InternetExplorer (V-223016), and by the textual description both should use the same value (0x23c00). But if you include both in your configuration you will get a DSC conflict warning -- apparently there is a discrepancy in the setting between the two modules. This will cause DSC audit to stop.

WARNING: The resources ('[RegistryPolicyFile][V-225224][medium][SRG-APP-000175]::[DotNetFramework]BaseLine' and '[RegistryPolicyFile][V-223016][low][SRG-APP-000175]::[InternetExplorer]BaseLine') have conflicting values of the following properties: 'ValueData'. Ensure that their values match

I attempted to put in a local org setting override to get around the issue, and it didn't work (same presentation). I'm assuming this means that there is a difference in how the two XML points are transposed into MOF definitions.

org setting for IE
<OrganizationalSettings fullversion="2.2"> <OrganizationalSetting id="V-223016" ValueData="0x23c00" /> </OrganizationalSettings>

and DotNet
<OrganizationalSettings fullversion="2.2"> <OrganizationalSetting id="V-225224" ValueData="0x23c00" /> </OrganizationalSettings>

@erjenkin
Copy link
Contributor

Hello @ImperatorRuscal,

This is interesting. The two Rules have different instructions for values to fix the finding ( 0x23C00 vs 23C00), PowerSTIG is setting it to be a DWORD - 146432 in both cases (not sure the logic here). In the case where two different DSC modules are trying to modify/control the drift on the same value, I would skip one of them in your configuration.

This will get you past the conflict message:

SkipRule = "V-223016"

Please let me know if you have any questions.

Eric

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants