The Group Policy Management Console XML and HTML reports missing information due to limitations in the GPMC

The Group Policy Management console (GPMC) in Active Directory has a nice feature which allows you to generate reports in HTML and XML format of the settings in the Group Policy Object.



The report is actually generated by the GPMC itself rather than the domain controller the tool is running against. This is somewhat problematic due to possible version differences between the tool and the Group Policy object settings.

Also the report only contains as much information as the tool can interpret - whilst the coverage is generally very good Microsoft seem to have become complacent in later versions of Windows where new settings have been added to Group Policy but the GPMC has not been updated to convert these into the settings in the HTML and XML reports. 

This is actually highlighted in the Windows Defender Firewall section where you may see the following:

This rule might contain some elements that cannot be interpreted by the current version of GPMC reporting module


Group Policy stores information in a variety of places including a binary registry.pol file, XML files (for Group Policy preferences), .ini files. It's a bit of a mess. The GPMC reports aggregate all of this information into a single report.


For the Windows Defender Firewall the rules are actually stored in the Registry.pol file. You can view this file with the Get-GPRegistryValue cmdlet or there is a nice GUI tool available here.

https://sdmsoftware.com/general-stuff/registry-policy-viewer-1-5/

You can see that the Windows Defender Firewall rule is actually stored in Group Policy as a String delimited by the | character and the GPMC just ignores the parameters it hasn't been coded to interpret.


The items that aren't interpreted by even the latest GPMC on Windows Server 2022 include the following:

  • Rule application packages
  • Rule compartments
  • Edge Traversal > Defer to user
  • Edge Traversal > Defer to application
  • Local Principals Tab
  • Allow the computers to dynamically negotiate encryption
  • IP Sec integrity algorithms aren’t all supported
  • Key Exchange Algorithms aren’t all supported – Diffe-Hellman Group 24 defaults to a different key exchange.
  • Most of the identity algorithms are  not supported.
  • Many of the newer encryption algorithms are not supported.
  • The advanced settings of the authentication method are not displayed at all.


 While you're here -
Why not check out our Group Policy Audit and Documentation Tool?



Comments

Post a Comment

Popular posts from this blog

Windows Server 2016, 2019, 2022, Windows 10 and Windows 11: Date and time "Some settings are managed by your organization".

Image
When you're using the new "Modern" date and time settings in Windows Server 2016, 2019, 2022, Windows 10 and Windows 11 you may find that you can't set the correct date and time and the value "Some settings are managed by your organization". - While you're here - Why not check out our Windows Server Documentation and Audit Tool? The simplest way around this is to go back to the proper control panel using Start, Run, "Control.exe" and searching for "Set the date".  Within here you can set the date and time manually as required If you try and click the Change time zone button you may again get access denied... To resolve this open an elevated command prompt by right clicking the command prompt and selecting Run as Administrator  From there run the command rundll32.exe shell32.dll,Control_RunDLL timedate.cpl This will open the Data and Time control panel app elevated as an Administrator.
Read more

TFTPD32 or TFTPD64 reports Bind error 10013 An attempt was made to access a socket in a way forbidden by its access permissions.

Image
When you start the trivial FTP (TFTP) server application TFTPD32 or TDTPD64 you may see the following error Bind error 10013 An attempt was made to access a socket in a way forbidden by its access permissions. This can be because another application is using this port. The easiest way to check if (and which) application is using the port is as administrator run an elevated command prompt and enter netstat -anb > ports.txt Then open ports.txt in Notepad and search for :69, you'll quickly be able to see the process using the required port - While you're here - Why not check out our Windows Server Documentation and Audit Tool?
Read more

Windows Server 2019 desktop icons such as My Computer, Windows cannot access the specified device, path, or file.

Image
In Windows Server 2019 you may notice that the desktop icons such as My Computer are missing, however when you goto Personalization > Themes > Desktop icon settings You see the error Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item. The quickest way to resolve this is to ignore the modern UI and desk.cpl ,5 From here you can easily add the My Computer icon - While you're here - Why not check out our Windows Server Documentation and Audit Tool?
Read more