Shulou(Shulou.com)06/03 Report--

In order to achieve faster migration performance and better AD performance-I can use the Repadmin.exe / syncall command to force refresh domain replication and update older windows Server OS system patches, of course, these actions are optional and we can choose according to the customer's actual situation. DFSR migration is just like AD synchronous replication and usually does not take a long time.

This command forces all partitions to be pushed for replication:

Repadmin / syncall / force / Aped

In addition, between AD domain controls, the default DFSR SYSVOL is replicated by default (5 minutes). If you want to increase the speed of DFSR replication, create links to AD sites for continuous replication

Use Dfsrdiag.exe Cmd or Update-DfsrConfigurationFromAD PowerShell cmdlet to speed up update synchronization

Get-ADDomainController-Server corp.***.com-Filter * |% {Update-DfsrConfigurationFromAD-ComputerName $_ .name-Verbose}

It is highly recommended to run repadmin forced synchronization and dfsrdiag forced polling after each migration step, which will greatly speed up the processing of synchronization.

Quick Migration

As described in the previous article, the running state of both AD and SYSVOL on domain controllers for this case is unknown.

1. Ensure free disk space

Using Psinfo.exe-d, you can easily determine the available disk space on the DC domain control.

Get-WmiObject-Class win32_logicaldisk-ComputerName srv01,srv02,srv03 # # multiple Server | FTsystemname,deviceid,freespace-auto

two。 Ensure the correct security policy

You must ensure that the built-in administrators group has the manage Audit and Security Log user right on all domain controllers. Enabled by default, if it is not set, we need to configure it correctly. Verify the group policy applied to the domain controller through Gpresult.exe inspection.

3. Ensure that AD replication is normal

DFSR migration depends entirely on each domain controller receiving and sending state changes through AD replication. There are many ways to check the health of AD, but the easiest way is probably the repadmin command or the Active Directory replication status tool (Active Directory Replication Status Tool).

4. Ensure SYSVOL file sharing

DFSR migration depends on the fact that the SYSVOL itself must be shared, and the easiest way to check all domain controllers is to use the Dcdiag.exe command:

5. Migration preparation phase

Dfsrmig / setglobalstate 1

Now you need to wait for the AD value to be synchronized to all domain controllers on PDC, then let DFSR switch to the Prepared status on each domain controller and update AD, and finally copy the value back to PDC. Use the following command to view progress:

Dfsrmig / getmigrationstate

When all the DC is ready, the output is as follows:

6. Migration redirection phase

You will now migrate to the redirected state, where both FRS and DFSR are replicating their own SYSVOL replicas, but DFSR replicas install SYSVOL and Netlogon shares.

Dfsrmig / setglobalstate 2

Get migration progress

Dfsrmig / getmigrationstate

7. Migrate Eliminated Pha

Finally, you will migrate to the Eliminated state, where DFSR is replicating SYSVOL and deleting FRS.

Dfsrmig / setglobalstate 3

Now, wait for this AD value on PDC to be synchronized to all domain controllers, then have DFSR switch to each domain controller and update AD, and finally copy the value back to PDC. Use the following command to check progress

Dfsrmig / getmigrationstate

When all the DC is ready, the output will look like this:

Migration completed

Note:

For the migration steps of "Express Migration" and "Hyper Migration", please refer to the "Quick Migration" example.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.