Windows Server 2016-preemption FSMO role

In many cases, when there is a problem with the production domain controller that cannot be repaired, we can only preempt the FSMO role to ensure that user authentication is normal or timely recovery. Generally in the same domain environment, we tend to have a master or primary and secondary domain control planning, usually work at the time, two domain control can realize the role of load-sharing, and when the primary domain controller hosting the FSMO five roles (production recommendation separates the role) down, then we can only through the secondary DC to preempt the primary DC role.

Span style= "FONT-SIZE:10PT;" > role	IP address	remarks
major.azureyun.local	192.168.156.1	alternate domain controller
V2spare.azureyun.local	192.168.156.2	Simulate downtime, this environment directly shuts down the machine

1. View the current FSMO role location information:

C:\windows\system32\ntdsutil.exe:roles FSMO maintenance:?? -Show this Help information connections-connect to a specific AD Dc/lds instance help-show this helpful message quit-Return to the previous menu seize infrastructure master-overwrite the structure role on the connected server Seiz  E naming master-overwrites the named master role on the connected server seize pdc-overwrites the PDC role on the connected server seize RID master-overrides the RID role on the connected server seize schema master- overriding schema roles on connected servers select operation Target-Select the site, server, domain, role, and naming context

2. Preempt the infrastructure host:

Enter the seize infrastructure master command to preempt the infrastructure master To Major.azureyun.local, prompt to confirm that the server Major.azureyun.local use the following values to occupy the infrastructure role, select "Yes" to continue:

The preemption success information is as follows:

3. Preempt the domain naming master:

Enter the seize naming master command to preempt the domain naming master to Major.azureyun.local, and confirm that the server Major.azureyun.local use the following values to occupy domain Naming role, select "Yes" to continue:

The preemption success information is as follows:

4. Preempt the PDC emulation host:

Enter the seize PDC command, preempt the PDC impersonation Master role to Major.azureyun.local, confirm that the server Major.azureyun.local uses the PDC role with the following values, select Yes Go on:

The preemption success information is as follows:

5. Preempt the RID master role:

Enter the seize RID Master command, preempt the RID master role to Major.azureyun.local, and confirm that the server Major.azureyun.local consume rid with the following values master role, select "Yes" to continue:

The preemption success information is as follows:

6. Preempt the schema master role:

Enter the seize schema Master command to preempt the schema master To Major.azureyun.local, confirm that the server Major.azureyun.local the schema role with the following values, and select Yes to continue:

The preemption success information is as follows:

FSMO Five role preemption steps:

PS c:\> ntdsutil.exec:\windows\system32\ntdsutil.exe:rolesfsmo maintenance:connectionsserver connections: Connect to server Major.azureyun.local bind to Major.azureyun.local ... Connect Major.azureyun.local with the credentials of this logged-on user. Server Connections:quitfsmo maintenance:fsmo maintenance:seize infrastructure masterfsmo maintenance:seize naming mast Erfsmo maintenance:seize RID masterfsmo maintenance:seize pdcfsmo maintenance:seize schema Masterfsmo Maintenance:quit C:\windows\system32\ntdsutil.exe:quitps c:\>

7. Verify the following information about the preemption FSMO role:

Netdom Query FSMO queries the current FSMO role location-related information, has been changed to Major.azureyun.local:

To query information about the current domain computer role:

Preemption FSMO role Operation Basic complete, thanks for support!

Windows Server 2016-preemption FSMO role