Windows Server 2016-graphical migration FSMO role

In the previous section we briefly introduced three different ways to view the FSMO host role information, before opening our brief review of the FSMO Five operations master roles: There are two types of forest-scoped operations master roles (schema master) and the domain naming master role Naming master) and domain-scoped operations master role three, respectively, the RID master role (RID Masters), PDC emulation master role (PDC Emulator), and infrastructure master role (Infrastructure Master) , either the forest-wide host role or the domain-scoped master role must be unique. This chapter and the following two chapters introduce three different ways of FSMO role migration method, I hope we can help everyone.

To view the operations master role:

1. View the current operations master role information by netdom query FSMO:

2. Migrating the Schema master role (schema Masters):

A. In the Run bar, enter: regsvr32 schmmgmt.dll and enter:

Prompt DllRegisterServer to register successfully.

B. Then open the MMC console to add the Active Directory schema;

C. In Active Directory schema, select the right-click Change Active Directory domain controller:

d. Select this domain controller or AD LDS instance, and in the list select the domain control spare.azureyun.local you want to switch to, you can enter the specified DC name when switching from the old version:

D. Tip the Active Directory Schema snap-in is not connected to the schema operations master. You will not be able to perform any changes. Schema modifications can only be made on the schema FSMO, click OK to continue:

E.active Directory schema Right-click on "Operations master":

F: Display, click on the "Change" button:

G: Prompt "Are you sure you want to change the operations master?" ", click" Yes "to continue:

H. Prompt to successfully transfer the operations master:

I. At this point we look at the schema host display information is spare.azureyun.local:

3. Change the domain naming operations master:

3.1. In Active Directory Domains and Trusts, right-select Change Active Directory domain controllers:

3.2. Select this domain controller or AD LDS instance, select the domain control spare.azureyun.local you want to switch to in the list, and click OK to continue:

3.3. Active directory Domains and Trusts right-click on "Operations master":

3.5. Display, click "Change" button to make domain naming operations master changes:

3.6. Tip "OK to transfer the operations master role to a different computer" and select "Yes" to continue:

3.7. Indicate that the operations master has been successfully transferred:

3.8. After the migration, the current domain naming operations master information is spare.azureyun.local:

4. change RID, PDC, infrastructure master:

4.1. Open "AD Users and Computers" right-click "Change Domain Controller" in "Azureyun.local":

4.2. Select "Spare.azureyun.local" and click "OK" to continue:

4.3. "Ad Users and Computers" right-select "Operations master" in "Azureyun.local"

4.4. Select "Change" in the RID interface, according to the prompt "You are sure you want to transfer the operations master role" select "Yes" for the RID master role migration:

4.5. The Operation master role was successfully routed:

4.6. View the RID master at this time as Spare.azureyun.local:

4.7. Switch to the PDC interface tick the change to make the current PDC role migration, and then select Yes if prompted:

4.8. The Operation master role was successfully routed:

4.9. The PDC role is Spare.azureyun.local at this point:

4.10. Switch to the infrastructure interface, select "Change" for the role migration, and select Yes to perform the operations master role migration as prompted:

4.11. When prompted to successfully transfer the operations master role, click OK to continue:

4.12. View current infrastructure host information displays "Spare.azureyun.local":

5. After all operations are completed, we query the current FSMO role information to be Spare.azureyun.local and the migration is successful.

With the completion of the FSMO role migration through the graphical interface, we will find that the graphical interface is cumbersome to operate, and the next two chapters will introduce the migration of FSMO role content through the command line. Thank you for your support.

Windows Server 2016-graphical migration FSMO role