I have 3 DC,[2008 R2] how should i keep my FSMO roles ? Please give some suggestions

what best method of keeping fsmo roles in 3 dcs?

fsmo availability , placement

active directory installation wizard performs initial placement of roles on domain   controllers. placement correct directories have few domain   controllers. in directory has many domain controllers, default placement   may not best match network.

consider following in selection criteria:   

• it's easier keep track of fsmo roles if host them on fewer computers.
• place roles on domain controllers can accessed computers need access given role, on networks not routed. example, obtain current or standby rid pool, or perform pass-through authentication, dcs need network access rid , pdc role holders in respective domains.
• if role has moved different domain controller, , current role holder online , available, should transfer (not seize) role new domain controller. fsmo roles should seized if current role holder not available. more information, go following microsoft website:
  http://technet.microsoft.com/en-us/library/cc816945(ws.10).aspx

        (http://technet.microsoft.com/en-us/library/cc816945(ws.10).aspx)    
• fsmo roles assigned domain controllers offline or in error state have transferred or seized if role-dependent operations being performed. if role holder can made operational before role needed, may delay seizing role. if role availability critical, transfer or seize role required. pdc role in each domain should online @ times.
• select direct intrasite replication partner existing role holders act standby role holder. if primary owner goes offline or fails, transfer or seize role designated standby fsmo domain controller required.

general recommendations fsmo placement

• place schema master on pdc of forest root domain.
• place domain naming master on forest root pdc.
  
  addition or removal of domains should tightly controlled operation. place role on forest root pdc. operations use domain naming master, such creating or removing domains , application partitions, fail if domain naming master not available. on domain controller runs microsoft windows 2000, domain naming master must hosted on global catalog server. on domain controllers run windows server 2003 or later versions, domain naming master not have global catalog server.
• place pdc on best hardware in reliable hub site contains replica domain controllers in same active directory site , domain.
  
  in large or busy environments, pdc has highest cpu utilization because handles pass-thru authentication , password updates. if high cpu utilization becomes problem, identify source, , includes applications or computers may performing many operations (transitively) targeting pdc. techniques reduce cpu include following:
  • adding more or faster cpus
  • adding additional replicas
  • adding additional memory cache active directory objects
  • removing global catalog avoid global catalog lookups
  • reducing number of incoming , outgoing replication partners
  • increasing replication schedule
  • reducing authentication visibility using ldapsrvweight , ldappriority, , using randomize1clist feature that's described in 231305
          (http://support.microsoft.com/default.aspx?scid=kb;en-us;231305)    
    .
  domain controllers in particular domain, , computers run applications , admin tools target pdc, must have network connectivity domain pdc.
• place rid master on domain pdc in same domain.
  
  rid master overhead light, in mature domains have created bulk of users, computers, , groups. domain pdc typically receives attention administrators. therefore, co-locating role on pdc helps ensure reliable availability. make sure existing domain controllers , newly promoted domain controllers, promoted in remote or staging sites, have network connectivity obtain active , standby rid pools rid master.
• legacy guidance suggests placing infrastructure master on non-global catalog server. there 2 rules consider:
  • single domain forest:
    
    in forest contains single active directory domain, there no phantoms. therefore, infrastructure master has no work do. infrastructure master may placed on domain controller in domain, regardless of whether domain controller hosts global catalog or not.
  • multidomain forest:
    
    if every domain controller in domain part of multidomain forest hosts global catalog, there no phantoms or work infrastructure master do. infrastructure master may put on domain controller in domain. in practical terms, administrators host global catalog on every domain controller in forest.
  • if every domain controller in given domain located in multidomain forest not host global catalog, infrastructure master must placed on domain controller not host global catalog.

---

arnav sharma | http://arnavsharma.net/ please remember click “mark answer” on post helps you, , click “unmark answer” if marked post not answer question. can beneficial other community members reading thread.

Windows Server  >  Windows Server General Forum