tried this for now on defected DC. should i wait for some time and check
is there anyway to check and confirm - AD replcation reporting shows no errors so far
https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/ad-forest-recovery-authoritative-recovery-sysvol
after moving FISMO roles to 2016 AD i can edit the GPs only from there and all other DCs have that dimmed
after moving FISMO roles to 2016 AD i can edit the GPs only from there and all other DCs have that dimmed
i have 2 sites - each one has 2016X1 and 2019X1 DC - total 4 DCs physical sites are separated by MPLS
i moved all FISMO to the site hosting my exchange servers thinking this is a better approach - all good except that when i try to edit any group policy on any DC that is dimmed - disabled - the only server i can edit from is the FSMO owner, ran Dcdiag and it seems i have time issue NTDS - i have configured public time servers on the FSMO and left the others to default - expecting they should take form that guy
any idea why i am not able to edit the GPOs from any DC except the FSMO holder?
7 answers
Sort by: Most helpful
-
Maher Ramadan 286 Reputation points
2020-09-18T17:38:13.06+00:00 -
Maher Ramadan 286 Reputation points
2020-10-04T17:06:53.663+00:00 it seams to be a major issue, something related to the domain admins group perhaps ! and domain admin member now is getting restrictions performing various tasks
for example now i am creating a new ADFS farm and i get permissions issue even though the only requirements is domain admin group and i have tried the default admin account and my admin account with no luck! the question is, is there a way to check default domain admin accounts group settings and revert to that,
did anyone face this before? could it be a group policy issue and how to confirm on that