wfninpa
asked on
Exchange 2003 SBS to Exchange 2010 best way?
I have Exchange 2003 SBS. I want to move just the Exchange functionality to our new server which will have Server 2008 R2 x64 with Exchange 2010 x64.
What would I have to do in order to keep SBS like it is and setup the new server to just take care of email?
I found this guide http://milindn.files.wordp
What is the safest method that will allow instant rollback if anything goes wrong?
What would I have to do in order to keep SBS like it is and setup the new server to just take care of email?
I found this guide http://milindn.files.wordp
What is the safest method that will allow instant rollback if anything goes wrong?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi
@cgaliher you are right. This is only for migration from SBS to Exchange.
And move SBS to Exchange and stick with the SBS is not recommended.
If this is the option from the asker, then I do not recommend apply this.
Jail
@cgaliher you are right. This is only for migration from SBS to Exchange.
And move SBS to Exchange and stick with the SBS is not recommended.
If this is the option from the asker, then I do not recommend apply this.
Jail
ASKER
Okay. Everything is very clear now. I have always hated how you couldn't do trusts with SBS.
I guess I am going to retire SBS. I only have about 30 users anyway, 12 of which are in the office and the other 18 are just email users.
Instead of all of the convoluted migration couldn't I just use Exmerge for any users below 2gb, Outlook 2003 or greater for users above 2gb to make .pst files for importing and just make a copy of the users data (any way to copy their desktop profile to preserve the desktop and preferences) and put that to the side for a couple hours.
Then setup Server 2008 as a DC with Exchange 2010 while not connected to the LAN and create my users, unplug the SBS 2003 Server, plug in the new Server 2008 DC with Exchange 2010, join the 12 machines to the network, setup their Outlook clients, import their .pst files, and put their user files back.
Wouldn't that be less convoluted in my case?
I guess I am going to retire SBS. I only have about 30 users anyway, 12 of which are in the office and the other 18 are just email users.
Instead of all of the convoluted migration couldn't I just use Exmerge for any users below 2gb, Outlook 2003 or greater for users above 2gb to make .pst files for importing and just make a copy of the users data (any way to copy their desktop profile to preserve the desktop and preferences) and put that to the side for a couple hours.
Then setup Server 2008 as a DC with Exchange 2010 while not connected to the LAN and create my users, unplug the SBS 2003 Server, plug in the new Server 2008 DC with Exchange 2010, join the 12 machines to the network, setup their Outlook clients, import their .pst files, and put their user files back.
Wouldn't that be less convoluted in my case?
Honestly, as described, just *reading* your way sounds more convoluted. But yes, that would work, in theory. Keep in mind that this will be a new domain with new user accounts so "putting their user files back" is not as trivial as it sounds. It will involve taking ownership, copying, resetting ownership, and if you have *any* shared files, setting up new security groups to match, reproducing those permissions as well, and hoping you don't miss anything.
Or you can migrate and thus preserve all.
Which sounds less convoluted?
-Cliff
Or you can migrate and thus preserve all.
Which sounds less convoluted?
-Cliff
ASKER
Know exactly what to do the right way now. Thank you.
This article you can check how to migrate from SBS2003 into 2010
Check and see if it helps
https://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_2881-Migrate-Small-Business-Server-2003-to-Exchange-2010-and-Windows-2008-R2.html
Jail