Announcement

Collapse
No announcement yet.

Recovering a Disaster struck AD environment.

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Recovering a Disaster struck AD environment.

    Im stuck with a ludacris environment.

    Since 2002 our domain has been running quite smoothly, even now the majority of the required features run like a charm. However over the years people have installed random applications and background jobs on the DC's causing certain aspects of windows 2000 to corrupt. Of the 2 controllers one has fallen over once, got reinstalled but thanks to the new sid it got it is now zombied and since it contains the FSMO roles i cant adprep /domainprep to niether 2003/2008.

    Tranferring the FSMO roles failes misrebaly, and im too scared to seize the roles in case i mess it up completely. (what are the risks of seizing?)

    What i need to do now is fix this domain, upgrade it to 2003/2008 and new hardware. I have 2x HS21 blades ready to go along with 2003 or 2008 vlks. And i need to keep the current domain name.

    Is it possible to export the useraccounts and AD object data from 2000 to a new 2003/2008/machine ?
    MCITP:SA 2008, MCITP:EA 2008
    MCTS Vista, MCTS Windows 7
    Cisco Certified Network Associate
    ITIL Practitioner V3
    IBM Certified Specialist: System X
    IBM Certified Systems Expert: BladeCenter
    VMWare Certified Professional
    Working on:
    Bcom Criminology, MS OCS

  • #2
    Re: Recovering a Disaster struck AD environment.

    Seizing the FSMOs (as long as the original FSMO owners are not brought back to life) is not a destructive operation. Make a System State backup of the DC before seizing the roles, and go for it.
    Guy Teverovsky
    "Smith & Wesson - the original point and click interface"

    Comment


    • #3
      Re: Recovering a Disaster struck AD environment.

      Originally posted by guyt View Post
      Seizing the FSMOs (as long as the original FSMO owners are not brought back to life) is not a destructive operation. Make a System State backup of the DC before seizing the roles, and go for it.

      I thought that if i seize all the fsmo roles from one dc to another they are _moved_ completely and you have basically changed the role holder ?

      The only reason for seizing would be to ultimately enable me to adprep /forestprep so that i can add a proper DC to the collection and the _transfer_ the roles to the new dc.
      MCITP:SA 2008, MCITP:EA 2008
      MCTS Vista, MCTS Windows 7
      Cisco Certified Network Associate
      ITIL Practitioner V3
      IBM Certified Specialist: System X
      IBM Certified Systems Expert: BladeCenter
      VMWare Certified Professional
      Working on:
      Bcom Criminology, MS OCS

      Comment


      • #4
        Re: Recovering a Disaster struck AD environment.

        Exactly. This is what you want to do at this point. Seize the roles from the malfunctioning DC to another DC. Demote the malfunctioning DC. Run NTDSUTIL for metedata cleanup if needed. DCPROMO another DC (so that you have two good, clean DC's) and prep the domain for 2003/2008.

        Comment


        • #5
          Re: Recovering a Disaster struck AD environment.

          What i need to do now is fix this domain, upgrade it to 2003/2008 and new hardware. I have 2x HS21 blades ready to go along with 2003 or 2008 vlks. And i need to keep the current domain name.

          Is it possible to export the useraccounts and AD object data from 2000 to a new 2003/2008/machine ?


          Now what i need from you...... to get it going.....

          Seizing won't cause issue

          I need what is happening on your old domain controller... what error are you getting.

          You said you want to go with 2008 or 2003

          I have implemented 2008 DC in existing env with 2003 ... shudn't be a big deal but a little trick..

          so send me the error and nature of problem
          Thanks & Regards
          v-2nas

          MCTS 2008, MCTIP, MCSE 2003, MCSA+Messaging E2K3, MCP, E2K7
          Sr. Wintel Eng. (Investment Bank)
          Independent IT Consultant and Architect
          Blog: http://www.exchadtech.blogspot.com

          Show your appreciation for my help by giving reputation points

          Comment


          • #6
            Re: Recovering a Disaster struck AD environment.

            Originally posted by joeqwerty View Post
            Exactly. This is what you want to do at this point. Seize the roles from the malfunctioning DC to another DC. Demote the malfunctioning DC. Run NTDSUTIL for metedata cleanup if needed. DCPROMO another DC (so that you have two good, clean DC's) and prep the domain for 2003/2008.
            i wanted to:
            -seize all from dc2 to dc1
            -trash dc2 completely
            -run of 1 dc while i adprep
            -add either a 2003/2008 dc
            -transfer the fsmo roles to the new dc
            -add the second new dc

            and voila 2 fresh dcs
            MCITP:SA 2008, MCITP:EA 2008
            MCTS Vista, MCTS Windows 7
            Cisco Certified Network Associate
            ITIL Practitioner V3
            IBM Certified Specialist: System X
            IBM Certified Systems Expert: BladeCenter
            VMWare Certified Professional
            Working on:
            Bcom Criminology, MS OCS

            Comment


            • #7
              Re: Recovering a Disaster struck AD environment.

              Originally posted by dotnerd View Post
              i wanted to:
              -seize all from dc2 to dc1
              -trash dc2 completely
              -run of 1 dc while i adprep
              -add either a 2003/2008 dc
              -transfer the fsmo roles to the new dc
              -add the second new dc

              and voila 2 fresh dcs
              Well, this is what Guyt and Joeqwerty are suggesting you do pretty much!
              Caesar's cipher - 3

              ZKHQ BRX HYHQWXDOOB GHFLSKHU WKLV BRX ZLOO UHDOLVH LW ZDV D ZDVWH RI WLPH!

              SFX JNRS FC U6 MNGR

              Comment

              Working...
              X