In this hands-on lab, you will learn how to identify Flexible Single Master Operations (FSMO) roles using PowerShell, how to move operations roles between domain controllers, and how to seize an operations role.
Learning Objectives
Successfully complete this lab by achieving the following learning objectives:
- Locate the Flexible Single Master Operations Roles
- Determine the domain of the
main-vm
using SConfig. - Locate the FSMO roles using netdom.
- Locate the FSMO roles using PowerShell.
- Identify the domain-level operations master using PowerShell.
- Determine the domain of the
- Locate the FSMO Roles Using Graphic Administrative Tools
Next, we will identify the FSMO roles using Graphic Administrative Tools. In addition to validating this skill, we will prepare the environment for the third objective, where we will begin moving FMSO roles from
main-vm
tonew-vm
:- Identify the domain naming master.
- Identify the schema master.
- View the domain-level operations masters.
- Move the Infrastructure Master
- Move the infrastructure master (located on
main-vm
) tonew-vm
. - Move the PDC emulator to the
new-vm
domain controller using PowerShell.
- Move the infrastructure master (located on
- Seize FSMO Roles
Finally, we will seize some FSMO roles by going to
new-vm
. Once there, we should:- Identify which operations roles are currently running on
main-vm
. - Seize the schema master, domain naming master, and RID master from
main-vm
. - Confirm the successful move of the seized roles.
- Identify which operations roles are currently running on