How to force an authoritative and non-authoritative ...
support.microsoft.com › en-us › topicIf setting the authoritative flag on one DC, you must non-authoritatively synchronizeall other DCs in the domain. Otherwise you will see conflicts on DCs, originating from any DCs where you did not set auth/non-auth and restarted the DFSR service.For example, if all logon scripts were accidentally deleted and a manual copy of them was placed back on the PDC Emulator role holder, making that server authoritative and all other servers non-authoritative would guarantee success and prevent ...
KB2119: Restoring Domain Controller from an Application ...
https://www.veeam.com/kb211904.04.2016 · After restoring a Domain Controller, the automatic recovery process performs a non-authoritative restore, causing the Domain Controller to begin seeking replication partners. However, in a scenario where all Domain Controllers are lost, and there are no partners available, replication may take quite a long time to start (e.g., 15-30 minutes).
How to recover a Domain Controller (DC) - Best practices for ...
www.veeam.com › blog › how-to-recover-a-domainMay 16, 2016 · Performing a restore of a Domain Controller in non-authoritative mode. Whenever you’re about to restore a DC, first determine whether a non-authoritative restore is enough, or if should you go further and perform an authoritative restore. The difference between those two restore types is that within a non-authoritative restore, the DC understands that it was out for a while, so it lets other in site DCs update its own database with the latest changes that occurred when it was down.