Microsoft
Software
Hardware
Network
Question : Exchange Migration - Exchange 2003 - Exchange 2007 - Old Hardware to New Hardware
Hi,
My current setup
1 x Physical Server running - Windows 2003 - Standard Edition Server (DC), Exchange 2003 Standard Edition.
1 Head Office with 10 Client Desktops and 7 remote sites dialing in using Terminal Services.
I have purchased a new higher specification server and want to migrate the existing infrastructure to the new hardware with the only software changes being that I will be using Exchange 2007 on the new box.
I would prefer to not have to migrate all the client desktops to a new domain so was thinking of doing the following.
Install New server alongside existing server. DC Promo and then using NTDSUtil move all the FSMO roles to the new server and also the GC.
Once that is completed I'd install exchange on the new server, and then (unknow area) plan on using the mailbox move utility to migrate the mailboxes over to the new Information Store.
Once all mailboxes are back online I'm a little unclear as to what to do with the outlook clients. Will I change change the server name that they are pointing to or should I create new outlook profiles for each user?
My question then is - Do you think my brief overview of the migration plan seems realistic and what would you suggest I do for the outlook clients?
Thanks
Russ
Answer : Exchange Migration - Exchange 2003 - Exchange 2007 - Old Hardware to New Hardware
I do not see any issues with that but if you are going with 64-bit are you going to switch to Exchange 2007 seems like a good time to do that if you are going with 64-bit.
Random Solutions
Revoked Certificates publication issue
Find and open a PDF file with Access 2009
i copied the mddata file from 1 exchange server to another, mounted the mailbox file, but can't see my mail
Outlook 2007 won't connect to my Exchange 2010 server using Outlook Anywhere
Toolbars and menu bar not visable after restore
WinXP Offline Files - Disaster Recovery
Macrovision Setup will not run proprly
Printing from .NET Windows Service - Object reference not set to an instance of an object
Difference between Server 2003 Appliance edition and server 2003 R2
Windows Script Control component