Seizing FSMO roles

1, openPowershell, enterNtdsutil. EXE; Enter " Help", ManageNTDSrole owner token, using theRoles"command, enter"Roles";

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/58/C0/wKiom1S7P1PxrGGuAAW3omK37oI222.jpg "title=" 1.PNG " alt= "Wkiom1s7p1pxrgguaaw3omk37oi222.jpg"/>

2 , enter the Help "Get help; Connect to a specific instance, using the" Connections "; input" Connections ";

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/58/BD/wKioL1S7QDjQowFLAAPWKfTyyrM958.jpg "title=" 2.PNG " alt= "Wkiol1s7qdjqowflaapwkftyyrm958.jpg"/>

3 , enter " help "Get help, Connect to the server, use Connect to server%s, enter connect to server ad-server .xuelan.local Span style= "font-family: ' Microsoft Jas Black ';" lang= "ZH-CN" xml:lang= "ZH-CN" > "

( %s , is the server's FQDN The full name, in the example " Ad-server . Xuelan.loca L ")

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/58/C0/wKiom1S7P3nAb1LlAAL5YBvaf5U960.jpg "title=" 3.PNG " alt= "Wkiom1s7p3nab1llaal5ybvaf5u960.jpg"/>

4 , enter the quit "Return to the previous level, enter" Help "Get help; capture infrastructure master, use seize infrastructure master command;

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/58/BD/wKioL1S7QFeDBxHAAAPd14At7LM980.jpg "title=" 4.PNG " alt= "Wkiol1s7qfedbxhaaapd14at7lm980.jpg"/>

5 , enter "Seizeinfrastructure Master "After confirmation, a role occupancy confirmation dialog will pop up, select" Yes ";

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/58/C0/wKiom1S7P5TjX0AzAAPKfIKgACk929.jpg "title=" 5.PNG " alt= "Wkiom1s7p5tjx0azaapkfikgack929.jpg"/>

6 , when the command is complete, we look at the process and find that the system will attempt to transfer the role safely before the role is captured, but the system will continue to claim (seize) after the security transfer fails;

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/58/BE/wKioL1S7QHWzv1v2AARYCaoHAdw521.jpg "title=" 6.PNG " alt= "Wkiol1s7qhwzv1v2aarycaohadw521.jpg"/>

7 , from 4 step help, you can know , seize the domain naming master role with "seize naming master"; (note here in 2008

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/58/BE/wKioL1S7QIOhlVMRAAN22xlYdzk692.jpg "title=" 7.PNG " alt= "Wkiol1s7qiohlvmraan22xlydzk692.jpg"/>

8 , also from the first 4 step of the help can know that capture PDC role, use "Seize PDC", enter "SEIZEPDC", also pop up "role Occupancy confirmation Dialog" select "Yes"; PDC host role, the same will try to secure the transfer, the transmission fails to seize, the process is similar to the front;

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/58/C0/wKiom1S7P8DAzybyAAO0xRWfSxU050.jpg "title=" 8.PNG " alt= "Wkiom1s7p8dazybyaao0xrwfsxu050.jpg"/>

9 , seize The rid role uses "seize RID Master" and also selects "Yes" in the "Role Occupancy confirmation dialog box" that pops up;

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/58/BE/wKioL1S7QJ6iM58qAAR0NcrxLlg945.jpg "title=" 9.PNG " alt= "Wkiol1s7qj6im58qaar0ncrxllg945.jpg"/>

Ten , capture the schema master role using "Seizeschema Master", and also select "Yes" in the "Role Occupancy confirmation dialog box" that pops up;

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/58/C0/wKiom1S7P-DxYuCLAAVHCknoj54457.jpg "title=" 10.PNG "alt=" Wkiom1s7p-dxyuclaavhcknoj54457.jpg "/>

One , here the character capture has been completed, the following is the verification of the role of the success of the request; I'm going to go ahead, so use two times " quit "return to the front; if it is rerun Powershell , run "Netdomquery FSMO" to view FSMO role.

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/58/BE/wKioL1S7QOCgbfq1AANI428v-fI288.jpg "title=" 11.PNG "alt=" Wkiol1s7qocgbfq1aani428v-fi288.jpg "/>

This article is from the "Snow Orchid" blog, please be sure to keep this source http://yupeizhi.blog.51cto.com/3157367/1605265

Seizing FSMO roles