When troubleshooting Group Policy issues in your network, sometimes the only identifier you’re given is a GUID (Globally Unique Identifier). If you’ve ever run a gpupdate /force command, you might notice that the output shows the GUID of the failing Group Policy Object (GPO) rather than its name. As a system administrator, it’s important to know how to translate that GUID into something more meaningful—like the actual GPO name. Please see Create a web page to visualize the output of BitLocker Script, Unable to execute: The application GUID not found in the application list.
This guide will walk you through how to find the GPO name using its GUID in both PowerShell and the Group Policy Management Console (GPMC). We’ll also cover an alternative method using the gpresult command.
Here are other related guides How to Install Winget on Windows Server, Set Special File Permissions with SUID or GUID and Sticky Bit in Linux, and Prevent OS Reinstallation: Change from legacy BIOS to UEFI.
Step 1: Using PowerShell to Find GPO by GUID
PowerShell is a quick and efficient way to identify the GPO associated with a GUID. Here’s how you can use it:
Steps:
Launch PowerShell as an administrator on your Active Directory server.
Before running any Group Policy commands, make sure the Group Policy module is imported by typing:
Import-Module GroupPolicy
Use the following command to search for the GPO by GUID:
Get-GPO -Guid AEA1B4FA-97D1-45F2-A64C-4D69FFFD92C9 -Domain yourdomain.com
Replace AEA1B4FA-97D1-45F2-A64C-4D69FFFD92C9 with the GUID you are troubleshooting and yourdomain.com with your actual domain name.
You’ll get detailed information about the GPO, including its name, creation time, and status. This helps you easily identify the policy that needs attention.
Please see How to Install Group Policy Management Console on Windows 11, how to ” to Install Group Policy Management Console on Windows 11, and What is GPO and how can it be launched in Windows.
Step 2: Using Group Policy Management Console (GPMC) to Find GPO by GUID
PowerShell is great, but if you prefer a GUI, the Group Policy Management Console (GPMC) offers another method to find the GPO associated with a GUID.
Steps:
On your AD server or management workstation, press Windows + R to open the Run dialog.
Type gpmc.msc and hit Enter to open the Group Policy Management Console.
In GPMC, right-click on your domain name in the left-hand pane. Select Search from the context menu. This will open a search dialog box.
In the search dialog, choose GUID from the dropdown menu.
Copy and paste the GUID (including the {} brackets) of the GPO you are looking for into the search box, then click Add.
Click Search and wait for the search to complete.
The GPO with that GUID will appear in the search results, showing you the GPO name and other information.
Here is how to set up a Single App Kiosk Mode Configuration using MDM Bridge WMI Provider, and how to Configure Windows Device Inactivity Limit Locally and Domain Wide.
Step 3: Using gpresult to Find the GPO
You can also use the gpresult command to create a report that will help you identify the GPO causing the issue. This is useful if you want to see a broader report of applied policies.
Steps:
Open Command Prompt or PowerShell as an administrator.
Run the following command to generate an HTML report:
gpresult /H C:\path\to\report.html
Open the generated HTML report in a browser. Use the browser’s search function (Ctrl + F) to find the GUID or specific setting that’s causing issues.
In the report, you’ll find the name of the GPO linked to that GUID, as well as the winning policy setting.
Troubleshooting Tips
- Ensure Correct Domain: When using PowerShell or GPMC, make sure that you are connected to the correct domain where the policies are being applied.
- Permissions: You’ll need appropriate admin privileges to search for and view GPOs. Make sure you’re running the necessary tools with elevated permissions.
- Check GPO Status: If a GPO isn’t being applied correctly, it could be due to status issues. Review the policy settings to ensure it’s enabled and properly linked to the domain or OU (Organizational Unit).
Conclusion
Whether you prefer using PowerShell or the Group Policy Management Console, finding a GPO by its GUID is an essential skill for troubleshooting Group Policy issues.
These methods make it easy to quickly identify problematic policies, allowing you to resolve issues more efficiently.
Use the step-by-step instructions above to translate GUIDs into meaningful GPO names, and streamline your management tasks.
I hope you find this post helpful on how to Determine GPO from GUID or Name. If you have any questions, feel free to leave them in the comment section below.
