Announcement

Collapse
No announcement yet.

W2k3 DC on new hardware with same name and ip address

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

  • W2k3 DC on new hardware with same name and ip address

    Hello,

    We have two DC's W2k3 SP1 installed in our single domain. There is also a.o. a Exch2k3 SP1 server installed on the domain. The first DC contains all the fsmo-roles with AD Int, GC, DHCP, WINS but installed in \winnt directory ('in place upgrade' once). The second is also AD Int with GC, WINS (but installed in \windows). We now want to install the first on new hardware in \windows while keeping the same name and ip address. What is the best/safest/quickest way to do that?

    Thanks
    Hendrik

  • #2
    Re: W2k3 DC on new hardware with same name and ip address

    create a new DC with unique name... and the file structure like you want it.

    backup the old... the entire thing.

    restore the backup to the new file structure... while in recovery mode.

    bring the new online.

    squash the old.

    but thats just speculation. ive never tried to do that.

    i would probably just bring up a new one, force a complete replication, seize the roles on the new, and squash the old one once everything has replicated and all the roles are seized...

    again, this is not a tested routine or based on any KBs. i dont think you will find a KB with the things you want to accomplish...

    good luck!
    its easier to beg forgiveness than ask permission.
    Give karma where karma is due...

    Comment


    • #3
      Re: W2k3 DC on new hardware with same name and ip address

      James, you have forgotten about our good friend Mr Swing Migration. Hendrik, this will do all you want. (Might be an idea to install the SPs on the servers and Exchange at some stage.)
      1 1 was a racehorse.
      2 2 was 1 2.
      1 1 1 1 race 1 day,
      2 2 1 1 2

      Comment


      • #4
        Re: W2k3 DC on new hardware with same name and ip address

        nice product... i have never heard of it, but the service it offers looks like the exact thing Hendrik is looking for.

        thanks for the update.

        Hendrik would have probably hosed the whole thing had he followed my half-baked advice.
        its easier to beg forgiveness than ask permission.
        Give karma where karma is due...

        Comment


        • #5
          Re: W2k3 DC on new hardware with same name and ip address

          Thanks James and Biggles77 for the replies.
          Watching the Swing Migration: why not do a transfer of the roles, and to the second DC then?

          Also in general: I once did a migraton of our Exch2k3 server to new hardware from \winnt to \windows. There was an (exchange) kn. base article mentioning the "Reset computer account" and later "renaming to the same name and ip" what worked excellent. I was wondering whether I could use something like that again for a dc? So transfering all the roles and replace/remove all other stuff (demote, dns, dhcp, wins, gc) to the 'mirror' second dc, install new dc with same name and ip etc. and transfer roles etc. back.

          Thanks again!
          Hendrik
          Last edited by Hendrik; 3rd October 2007, 10:59.

          Comment


          • #6
            Re: W2k3 DC on new hardware with same name and ip address

            Anybody else perhaps?
            Thanks.

            Comment


            • #7
              Re: W2k3 DC on new hardware with same name and ip address

              Let me get this right before i comment.

              You have the following on your site.

              2 * Domain Controllers
              1 * Exchange Server

              DC1 holds all your FSMO roles.
              DC2 is a GC, WINS, DNS.

              What you want is to demote server 1 and replace it with a server of the same name and IP address.

              This is actually rather simple if that is the case.

              Transfer FSMO roles from DC1 to DC2.
              Transfer DHCP, DNS and anything else from DC1 to DC2.
              Transfer all Data to DC2.
              Allow replication to occur.
              Demote DC1 back to being a member server, thus removing AD from it.
              Ensure users can connect to the domain and retreive all data, emails etc, etc, etc.
              Remove DC1 from the domain completly by removing from the domain.
              Allow replication to occur.
              Delete all references to DC1 in DNS.
              Take a final backup of the system.
              Format the system and install a new installation of Server 2003 applying any updates that you need.
              Assign the new computer the same name as the old DC1 and assign the same IP address as the old DC1.
              Join the machine to the domain as a member server.
              DCPromo the machine to be a new DC on your existing domain.

              I've no doubt missed something and someone will be along to add to it.

              If the scenario i posted is incorrect then please let me know and we will re-think it.

              Comment


              • #8
                Re: W2k3 DC on new hardware with same name and ip address

                Hello Wullieb1,

                I was thinking in the same way but needed some feedback: I was wondering if we could completely remove DC1 and bring it back in \windows without losing any crucial ip/name, data/references somewhere? (and in the quickest way as possible..). We have a lot of them, that's why.
                Indeed we have a.o.:
                2 * Domain Controllers
                1 * Exchange Server
                (also 12 other servers)

                DC1 holds all the FSMO roles (and DNS, WINS, DHCP, GC also but you mentioned it later)
                DC2 is a GC, WINS, DNS.

                Hendrik
                Last edited by Hendrik; 4th October 2007, 10:39.

                Comment


                • #9
                  Re: W2k3 DC on new hardware with same name and ip address

                  The way i wrote is probably the quickest way to do it.

                  To do it the way i said should take a max of 3 days IMO.

                  Preperation is the key.

                  You could have a server built and ready to go so that all it needs is an IP change and a name change.

                  Backups should be run overnight, your not there anyway. Replication will occur overnight as well.

                  Trust me plan it out and give yourself a schedule to do it in and you'll be fine. Sometimes you need to have the planning done properly to help iron out small niggles.

                  Good luck

                  Comment


                  • #10
                    Re: W2k3 DC on new hardware with same name and ip address

                    The first tests looked good here.
                    Thanks everybody for the feedback.

                    Hendrik

                    Comment


                    • #11
                      Re: W2k3 DC on new hardware with same name and ip address

                      Originally posted by Hendrik View Post
                      The first tests looked good here.
                      Thanks everybody for the feedback.

                      Hendrik
                      Excellent.

                      Thanks for posting back.

                      Comment

                      Working...
                      X