Monday, May 24, 2010

Seizing FSMO Roles

Seizing FSMO Roles:

   The five FSMO roles are:


Schema master -       Forest-wide and one per forest.

Domain naming master -      Forest-wide and one per forest.

RID master -      Domain-specific and one for each domain.

PDC -      PDC Emulator is domain-specific and one for each domain.

Infrastructure master -     Domain-specific and one for each domain.

 Important:
 Seize the roles only if the original FSMO role owner will not be brought back into the environment.If the RID, Schema, or Domain Naming FSMOs are seized, then the original domain controller must not be activated in the forest again. It is necessary to reinstall Windows if these servers are to be used again.

Before seizing roles user must be member of:

--------------------------------------------------------------------------
FSMO Role                         Administrator must be a member of

--------------------------------------------------------------------------
Schema                                 Schema Admins

Domain Naming                 Enterprise Admins

RID                                         Domain Admins

PDC Emulator                     Domain Admins

Infrastructure                     Domain Admins


--------------------------------------------------------------------------
 
Caution:


Using the Ntdsutil utility incorrectly may result in partial or complete loss of Active Directory functionality.

STEPS:
  1.  On any domain controller, go to command prompt.
  2. type Ntdsutil.
  3. type roles.
  4. type connections
  5. type connect to server  servername,  where is the name of the server where you want to transfer roles, and then press ENTER
  6. quit
  7. quit
  8. type seize  role, where is the role you want to seize.  Examples are:
Seize domain naming master

Seize infrastructure master

Seize PDC

Seize RID master

Seize schema master

You will receive a warning window asking if you want to perform the seize. Click on Yes.

9. quit

FINISH.....

****Keep Smiling..****
           Pradeep

No comments:

Post a Comment