This message was deleted.
# _general
s
This message was deleted.
j
Depends how they are doing the filtering I think (although am not an expert). I think the policy applies at a Security Filter level and then the WMI filter denies it
r
WMI filtering on the root domain sounds fun
👍 1
m
What I’m worried about is that because every policy is at the root level even if it’s not enforced and they block inheritence it still show up in the applied list
so it’s taking time to process even when the settings are being denied
j
Yeah seems really stupid
m
I really just want to build a new domain at this point
some people who are in 40 AD groups have logons of 400 seconds or more
because they also have loopback merge
j
Oof
r
oh my
Seeing a bunch of "enforced" ones too?
m
no, hardly anything is enforced, that’s the insane thing
it’s all just dumped at the root level and then blocked lower down
well, 3 things are enforced, one of them being logon scripts…
k
Why do people do stuff like that?
m
it looks like all the logon scripts are applying even from policies that aren’t enforced
I’m not sure if that’s normal for stuff applied at the root level because literally nobody else does it this way and I’ve never seen it before
k
I have seen it plenty of times here in DK. It's like some people don't understand how GPOs work which is a bit scary since they have been around for more than 20 years
r
yep that would be normal with the login scripts applying
There should be next to no policies at the root outside maybe a domain password pol
k
Totally agree
r
I have had customers do this as well and always painful. The next step I see admins do outside of fixing the problem is create OUs with "block inheritance" and reapply the policies they need
So you end up with a bunch of OUs with fed up policies vs just fixing it at the beginning
k
Yep, seen that too. I have also seen that loopback processing has been enabled in every single GPO configured on the terminal server OU, because someone thought it was a requirement
😀 1
r
WMI filtering is garbage and will cause even more processing issues. That's the whole reason for OUs
m
I just want to build them a new domain at this point
😮 1
it has WMI filtering, logon scripts, loopback merge, blocked inheritance and relinking, and 100 GPOs at the root level 1/3 of which are marked as inaccessible
😮 2
j
Run GPOZaurr on it and see how the reports look
m
I’ve not used that before, I take it it’s good?
j
Someone here recommended it to me, pumps out a huge HTML file full of GPO data with options to export reports and recommendations - I'm sold https://github.com/EvotecIT/GPOZaurr
m
nice
there’s a lot of red in these reports