Add support to full path of OU within AD infrastructure + option to specify OU to analyze GPOs in (with or without recurse) #16
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…oname to fit XML naming
… without recurse)
Fist0urs
changed the title
Owner
|
i'm super busy atm with work but i will have a look at this asap, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
thank you very much for this tool that gives a good basis while analyzing GPOs!
This PR adds the display of the full path of an OU while treating GPOs. Indeed different OUs may have the same name while being located in another location within the AD infrastructure. The variable name was also changed to follow the naming "SOMName" and "SOMPath" of the Get-GPORerport produced XML.
Furthermore the 2nd commit adds the option to specify an OU to analyze GPOs in (with or without recurse). This can be interesting while trying to debug specific GPOs in OUs (like parameter override or inheritance blocked) ;-).
Please note that I'm a not (yet) a PowerShell guy so feel free to give me some feedback regarding implementation :-).
This last feature has been tested only with the "WithFile" option, thus Domain and WithoutFile is not included in this PR.
Cheers!