Announcement

Collapse
No announcement yet.

Exchange 2003-2010 Transition

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

  • Exchange 2003-2010 Transition

    I am working on a Exchange 2003 to 2010 transition and have a couple of questions.

    Firstly, before I go ahead an install Exchange 2010, are there any DNS considerations I need to be aware of first? My concern is that the A record for the namespace points currently to 2003, as does the MX. One I introduce the 2010 server (all roles), will it 'take over' and therefore break client connectivity?

    My understanding is that mailflow will then traverse the 2010 server once installed, but the DNS records point to 2003. I wanted to set up the Exchange 2010 server, configure it, and then move all mailboxes over a weekend together with updating the DNS records and firewall, and am concerned that something will break before I have the opportunity to do so.

    Secondly, my 2003 server is in a different site to the 2010 server, will that be an issue at all?

  • #2
    Re: Exchange 2003-2010 Transition

    For client access, you need to read the documentation on coexistence on TechNet. Everything is explained there. Similar for mail flow, you can deliver email to any server in the platform - Exchange will sort out where it needs to go.

    Do ensure that you have replicated public folders to the new server before you move any mailboxes to it. Furthermore there is no need to rush through moving the mailboxes, Exchange can do coexistence quite happily.

    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


    • #3
      Re: Exchange 2003-2010 Transition

      Thank you.

      I have never fully understood the legacy/coexistance part of this to be honest.

      Is my process correct?

      - Create new A record legacy.mycompany.com pointing to new 2010 CAS server

      - Move DNS namespace across to 2010 CAS

      - Generate new Cert from 2010 server incorporating primarynamespace.mycompany.com, autodiscover.mycompany.com and legacy.mycompany.com

      - Assign above cert to 2003 and 2010

      - Run the Set-OwaVirtualDirectory -Identity "server\owa (Default Web Site)" -Exchange2003Url https://legacy.mycompany.com/exchange

      Requests for 2003 mailboxes are then redirected by 2010 to 2003 seamlessly?

      Comment


      • #4
        Re: Exchange 2003-2010 Transition

        The legacy.example.com host name needs to point to the legacy server - so your Exchange 2003 server. The idea being that all traffic hits the Exchange 2010 server and Exchange will sort out whether it is redirected or not.

        Otherwise the rest of it is fine.

        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

        Working...
        X