-
Notifications
You must be signed in to change notification settings - Fork 18
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.
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
Improve GPO Table(s) #128
Comments
If I understood correctly,
Regards, |
Correct. Thank you |
rebelinux
added a commit
to rebelinux/AsBuiltReport.Microsoft.AD
that referenced
this issue
Jul 15, 2023
rebelinux
added a commit
to rebelinux/AsBuiltReport.Microsoft.AD
that referenced
this issue
Jul 15, 2023
rebelinux
added a commit
to rebelinux/AsBuiltReport.Microsoft.AD
that referenced
this issue
Jul 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Currently, it's only possible to see if a GPO is linked by looking at the OU table. It would be great if any of the Informational levels (1-3) added a column (info 1) or row (info 2-3) for the linkage.
Here is an example of info 3:
I would be great if the linkage could be added as a row here. In info 1, it would be a 4th column.
At minimum, it would we need a count of the number of targets the GPO is linked to (or a boolean:
if ($count -eq 0) ...
. This is accomplished with something like this:The above is a quick and dirty example, but it gets the point across.
We could expand on this for info 2-3. When this info level is used, each individual table for each GPO would include the actual targets, not just the count (or boolean).
Additional Context
No response
Before submitting
The text was updated successfully, but these errors were encountered: