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
When adding HardCodeRules to SQL Server Instance 2.5 STIG and generating a new PowerStig Xml, the resulting Xml lacks the Name entries for V-213954 (all 4 split rules).
By default the following sample databases are in each sub rule Name entry:
Upon regenerating the PowerStig Xml with the ConvertTo-PowerStigXml, the Name entries are blank ( <Name /> ) resulting in an exception when trying to compile.
The issue is easily remediated by entering the Name entries back into the xml.
The text was updated successfully, but these errors were encountered:
This was due to a variable not clearing out during multiple converts within the same PowerShell session. Workaround would be to do as you did or start a new PowerShell session for the next convert.
The fix has been added to #1027. Should be available in the next version.
When adding HardCodeRules to SQL Server Instance 2.5 STIG and generating a new PowerStig Xml, the resulting Xml lacks the Name entries for V-213954 (all 4 split rules).
By default the following sample databases are in each sub rule Name entry:
Upon regenerating the PowerStig Xml with the ConvertTo-PowerStigXml, the Name entries are blank (
<Name />
) resulting in an exception when trying to compile.The issue is easily remediated by entering the Name entries back into the xml.
The text was updated successfully, but these errors were encountered: