asked on

Migration from Exchange 2003 to 2010 without coexistence?

Is it possible to migrate a single Exchange 2003 server to Exchange 2010 without using coexistence?

I would like to export user mailboxes and public folders to PST files and import them to the new Exchange 2010 afterwards. Do I miss something important or is it possible to migrate a small Exchange server that way without problems or missing data?

I did not setup the Exchange 2003 system. Are there any options/features where some additional data or unusual preferences could be stored?

Is it better to use Outlook or Exmerge to create the PST files? I am thinking about problems with code pages using Exmerge. Will this be a problem if I use Outlook instead?

M A

Exchange 2003 usually runs on 32-bit hardware whereas Exchange 2007 / 2010 requires 64bit hardware.

If your current server is 32bit you will have to buy a new hardware. Then upgrade using the link below.

http://msexchangegeek.com/2010/01/30/rapid-transition-guide-from-exchange-2003-to-exchange-2010/

http://www.simple-talk.com/sysadmin/exchange/upgrade-exchange-2003-to-exchange-2010

http://www.simple-talk.com/sysadmin/exchange/upgrade-exchange-2003-to-exchange-2010---part-ii/

Or if your current hardware is 64bit and you do not want to buy new hardware
1.Export your mailboxes to PST using Exmerge
2.Export your Public Folders to PST from your outlook
3.Install exchange 2010 using the below URL

http://www.msexchange.org/articles_tutorials/exchange-server-2010/migration-deployment/installing-exchange-server-2010-beta-part1.html

M A

Please check this if you want to uninstall/remove exchange2003 from your networt
http://support.microsoft.com/kb/833396

Malli Boppe

Any real reason why you want go about creating PST files, instead of going through the co-existance path.

With your Approach.
1.) Creating PST files and import them would lot longer then moving hte maailboxes.
2.) When building new exchange 2010 server in the same domain it would recognise that you have 2003 server and wouldn't let you gohead.
3.)Moving PB would be lot more difficult
etc

exexc

ASKER

I'm planning to rebuild the whole network (including DC / Active Directory) because

a) It was not configured by me and has some design decisions I don't like (for example a very poor OU-structure, inconsistent role based access controls, 3rd party POP-connector instead of SMTP)

b) There are a lot of DNS/Replication and other errors in the event log and it will be faster/cleaner to start from scratch, than fixing all those problems

c) It's a small and very simple network (no policies, no complicated security structure, only 15 users)

So there won't be any problems with the active directory or leftovers from the old Exchange system.

What is PB?

ASKER CERTIFIED SOLUTION

lucid8

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

exexc

ASKER

Thanks.

lucid8

Happy to assist and thanks for the points