1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Active Directory work for customer...

Discussion in 'Networks' started by Theprof, Aug 16, 2011.

  1. Theprof

    Theprof Petabyte Poster Forum Leader

    4,570
    68
    196
    Out of curiosity, I am am thinking about splitting our customers internal FSMO roles that are currently on one server and putting 3 (Infrastructure, RID, and PDC) on a second server. That way we have 1 server that hosts the Schema and Domain name roles and one server hosting Infrastructure, RID, and PDC roles. I've already made sure that the servers are GC's and from a performance perspective things look good. Would you guys recommend to keep all the FSMO roles on the same server or split up the roles?

    Just a side now, I am restructuring the Active Directory for our customer with new OU's, fixing up GPO's, etc... so I figured I would add the FSMO role management to the task.
     
    Certifications: A+ | CCA | CCAA | Network+ | MCDST | MCSA | MCP (270, 271, 272, 290, 291) | MCTS (70-662, 70-663) | MCITP:EMA | VCA-DCV/Cloud/WM | VTSP | VCP5-DT | VCP5-DCV
    WIP: VCAP5-DCA/DCD | EMCCA
  2. Shinigami

    Shinigami Megabyte Poster

    896
    40
    84
    The argument for doing this is twofold. First, it means you're not placing all of your eggs in a single basket (so if you lose one server, half of your 'roles' still function), and the second pertains to performance, since a server with the PDCe role is the one which is most likely to be utilized (it remains the busiest server), and thus as you remove roles from it, you reduce any 'potential' load that may occur due to needs from the other FSMO roles.

    Admittedly, once your environment has been setup, you're not very likely to rely on the Domain Naming or Schema Master roles (used to extend your schema or add new domains to your forest, and that's just about it), but every little helps.

    And keeping the Infrastructure Master, PDCe and RID roles on the same server in a small environment is also a recommended practice, so I'd say go for it. Just make sure you updated any documented DR practices.
     
    Certifications: MCSE, MCITP, MCDST, MOS, CIW, Comptia
    WIP: Win7/Lync2010/MCM
    Theprof likes this.
  3. Theprof

    Theprof Petabyte Poster Forum Leader

    4,570
    68
    196
    Thanks Shinigami, I appreciate the input! What you said is pretty much what's been on my mind, I was just curious to get some opinions and see if I am missing something...
     
    Certifications: A+ | CCA | CCAA | Network+ | MCDST | MCSA | MCP (270, 271, 272, 290, 291) | MCTS (70-662, 70-663) | MCITP:EMA | VCA-DCV/Cloud/WM | VTSP | VCP5-DT | VCP5-DCV
    WIP: VCAP5-DCA/DCD | EMCCA
  4. onoski

    onoski Terabyte Poster

    3,120
    51
    154
    Personally from a performance and redundancy viewpoint I'd split the roles that comprise the FSMO roles. I quite like and second the point Shinigami made:)
     
    Certifications: MCSE: 2003, MCSA: 2003 Messaging, MCP, HNC BIT, ITIL Fdn V3, SDI Fdn, VCP 4 & VCP 5
    WIP: MCTS:70-236, PowerShell

Share This Page

Loading...