Transfer Operations Master when Operations Master is offline...

Discussion in 'Active Directory' started by Jon L, Oct 7, 2004.

  1. Jon L

    Jon L Guest


    I have recently upgraded my AD 2000 to AD 2003. When i should upgrade my
    Operations Mater server to w2k3 i had to upgrade some unsupported (old)
    drivers from HP. When the installation of the drivers where finished my
    server would never boot again. (I gave it up after four hours with HP
    support:-() I have 2 servers in my domain... and i have transfered all the
    server roles to the second server (Both was GC's).

    Is it possible to make my second server to be the Operations Master when the
    first DC is offline?

    Please help.....
    Jon L, Oct 7, 2004
    1. Advertisements

  2. Jon L

    MCTrainer Guest

    MCTrainer, Oct 7, 2004
    1. Advertisements

  3. Jon L

    Juan Guest


    okay. Let's see if I've understand you.

    You had 2 servers running Windows 2000. You graded them up to Windows 2003.
    You transferred all roles to one of both servers. You lost one server during
    the backup. This was the server which held all FSMO - roles?

    Okay. No problem. You can specify that the other server should now act as
    holder of all roles by raising them.

    I've tested the following script:

    RAISING FSMO roles:

    If a FSMO Role holder breaks down and cannot be brought back online, you
    have to “seize†the FSMO Role to another DC. Use this option if the option of
    “Restore FSMO – role – holder DC after breakdown†is not wanted or not
    practicable. Consider the Technet Article to identify the best DC for this
    Seizing FSMO roles
    • Logon to the server you want to become the new FSMO role holder
    o Start, Run, cmd, ntdsutil
     roles
    • connections
    o connect to server <FQDN-NewFSMORoleHolder>
    o quit
    • seize <role>
    o (Displays an error message, that the current holder could not be contacted)
    • quit
     quit
    If you want that broken FSMO role holder, which will later be restored,
    should become its old name, you have to cleanup the active directory and wait
    until the changes are replicated to all locations.
    • Logon to any DC
    o Start, Run, cmd, ntdsutil
     metadata cleanup
    • connections
    o connect to server <FQDN-CurrentDC>
     quit
    • select operation target
    o list domains
     select domain <no-of-theDomain-the-DC-was>
    o list sites
     select site <no-of-theSite-the-DC-was>
    o list servers in site
     select server <no-of-theDC-the-DC-was>
    o quit
    • remove selected server
    • quit
     quit
    o Delete computer object in Acitve Directory Users & Computers
    o Delete server object in Sites & Services

    Good luck!

    Juan, Oct 7, 2004
  4. Jon L

    Jon L Guest

    Thank you very much for your answer!
    I havent tested it yet but i will give feed back on the results when i have
    done the operation.

    Thanks again, Jon
    Jon L, Oct 8, 2004
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.