However, DFS replication for SYSVOL must be used between DCs for the SYSVOL folder to be included in the IFM media. The SYSVOL folder can also be included in the installation media. The installation media for an RODC can be created on either a writable domain controller or another RODC. When you use IFM to make the installation media for an RODC, it removes cached passwords. It offers additional security and performance benefits, such as storing account credentials only of users who hit the RODC for authentication. In remote locations, installing a read-only domain controller (RODC) is the preferred option. To perform a nonauthoritative restore of AD DS and authoritative restore of SYSVOL using wbadmin.Install secondary DC from media on Server 2019/2022 For more information about creating a system state backup, see Backing up the System State data. The backup must explicitly include system state data a full server backup that is used for full server recovery will not work. Use the following procedure to perform a nonauthoritative restore of AD DS and an authoritative restore of SYSVOL at the same time by using wbadmin.exe on a DC that runs Windows Server 2012, Windows Server 2008 R2, or Windows Server 2008.
If you are using File Replication Service (FRS) to replicate SYSVOL, follow the steps in article 290762 in the Microsoft Knowledge Base, using the BurFlags registry key to reinitialize FRS replica sets, or if necessary, article 315457 315457to rebuild the SYSVOL tree.If you are using a different backup solution or if you intend to complete the authoritative restore of SYSVOL later in the forest recovery process, you can perform an authoritative restore of SYSVOL by using these alternative methods: The following procedures use the Wbadmin.exe to perform a nonauthoritative restore of Active Directory or Active Directory Domain Services (AD DS). To perform a nonauthoritative restore, complete the following procedure. Performing a nonauthoritative restore of Active Directory Domain ServicesĪpplies to: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 20 R2, Windows Server 20 R2
0 kommentar(er)
