Active Directory Replication - HELP!

Discussion in 'Software' started by Fluid, Apr 29, 2009.

  1. Fluid

    Fluid Byte Poster

    180
    0
    14
    The zone name must be exactly the same as your Active Directory Domain name, or, if on a stand-alone or workgroup environment - t

    http://www.petri.co.il/install_and_configure_windows_2003_dns_server.htm

    So ill follow that :)
     
  2. oush

    oush Byte Poster

    103
    0
    21
    hope its fixed?
     
    Certifications: MCITP: EA, Linux+, CCNA, CCDA
    WIP: CCIP
  3. Fluid

    Fluid Byte Poster

    180
    0
    14
    Thanks its going well, but im rather confused regarding the FSMO roles. From what I understand is that only one DC can have the FSMO roles and be active at the same time. Can I not make another DC have the roles as well and if the first DC files then i just activate the roles on the 2nd DC? Or do I need to seize them manually, sezing the roles manually does not make any sense to me as you will be stuffed if you have hardware failures or total data loss... I tried googling "Replicating FSMO Roles" etc but all they talk about is sezing the roles.
     
  4. craigie

    craigie Terabyte Poster

    3,020
    174
    155
    OK, to be perfectly clear, you cannot have more than one server performing the same FSMO role in the domain period.

    If you have planned downtime then you can transfer the roles onto another Server manually.

    If you Server blows up, then you need to seize the roles from that Server and place them onto another Server in the same domain,. Then you need to completely wipe and reinstall the blown up Server before reinstating it into AD, otherwsie you will have massive issues.
     
    Certifications: CCA | CCENT | CCNA | CCNA:S | HP APC | HP ASE | ITILv3 | MCP | MCDST | MCITP: EA | MCTS:Vista | MCTS:Exch '07 | MCSA 2003 | MCSA:M 2003 | MCSA 2008 | MCSE | VCP5-DT | VCP4-DCV | VCP5-DCV | VCAP5-DCA | VCAP5-DCD | VMTSP | VTSP 4 | VTSP 5
  5. Triton.Deep

    Triton.Deep Bit Poster

    42
    3
    22
    First, craigie's post just before this one is right on.

    Just keep in mind, even if one of your Domain Controllers had all five roles and it had a massive heart attack and died, while there might be (might, depending on if you have pre-Windows 2000 systems in your Domain mostly) some small amount of impact on your users you would generally have days to fix the problem. Some of those FSMO roles are practically never used.

    You'll have time if that happens, just have a process in place and know how to switch them over both gracefully for maintenance windows if needed, or by seizing them if your DC bites the dust hard.

    Heres some more help:

    1) FSMO Role Placment: http://support.microsoft.com/kb/223346
    2) FSMO Gracful Transfer: http://support.microsoft.com/kb/324801
    3) FSMO Role Seizure: http://support.microsoft.com/kb/255504

    Use #1 to figure out where to put them. Use #2 to transfer roles if all your DC's are avaliable and good to go. Use #3 if one of your DC's hosting FSMO roles crashs bad and you can't get it back online.

    J.
     
    Certifications: MCITP EMA, MCTS, MCSE (x3), CCNA, A+,etc
    WIP: MCM for Exchange probably. Not Sure

Share This Page

Loading...
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.