none
Upgrade path from Exchange 2003 to 2010

    Question

  • When Exchange 2010 gets relased to the public will it include an upgrade path from Exchange 2003 to 2010?

    Thanks
    Bulls on Parade
    Wednesday, April 22, 2009 8:33 PM

Answers

  • Yes from E2K3 SP2 and later.

    Henrik Walther Exchange MVP | MCM: E2K7 | MCITP: EMA/EA | MCSE: M+S - MSExchange.org

    To clarify, you have to build a new server and move the mailboxes. You cannot do an in-place upgrade, but 2010 will co-exist with SP2 perfectly fine.
    Brian Day / MCSA / CCNA, Exchange/AD geek.
    Wednesday, April 22, 2009 11:43 PM

All replies

  • Yes from E2K3 SP2 and later.

    Henrik Walther Exchange MVP | MCM: E2K7 | MCITP: EMA/EA | MCSE: M+S - MSExchange.org
    Wednesday, April 22, 2009 8:39 PM
  • Yes from E2K3 SP2 and later.

    Henrik Walther Exchange MVP | MCM: E2K7 | MCITP: EMA/EA | MCSE: M+S - MSExchange.org

    To clarify, you have to build a new server and move the mailboxes. You cannot do an in-place upgrade, but 2010 will co-exist with SP2 perfectly fine.
    Brian Day / MCSA / CCNA, Exchange/AD geek.
    Wednesday, April 22, 2009 11:43 PM
  • Yes from E2K3 SP2 and later.

    Henrik Walther Exchange MVP | MCM: E2K7 | MCITP: EMA/EA | MCSE: M+S - MSExchange.org

    To clarify, you have to build a new server and move the mailboxes. You cannot do an in-place upgrade, but 2010 will co-exist with SP2 perfectly fine.
    Brian Day / MCSA / CCNA, Exchange/AD geek.
    Hi,

    Yep, AFAIK But Beta version doesn’t support manage e2k3 in exchange 2010 management console. It might be support in RTM.

    Regards

     


    Chinthaka -If you think my thread is helpful, Please vote.
    Thursday, April 23, 2009 12:59 AM
  • To clarify, you have to build a new server and move the mailboxes. You cannot do an in-place upgrade, but 2010 will co-exist with SP2 perfectly fine.
    Brian Day / MCSA / CCNA, Exchange/AD geek.

    Well in-place upgrades from E2K3 to E2K10 would have been a very surprising move from the Exchange Product group since in-place upgrades also wasn't an option with E2K3 > E2K7 transitions.

    Oh and with all the changes done since E2K3 (Windows server versions, move to x64 architecture, major store enhancements/changes and so on), I think providing an in-place upgrade option would be close to impossible. And if it was possible I would do everything in my power to avoid it just like I did back in the Exchange 5.5 > E2K and E2K > E2K3 transition/upgrade days.

    Henrik Walther Exchange MVP | MCM: E2K7 | MCITP: EMA/EA | MCSE: M+S - MSExchange.org
    • Proposed as answer by ValiDumitru Sunday, November 15, 2009 1:06 PM
    Thursday, April 23, 2009 7:19 AM
  • Yep, AFAIK But Beta version doesn’t support manage e2k3 in exchange 2010 management console. It might be support in RTM.

    Regards

     


    Chinthaka -If you think my thread is helpful, Please vote.

    The management of E2K3 and E2K7/E2K10 is completely separate as the admin tools were re-architectured with E2K7, so this will also be the case when we reach RTM.

    But an interesting detail is that the E2K7 and E2K10 management tools can run on the same machine making management in mixed environment slightly easier: http://blogs.msexchange.org/walther/2009/04/23/installing-e2k7-and-e2k10-management-tools-on-the-same-machine/


    Henrik Walther Exchange MVP | MCM: E2K7 | MCITP: EMA/EA | MCSE: M+S - MSExchange.org
    Thursday, April 23, 2009 7:30 AM
  • I had just performed an exchange 2003 to exchange 2010 migration. First off, this went flawless! I was so happy with the outcome. As many of you know, Exchange 2010 requires 64 bit OS. THEREFORE, I started the projected by creating a new 64-bit Windows 2008 enterprise server and a new windows 2008 64 bit enterprise domain controller in an existing 2003 active directory environment. First, let me say that you have to run adprep off the 2008 cd on your DC that holds your fsmo roles. I installed exchange 2010 and brought up a new BES 5.0.2 server as I thought this would be an excellent time to refresh corporate blackberry users. I love this version of exchange! I was running co-existence mode until the migration was complete and then I uninstalled exchange 2003 from my environment and retired that old clunky exchange server. Let me say that despite the noise about making your client access and mailbox role a VM. I had no issue doing this, as I am a huge VMware and virtualization fan. I have had no issue with my cas, hub, and mailbox roles all in one VM with zero performance issues. One thing I do not like is that by design store.exe is now a memory hog! However, there are parameters that you can use in adsiedit.msc where you can limit the memory usage of store.exe that work great! All in all the only complaint I got was from the helpdesk, as they cannot install Exchange management tools on their desktops because they run 32 bit OS. I told them to upgrade their desktop OS to 64 bit so they can run the tools. I know they make some third party management tools that allow your helpdesk to still perform common exchange tasks but I am NOT a big third party fan. If anyone has any questions about more details about my migration from exchange 2003 to 2010 I will be more than happy to answer them. In addition, when you plan your exchange 2010 rollout one big thing to remember here is give yourself plenty of space for the info store lun as exchange 2010 does NOT like to have less than 2 gb free space of the store lun or luns. If it goes below 2 GB mail will stop flowing and will not flow again until you free up some space.

    Frank Bicocchi

    Thursday, February 10, 2011 9:20 PM
  • For anyone following up, heres some nfo that might be helpfull

    Exchange 2003 to 2010 Migration

    Pete

    PeteNetLive

    Monday, April 04, 2011 3:56 PM
  • Hi,

    I have three Server DC1 , DC2  and Mail (exchange 2003 sp2 ) all are running with windows server 2003 sp2 x86. Now we have a plan to go for windows 2008 R2 and Exchange 2010. Four new x64 server ( DC1 , DC 2 , Exchange Prime ( Client , Hub) , Exchange MB. Please provide the best way of doing this task.

    Unais

    unaischr@gmail.com
    Tuesday, April 19, 2011 7:38 PM
  • For anyone following up, heres some nfo that might be helpfull

    Exchange 2003 to 2010 Migration

    Pete

    PeteNetLive


    Hi,

    I have three Server DC1 , DC2  and Mail (exchange 2003 sp2 ) all are running with windows server 2003 sp2 x86. Now we have a plan to go for windows 2008 R2 and Exchange 2010. Four new x64 server ( DC1 , DC 2 , Exchange Prime ( Client , Hub) , Exchange MB. Please provide the best way of doing this task.

    Unais

    unaischr@gmail.com
    Tuesday, April 19, 2011 7:43 PM
  • Hi,

    I have three Server DC1 , DC2  and Mail (exchange 2003 sp2 ) all are running with windows server 2003 sp2 x86. Now we have a plan to go for windows 2008 R2 and Exchange 2010. Four new x64 server ( DC1 , DC 2 , Exchange Prime ( Client , Hub) , Exchange MB. Please provide the best way of doing this task.

    Unais

    unaischr@gmail.com
    Tuesday, April 19, 2011 7:43 PM
  • Hi Frank:

    Thanks for the Useful information Happy to hear that the migration went smoothly.

    I am in an environmemt that will be moving from Exchange 2003 to 2010 shortly. Noting what you mentioned regarding running the adprep on the primary DC; did you happen to notice any issues with AD afterwards? Also how long after that you ran the AD prep did you start the Exchnage 2010 installation? (i.e. 1 week..etc)

     Primarly the focus is on using VM's for Exchange 2010 which I am a big fan of. Understanding the reduced I/O with Exchange 2010; how large of an environment were you architechting this solution for?

    I appreciate your insight.

    Demetrios

    Monday, May 02, 2011 4:22 PM
  • Frank,

    Good comments. Encouraging as I am about about embark on an upgrade of three  Exchange 2003 Server in CA onto one Exchange 2010 Server in FL over an VPN conection.

    What do you think? Any advise or good reading material. I am no Exchange expert.

    Nigel

    Wednesday, September 14, 2011 2:37 AM