Replace Exchange 2003 server with Exchange 2010 Server
We are installing a 2008 member server with exchange 2010 into a 2003 domain. Currently have one exchange 2003 on a 2003 member server with no front end. Once 2010 is completely installed and setup correctly, we want to completely replace the Exchange 2003 server without too much hassle. Here are my questions:
- Can we move over all mailboxes to new server and disconnect old server, then rename the new server with the old servers name & IP?
- What is the fastest and easiest way to move over mailboxes?
- Can we move the SSL certificate that the old server had to the new server?
- What is the best way for Outlook 2003 and 2007 clients to get connected with the least amount of interruptions?
I am currently following the link below starting from step 6: (we do not have a SBS, but I have yet to find a better step by step link)
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
- Can we move over all mailboxes to new server and disconnect old server, then rename the new server with the old servers name & IP?
- What is the fastest and easiest way to move over mailboxes?
- Can we move the SSL certificate that the old server had to the new server?
- What is the best way for Outlook 2003 and 2007 clients to get connected with the least amount of interruptions?
I am currently following the link below starting from step 6: (we do not have a SBS, but I have yet to find a better step by step link)
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
Or you can join your new server to the domian and use exchange tools to move mailboxes to the new server.
Then give your new server a DNS alias of your old server name. This will allow clients configured for the old server to get mail from the new server. This should give you very little down time.
I'm not sure about exchange 2010 but 2007 had a tool to move mailboxes on a schedule over night.
Then give your new server a DNS alias of your old server name. This will allow clients configured for the old server to get mail from the new server. This should give you very little down time.
I'm not sure about exchange 2010 but 2007 had a tool to move mailboxes on a schedule over night.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
When you move the mailboxes, the outlook client will "know" that the mailbox was moved and the only thing that will happen is, if the outllok was on during the migration, user will get a message saying "administrative change was made. please restart outllok",.... easy win.. i think.. in my opinion forget the "same name" idea...
ASKER
Thanks everyone,
LTCexpert: making the alias would work?
LTCexpert: making the alias would work?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
DNS Alias will work. But the autodiscovery sounds like a much cleaner way around the issue to me.
ASKER
Thanks guys, I really appreciate everyone's input and will try my best to make this as painless as possible for myself... haha
If the name of the server needs to be changed, I was most worried about having to change MX Records as well as internal DNS records which sometimes can be a time consuming wait. Oh well-
If the name of the server needs to be changed, I was most worried about having to change MX Records as well as internal DNS records which sometimes can be a time consuming wait. Oh well-
It would probably be best to export all of the mailboxes first, then copy them to the new server and import them. You could do this with Exmerge, OR you could use an Outlook client to export all emails to PST files which you could then import.
There should be no reason why the new server can't have the same name and IP as the old server, but it's best to configure it with these details from the outset, and only attach it to the network once the old server is off.