realtimer
asked on
New Exchange [2013] server; new separate domain. How do I import mailboxes?
Hello,
I am in the process of replacing an environment running 1 SBS 2003 with 2 servers - 1 Domain Controller/File Server and 1 Exchange 2013 server.
I learned the hard way recently that exporting mailboxes and public folders to PST, and then importing them to the new mailboxes creates a mess. 1 - Public Folder calendars get populated with entries that say "Copy" and cannot be edited. 2 - in mailbox contents, when users try to reply to pre-migration messages, they receive NDR's.
That said, I want to implement the appropriate solution for migrating mailboxes. This is not a lateral migration, so I will not have both servers on the same domain. I will not be able to move mailboxes from SBS2003 to Exchange 2013. So what are my options?
Thanks in advance.
Regards,
Real-Timer
I am in the process of replacing an environment running 1 SBS 2003 with 2 servers - 1 Domain Controller/File Server and 1 Exchange 2013 server.
I learned the hard way recently that exporting mailboxes and public folders to PST, and then importing them to the new mailboxes creates a mess. 1 - Public Folder calendars get populated with entries that say "Copy" and cannot be edited. 2 - in mailbox contents, when users try to reply to pre-migration messages, they receive NDR's.
That said, I want to implement the appropriate solution for migrating mailboxes. This is not a lateral migration, so I will not have both servers on the same domain. I will not be able to move mailboxes from SBS2003 to Exchange 2013. So what are my options?
Thanks in advance.
Regards,
Real-Timer
vSolutionsIT
Exporting emails from Exchange 2003 and importing to Exchange 2013 is not really recommended as it stripes down the formatting of the emails most of the time and email contents shows as junk characters while they are viewed.
ASKER
I understand that. Hence the question.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
My recommendation will be:
Install a new server (2008 or 2012, they could be trial and/or VMs) as a member.
Install Exchange Server 2010 (could be also trial)
Create new dbs
Install Certificates
Migrate mailboxes from 2003
Migrate shared folders (if any) from 2003
Re-direct mail flow to 2010 (DNS A and MX record, firewall, etc.)
Remove Exchange 2003
Install a new server (2008 or 2012)
Install DHCP, DNS, AD GC roles
Transfer FSMO role to new Server
Transfer Scripts to new Server
Remote SBS 2003
Install a new server as a member.
Install Exchange Server 2013.
Create new dbs
Migrate Certificates
Migrate mailboxes from 2010
Migrate shared folders (if any) from 2010 (not recommended)
Re-direct mail flow to 2013 (DNS A and MX record, firewall, etc.)
Remove Exchange 2010 and Server 2012 (box or VM)
Please note that you will need 3 machines to complete the migration, this machines could be full hard metal or VMs or a combination. Also note, Server 2012 will allow you to have up to 2 VMs without extra cost. If you don't care and can handle only 5 db on the exchange 2010 (transitional Exchange) you could use a trial version for the migration which give you 180 days license.
Here are some links to help you more, with some step-by-step guidance. Please read them carefully before you start:
Adding Server 2012 to a 2003 environment:
http://blogs.technet.com/b/canitpro/archive/2013/05/05/step-by-step-adding-a-windows-server-2012-domain-controller-to-an-existing-windows-2003-network.aspx
AD Migration from 2003 to Server 2012
http://blogs.technet.com/b/canitpro/archive/2013/05/27/step-by-step-active-directory-migration-from-windows-server-2003-to-windows-server-2012.aspx
Migration from Exchange 2003 to 2010 (Transition)
http://www.petenetlive.com/KB/Article/0000234.htm
Migration from Exchange 2010 to 2013 (3 parts article)
http://www.petenetlive.com/KB/Article/0000788.htm
Install a new server (2008 or 2012, they could be trial and/or VMs) as a member.
Install Exchange Server 2010 (could be also trial)
Create new dbs
Install Certificates
Migrate mailboxes from 2003
Migrate shared folders (if any) from 2003
Re-direct mail flow to 2010 (DNS A and MX record, firewall, etc.)
Remove Exchange 2003
Install a new server (2008 or 2012)
Install DHCP, DNS, AD GC roles
Transfer FSMO role to new Server
Transfer Scripts to new Server
Remote SBS 2003
Install a new server as a member.
Install Exchange Server 2013.
Create new dbs
Migrate Certificates
Migrate mailboxes from 2010
Migrate shared folders (if any) from 2010 (not recommended)
Re-direct mail flow to 2013 (DNS A and MX record, firewall, etc.)
Remove Exchange 2010 and Server 2012 (box or VM)
Please note that you will need 3 machines to complete the migration, this machines could be full hard metal or VMs or a combination. Also note, Server 2012 will allow you to have up to 2 VMs without extra cost. If you don't care and can handle only 5 db on the exchange 2010 (transitional Exchange) you could use a trial version for the migration which give you 180 days license.
Here are some links to help you more, with some step-by-step guidance. Please read them carefully before you start:
Adding Server 2012 to a 2003 environment:
http://blogs.technet.com/b/canitpro/archive/2013/05/05/step-by-step-adding-a-windows-server-2012-domain-controller-to-an-existing-windows-2003-network.aspx
AD Migration from 2003 to Server 2012
http://blogs.technet.com/b/canitpro/archive/2013/05/27/step-by-step-active-directory-migration-from-windows-server-2003-to-windows-server-2012.aspx
Migration from Exchange 2003 to 2010 (Transition)
http://www.petenetlive.com/KB/Article/0000234.htm
Migration from Exchange 2010 to 2013 (3 parts article)
http://www.petenetlive.com/KB/Article/0000788.htm
@hecgomrec
Well yes, but this doesn't meet his requirement to be in a new AD domain.
Now he could do Step 2 (New DC and new Exchange Server in the same domain, running Std Edition) and get the domain and Exchange off of SBS.
The do clean installs for Part 3 in a new AD domain. Then setup trusts between the original domain and the new domain to allow for moving mailboxes and data to the new domain boxes.
And granted you could use trial software for most of this but there's a lot of hardware required to go this route.
Well yes, but this doesn't meet his requirement to be in a new AD domain.
Now he could do Step 2 (New DC and new Exchange Server in the same domain, running Std Edition) and get the domain and Exchange off of SBS.
The do clean installs for Part 3 in a new AD domain. Then setup trusts between the original domain and the new domain to allow for moving mailboxes and data to the new domain boxes.
And granted you could use trial software for most of this but there's a lot of hardware required to go this route.
@realtimer:
I don't think is fair to choose your answer from 2 options suggesting you to do something you expressed is messy and you already had bad experience with.
As I suggested, you won't have to change the domain and if you do want to change it you can always do a cross-site migration.
Once again it is frustrating to see you have chosen as your answers the very thing you described as "hard" experience and you were provided with an " appropriate solution " yet you discarded it.
I don't think is fair to choose your answer from 2 options suggesting you to do something you expressed is messy and you already had bad experience with.
As I suggested, you won't have to change the domain and if you do want to change it you can always do a cross-site migration.
Once again it is frustrating to see you have chosen as your answers the very thing you described as "hard" experience and you were provided with an " appropriate solution " yet you discarded it.