Announcement

Collapse
No announcement yet.

Moving Exch 2003 to new hardware

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

  • Moving Exch 2003 to new hardware

    Hello
    I currently have an exchange 2003 (w/sp2) server on a windows 2003 (r2) domain controller. Both Windows and Exchange are fully patched.
    We need to take exchange off of the domain controller, temporarily move it to new hardware (i have 2 idenitcal machines) , then demote the DC back to a member server, and then move exchange back to its original box. I found a microsoft document that explains how to move your exchange server to new hardware with keeping the same name.
    http://technet.microsoft.com/en-us/l...EXCHG.65).aspx

    Has anyone ever followed this document having their existing exch server on a DC, moving it to a member server, demoting their DC and moving exch back to its original box?

    Do you think it would be just as easy to replicate the public folders and move mailboxes rather than restore the info store's from tape? If I decided to restore the info store to the new server, would it also keep all of my settings such as my SMTP connector or any other tweaks i've made to my exch server?

  • #2
    Re: Moving Exch 2003 to new hardware

    Hi,


    Yep its work but you have to ensure that you following the proper steps, if you mis/forgot something you will be in BIG TROUBLE. and in your situation you have installed Exchange on DC.

    We had done the same thing, NTBACKUP & /disasterecovery switch help alot.

    Rgds

    Comment


    • #3
      Re: Moving Exch 2003 to new hardware

      Any reason you want to keep the same name?
      If it is just so that you don't have to visit all the machines, you don't need to worry about that. As long as both the old and the new machines are alive when the users login for the first time Outlook will automatically redirect.

      Your best option would be to swing to a new machine with a new name. My guide to the process is here: http://www.amset.info/exchange/migration.asp
      Zero risk, zero downtime, completely transparent to the users. No weekend working, no pressure to get everything done in a short window.

      Data restore is high risk and is not something I would recommend - particularly when there are other techniques that are more reliable and do not put the data at risk.

      If you do decide that you want to swing back to the original machine I would not advise that you simply DCPROMO it out and then install Exchange on to the machine again. I have seen that cause problems. DCPROMO it out, then drop in to a workgroup, wipe and rebuild. That will ensure that all of the security, particularly around IIS functionality is correct.

      Simon.
      --
      Simon Butler
      Exchange MVP

      Blog: http://blog.sembee.co.uk/
      More Exchange Content: http://exchange.sembee.info/
      Exchange Resources List: http://exbpa.com/
      In the UK? Hire me: http://www.sembee.co.uk/

      Sembee is a registered trademark, used here with permission.

      Comment


      • #4
        Re: Moving Exch 2003 to new hardware

        Yes, since my post yesterday I was weighing the best option for this process and felt the swing migration would be the best bet here.

        Once I have the exchange server off of the DC and on to a member server, Would I first uninstall exchange from the DC,then run dcpromo or would you dcpromo the dc 1st and then uninstall exchange

        the dc that exchange is on now is getting wiped and reloaded. But logically speaking, it would seem to make sense to remove exchange off the dc 1st, (verify its completely out of the organization on my new temporary exch member server) and then demote the box to a workgroup , then reload

        let me know your thoughts

        thanks
        Jamie

        Comment


        • #5
          Re: Moving Exch 2003 to new hardware

          Do not touch the domain functionality until Exchange has been removed.
          Therefore you should confirm all data has been removed then uninstall Exchange and reboot.
          Then run DCPROMO to remove it and reboot.
          Then drop in to a workgroup.

          Ideally when the machine is rebuilt a new name is used. I have seen some odd things happen when the name of a former domain controller has been used.

          Simon.
          --
          Simon Butler
          Exchange MVP

          Blog: http://blog.sembee.co.uk/
          More Exchange Content: http://exchange.sembee.info/
          Exchange Resources List: http://exbpa.com/
          In the UK? Hire me: http://www.sembee.co.uk/

          Sembee is a registered trademark, used here with permission.

          Comment


          • #6
            Re: Moving Exch 2003 to new hardware

            that's what i thought. it would make sense to take off exch 1st before demoting the dc ..heh, i can only imagine what mess that would cause.

            also - not sure if you or anyone has ever seen this ... but after i built the new exchange member server, i noticed in the queue's section on the new server gets built up with these msgs that read "[email protected]" and in a retry state.
            ever see that before?

            Comment


            • #7
              Re: Moving Exch 2003 to new hardware

              Exchange replicates information between itself using SMTP. If you are seeing messages in the queues for the other server you need to look at the original server to see if there is anything that is stopping the email from being delivered - restrictions on SMTP for example.

              Simon.
              --
              Simon Butler
              Exchange MVP

              Blog: http://blog.sembee.co.uk/
              More Exchange Content: http://exchange.sembee.info/
              Exchange Resources List: http://exbpa.com/
              In the UK? Hire me: http://www.sembee.co.uk/

              Sembee is a registered trademark, used here with permission.

              Comment


              • #8
                Re: Moving Exch 2003 to new hardware

                Yes I checked the smtp virtual server on my source exchange server.
                i do have restrictions set in the source exch server in the properties of the smtp virtual server. I added the same restrictions to my new exch server i'm building. I still see msgs in the queue's on both servers that look something like "[email protected]" that go into a retry state. so i go in and delete them.

                for now i've just stopped the smtp virtual server on the new exchange server because i need to get my public folders moved which we have a ton of

                Comment


                • #9
                  Re: Moving Exch 2003 to new hardware

                  What restrictions do you have on the SMTP virtual server? I don't actually recommend restrictions on the SMTP VS. If you want to restrict what can connect to the SMTP VS do it at the firewall.

                  Simon.
                  --
                  Simon Butler
                  Exchange MVP

                  Blog: http://blog.sembee.co.uk/
                  More Exchange Content: http://exchange.sembee.info/
                  Exchange Resources List: http://exbpa.com/
                  In the UK? Hire me: http://www.sembee.co.uk/

                  Sembee is a registered trademark, used here with permission.

                  Comment


                  • #10
                    Re: Moving Exch 2003 to new hardware

                    we specified which network (we have multiple vlans) can send emails out of our exch server. we ran into a problem after we upgraded our infrastructure. since the VS was left blank, we started getting all these junk mail queue's pile up in our exch server. Our mail server is not set up to receive mail (we still have a provider handling our incoming mail) and i think port 25 was opened which would have caused our problem.

                    Comment

                    Working...
                    X