okay, so i have 2 domain controllers in my domain. lets call them DC “S” and DC “V” for simplicity. Both are VMs and the each reside in different sites/campuses. If i make a change to group policy and perform a gpupdate /force DC “V” works as expected but DC “S” does not apply the new settings.If i check the event viewer it states that new policies have been detected and applied after every gpupdate but gpresult does not show the new policies. however, i’ve noticed, after a few hours, policies will finally update themselves. Even if i remove the setings or delete the GPO link DC “S” does not make the changes.
I’m at a loss here and am not sure how to troubleshoot this any further. Any tips or info will be greatly appreciated.
2 Spice ups
justin1250
(Justin1250)
2
How fast is the link?
Have you made any modifications to slow link detection?
gpresult states a fastlink is detected. funny thing is DC “V” is on the other side of a 60Mbps point to point radio where as DC “S” is on a mostly 1Gbps site.
justin1250
(Justin1250)
4
Is V the pdce role holder? If so any gpo changes would originate there. Not sure why S is lagging like that
Does dcdiag report any errors?
ya, “V” actually hold all the FSMO roles. I need to work on getting some moved to “S”. dcdiag without any switches passes all tests. it does mention errors in the event log: There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems.
justin1250
(Justin1250)
6
Do you know if sysvol is replicating with dfs or frs?
im not 100% sure but i assume frs. Domain functional level is currently at 2003 if that helps.
justin1250
(Justin1250)
8
Yeah it’s frs then. Dfs you need function level of 2008. What frs errors are in the event log?
give me a bit. currently racking up the hyper v host
No errors, just warnings about write cache being enabled. Also a warning with ID 13565 about initializing sysvol. But that was around the time I spun up the machine.
Still wondering what might cause gpupdate not to work even though the system will update policy on it’s own sometime later.