Skip to content

New Query - All GPOs applied to a specific computer.yml #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Oct 14, 2025
Merged

New Query - All GPOs applied to a specific computer.yml #33

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0db8d38
Create All GPOs applied to a specific computer.yml
auk0x01 Oct 9, 2025
ee40258
Update All GPOs applied to a specific computer.yml
martinsohn Oct 9, 2025
083b38a
Update All GPOs applied to a specific computer.yml
martinsohn Oct 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions queries/All GPOs applied to a specific computer.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
name: All GPOs applied to a specific Computer
guid: 1d75a21e-0d34-40c5-9360-281b60737d87
prebuilt: false
platform: Active Directory
category: Domain Information
description: View all GPOs that are applied to any specific computer. This query identifies GPOs that are applied at both the Domain Level and the OU level, saving time in large Active Directory environments where GPO inheritance is complex. Replace "COMPUTER_NAME" with the target computer name or a substring. Note this does not take OU 'Block inheritance' and GPO 'No Override' into account.
query: |-
MATCH p=(c:Computer)<-[:Contains*..]-(:OU)<-[:GPLink]-(:GPO)
WHERE c.name CONTAINS "COMPUTER_NAME"
RETURN p
revision: 1
resources:
- https://learn.microsoft.com/en-us/previous-versions/windows/desktop/Policy/overriding-and-blocking-group-policy
acknowledgements: Adnan Ullah Khan, @auk0x01
Loading