The nonauthoritative restore is the most common way to reinitialize SYSVOL replication on individual domain controllers. Domain controllers that are nonauthoritatively restored must have inbound connections from other working domain controllers, which are participating in Active Directory and FRS replication.
In a large deployment environment consisting of many domain controllers, the remaining domain controllers can be recovered using a nonauthoritative mode restore under the following conditions:. Event is logged in the FRS event log to signal that a nonauthoritative restore has started. The member performs an initial join of the replica set from an upstream partner or from the computer that is specified in the Replica Set Parent registry key if a parent has been specified for SYSVOL replica sets.
The reinitialized computer runs a full replication of the affected replica sets when the relevant replication schedule begins. When the process is complete, an event is logged to signal that FRS is operational. If the event is not logged, there is a problem with the FRS configuration.
The placement of files in the pre-existing folder on reinitialized members is a safeguard in FRS that is designed to prevent accidental data loss. Any files destined for the replica that exist only in the local pre-existing folder and were replicated after the initial replication may then be copied to the appropriate folder.
When outbound replication has occurred, files in the pre-existing folder can be deleted to free additional drive space. Authoritative restores are used as a last resort in case of critical situations such as divergence of data on the content set caused by directory collisions.
For example, an authoritative restore might be needed to restore an FRS replica set where replication has completely stopped and a rebuild from scratch is required. The FRS service must be disabled on all downstream replication partners direct and transitive for the reinitialized SYSVOL folder before the authoritative restore has been configured to occur. Events and have been logged in the FRS event log. These events indicate that the membership of the SYSVOL replica set has been established on the domain controller that is configured for the authoritative restore.
PathPing works like ping except it echo-locates for 25 seconds and reports the percentage of lost packets. As a bonus, PathPing shows you the hops rather like a tracert printout. These ten command line tools have served me well down the years, please send me your collection. SolarWinds have produced three Active Directory add-ons.
These free utilities have been approved by Microsoft, and will help to manage your domain by:. These free utilities have been approved by Microsoft, and will help to manage your domain by: Seeking and zapping unwanted user accounts. Finding inactive computers. Bulk-importing new users. About The Author Guy Thomas.
Related Posts. Select Clear to bring the attribute to the Edit Attribute line. You can then use the Robust File Copy utility to copy the Administrative Template folders back to the guid folders if you want. Technically, if you don't have any custom Administrative Templates, you don't have to add the Administrative Template folders back to the PDC emulator. The folders will be automatically regenerated by using the local Administrative Templates whenever someone edits the Group Policy object GPO.
For best results, use the Robust File Copy utility. If you have custom Administrative Templates, make sure they have unique file names across policies. Unless you have specific Administrative Template requirements for example, you use certain Administrative Templates only for certain policies , a good idea is to combine these approaches to have a complete set of Administrative Templates for editing a GPO.
Skip to main content. This browser is no longer supported. Download Microsoft Edge More info.
0コメント