User Profile
AaronMargosis_Tanium
Iron Contributor
Joined 6 years ago
User Widgets
Recent Discussions
Re: Microsoft Policy Analyzer 4.0 crashes after apply April updates
My apologies for the bug leading to a crash rather than displaying a warning. Also my apologies for having to post the answer as a screenshot: the techcommunity platform seems to have some unnecessarily aggressive filtering that deletes comments that it shouldn't.539Views0likes0CommentsRe: Microsoft Policy Analyzer 4.0 crashes after apply April updates
The problem is that with the April 8 2025 updates Microsoft added a new Advanced Auditing subcategory and mistakenly assigned it the same GUID that is already assigned to another subcategory. That's a bug in Windows -- those GUIDs need to be unique to configure auditing. The bug in Policy Analyzer appears to be that it assumes there are no duplicates and fails to check for them (which it had never needed to before). The new Advanced Auditing subcategory is represented in the registry key, HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Audit\SystemPolicy\LogonLogoff\AccessRights. On a US-English system, it is called "Audit Access Rights" in the "Logon/Logoff" category. In the registry it has the same GUID as "Audit Token Right Adjusted" under "Detailed Tracking." Microsoft updated the Windows Update packages on April 11 for some OSes, including Win11 23H2/24H2, Win11 LTSC 2024, WS2025, and Azure Stack HCI 22H2, so that applying WU after that date resolves the issue. (As far as I can tell, the mistake was never applied to Win10 22H2.) For many other supported OSes, including WS2022, WS2019, WS2016, Win10 LTSC 2019, Win10 LTSC 2016, fixing the issue requires finding, downloading, and installing an OS-specific out-of-band update from the Microsoft Update Catalog website. One of the outcomes of applying the fix is that the "Access Rights" subcategory and the AccessRights registry key is removed.424Views0likes0CommentsRe: Microsoft Policy Analyzer 4.0 crashes after apply April updates
I was out for a couple of days -- just now was my first opportunity to test. I updated my standalone Win11 24H2 VM with the latest WU updates and then tested Policy Analyzer a number of ways. Could not reproduce a crash. Did Microsoft fix the patch and reissue it?646Views0likes2CommentsRe: Microsoft Policy Analyzer 4.0 crashes after apply April updates
What operating system are you seeing this happening on, and do you have any particular security baselines applied? [edit] Also, when did the error occur? Right when starting Policy Analyzer, or when trying to perform a specific operation?797Views0likes5CommentsRe: Confusing Naming of Intune M365 Apps Baseline
Office used to have separate GPOs for different Office versions, with the settings persisted in different registry keys. After publishing the 2016 GPOs, they decided to stop doing that and just to continue using the "2016" GPO folder names and the "2016" registry keys for all future Office versions. These are the correct ones for managing your Office apps today.152Views1like0CommentsRe: How to Use Baselines Correctly as a Beginner
The SCT baselines don't provide a means to undo the application of a baseline. Some of the settings are "tattooed" so it's not entirely possible to revert completely to the original state. The purpose of the "Remove-EPBaselineSettings.ps1" script was to TRY to restore default settings for Exploit Protection settings that had been included in a baseline from several years ago. If experimenting, consider using virtual machines with snapshots that can be reverted. For the Policy Analyzer questions, see the documentation ("Policy Analyzer.pdf") that's included with the tool. Note that it does not ingest Excel files.268Views0likes0CommentsRe: Applying the SCT to standalone hardened systems?
The ADMX/ADML files are useful if you want to see or edit the settings in the Group Policy editor. If you're applying settings using a tool such as LGPO.exe and a GPO backup, the ADMX/ADML files don't need to be present on the endpoint.830Views0likes0CommentsRe: Question Regarding Server 2022 Domain & Controller MSCT baselines
katPedraza-- I think you're mistaken about that. The SCT's baselines for DCs have many settings that intentionally override the "Default Domain Controllers Policy" that ships in Windows and that is created automatically on DCs. Just as a couple of examples, the baselines' SeBackupPrivilege and SeRestorePrivilege user rights assignments intentionally override the default and grant the privilege only to Administrators. (Also, you accidentally marked criiser's question as the "Microsoft Verified Best Answer."))963Views0likes0CommentsRe: Policy Analyzer - Compare all settings
What you need to do is to merge the Policy Analyzer results (each .PolicyRules file is just an XML document) with a full listing of all available GPO settings. I don't know of any publicly available tools to get all those in an XML, but perhaps you could do something with the Excel spreadsheet that ships with the baselines that lists all the settings.15KViews0likes0Comments
Recent Blog Articles
No content to show