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
Describe the bug
Attempting to run the rules for V-63373 on Windows 10 brings up the following errors in the job:
Exception calling "RemoveAccessRuleAll" with "1" argument(s): "Some or all identity references could not be
translated."
+ CategoryInfo : NotSpecified: (:) [], CimException
+ FullyQualifiedErrorId : IdentityNotMappedException
+ PSComputerName : Win10Test
To Reproduce
Create a small mof with the 63373.a rules only and attempt to apply it to a system.
Expected behavior
Completed jobs and ACE's applied to the system drive. As of right now, jt is attempting to apply to %SystemDrive%. This corresponds to C: on most systems which does not interpret correctly in PowerShell. Inside the mof, it should be %SystemDrive%\ in order to properly label it as the root of the C drive. The Server 2012 STIGs properly adds the escaped backslash to the mof.
The text was updated successfully, but these errors were encountered:
Describe the bug
Attempting to run the rules for V-63373 on Windows 10 brings up the following errors in the job:
Exception calling "RemoveAccessRuleAll" with "1" argument(s): "Some or all identity references could not be
translated."
+ CategoryInfo : NotSpecified: (:) [], CimException
+ FullyQualifiedErrorId : IdentityNotMappedException
+ PSComputerName : Win10Test
To Reproduce
Create a small mof with the 63373.a rules only and attempt to apply it to a system.
Expected behavior
Completed jobs and ACE's applied to the system drive. As of right now, jt is attempting to apply to %SystemDrive%. This corresponds to C: on most systems which does not interpret correctly in PowerShell. Inside the mof, it should be %SystemDrive%\ in order to properly label it as the root of the C drive. The Server 2012 STIGs properly adds the escaped backslash to the mof.
The text was updated successfully, but these errors were encountered: