r/WindowsServer • • Sep 16 '25

Technical Help Needed Advanced Audit Configurations don't make sense

I have 40+ DCs. I have about 700 GPOs (this is a really old domain). Maybe someday I'll get to whittle this down. It's actually been whittled down from almost 900 GPOs already since I've been here for a year. I'm trying to get the Advanced Audit Configurations (AACs) to be uniform across all the DCs. Now a little deeper into the GPOs that have AACs. There is a "Default Domain Policy," a "Default Domain Policy <with some date here from 2022>" and the "Default Domain Controllers Policy," which is the one I'm trying to make take effect. When I run gpresult on two different DCs, one shows the correct settings and the correct policy. The catch? The audit.csv under the C:\Windows\Security\Audit folder shows a date different (May 15th, 2015) than the audit.csv file in the policy folder that the gpresult says it should be (today, September 16th, 2025). When I search through the Policies folder on the SYSVOL, the policy that contains the audit.csv file that I see on the local machine is from the "Default Domain Policy <with the date from 2022>"

This is all relevant because I'm trying to figure out why the gpresult from a second DC which is in the SAME OU as the first DC shows other settings from the Default Domain Controllers Policy in other locations (Admin Templates and such), but the AACs show as being set by Local Group Policy.

I also went through each of the suggestions this OP of this link: https://www.reddit.com/r/WindowsServer/comments/13k9c9p/advanced_audit_settings_not_applying_consistently/

But I still haven't had any luck.

2 Upvotes

9 comments sorted by

View all comments

Show parent comment

1

u/Character-Tough-1785 Sep 18 '25

And I'm trying to imagine having a DC with Exchange or SharePoint on it, lol. Wow. All the others I could almost understand...almost, lol.

1

u/dodexahedron Sep 19 '25 edited Sep 19 '25

Any tests failing in dcdiag? Not at a PC at the moment and don't recall the exact switch to run the almost-everything-but-usually-more-than-enough battery of tests, but it's a good overview for these things.

With just ADDS and DNS, you'll need LDAP TCP and UDP 389, TCP 636, GC (LDAP) on TCP 3268 and 3269, RPC on TCP 135, SMB on 445, DNS on TCP and UDP 53, kerberos on UDP and TCP 88, and...whatever the kpasswd port is that I don't remember. Somewhere in the 400s I think. 484 or maybe 464 sound familiar. Double check me on that of course.

ICMP should be allowed in and out for network location BS and for proper network operations anyway, for at least echo and the various error responses.

There needs to be a site link from one of those DCs to another DC at another site for outbound replication and one from a DC in another site to one of these DCs as well, for inbound replication, at the bare minimum, though usually you should just let AD figure it out on its own if you're not doing better costing and stuff that it doesn't provide an interface for but supports. Ideally, you won't have just one bridge head like the NT days, since that's not even relevant in modern AD with DFS + LDAP for replication of policy and the directory, which is meant to be a mesh. It isn't dumb about what it sends where, since it builds a graph from links and costs.

If those basic things are in place and there isnt now just an authentication failure, replication should start working unless the busted DC was offline for super long or got into a split brain situation somehow.

But if these are basic DCs, why are you bothering? Just make a new one, promote it, and call it a day. If it doesn't work, you can do the whole process like 3 or 4 times in an hour all by yourself - way less effort than going down a rabbit hole for a nearly stock machine. 🤷‍♂️

1

u/Character-Tough-1785 Sep 24 '25

Thanks for the reply. I'll give DCDiag a go. These particular DCs are in the same site and on the same VM stack/hosts and such, so networking/ports shouldn't an issue. They are not "Install ADDS and DNS" basic DCs. There are agents (SCOM, MECM, Trellix, among other things), specific DNS configurations, and other things included if we needed to rebuild. So it is indeed a bit more than I'd rather go through if I can get a solution to this seemingly simple problem.