Few more questions about Exchange 2007 -> 2007 migration

I'm preparing myself to move from my current server with Exchange 2007 to new server with Exchange 2007. First of all, I just want to share with you the list of steps I think I should follow, and I have some specific questions regarding it.

1. Install the same operating system - 2008 R2, all patches, AV

2. Install Exchange 2007 SP3 - same as on my old server and patch it to at least the same level as the old one.

3. Export certificate from the old server and import it on a new server and change all URL's on new server to reflect name on the cert.

4. Install GFI MailEssentials on the new server.

5. Configure Public folders replication.

6. Move one mailbox to a new server to test if its working ok.

7. Replicate GFI and Exchange 2007 settings so they will match old server.

8. Tell my firewall that from now SMTP will be going to / from new server.

9. Uninstall GFI and Exchange 2007 on the old server.

Now, there are few things I dont understand, considering that for some time 2 servers will have to coexist:

1. because of this issue - http://www.digicert.com/internal-names.htm - I have a split dns in place so I can use mail.external.com internally. All urls on the old server are set-up to use that external address. Works fine. I'm not sure what will happen with that cert used on a new server while the mail.external.com will still resolve to old server's IP.

2. with both servers having same roles - MB,HT, CAS - what is happening when email is sent by the user with mailbox on the new server - how will the new exchange know to pass it to old server to be sent outside and not directly ? Can't get my head around two identically configured CAS servers - how does it work ?

3. Any other problems with such coexistence ?
LVL 1
tp-it-teamAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MAS (MVE)EE Solution Guide - Technical Dept HeadCommented:
Mail flow is not a problem as Exchange server will communicate each other as long as it is in the same network and organization.


But I strongly suggest you to install exchange 2010 instead of exchange2007.
It is easy for administration and features more in exchange2010
0
tp-it-teamAuthor Commented:
I know that would be logical step but then I would need to buy license and cals.
Any other opinions ?
0
MAS (MVE)EE Solution Guide - Technical Dept HeadCommented:
ok then no worries.

It is a straight forward process. Majority of the configurations are saved in domian controller it will take the domain saved settings automatic.

Make sure you configure GFI properly before mapping external IP to new server

Configure new server as source server in send connector properties .

Move all user mailboxes to the new server and wait for all users login to outlook at least once before shutting down old server.

Move all the system/arbitration mailboxes to the new server.

Move public folders to the new server

Move Offline address book to the new server

Make sure autodiscover.domain.com point to the new server (both internally and externally)

Then shutdown old exchange server for couple of days to check for any errors in the new exchange server and user side errors.

When decommissioning old exchange it will prompt it will prompt you if you missed anything but you have to uninstall from add/remove programs
0
tp-it-teamAuthor Commented:
I know that in general its a simple process but can someone relate to these 2 specific questions I have ?
0
Simon Butler (Sembee)ConsultantCommented:
As you are using two servers that are the same version, this is pretty easy to manage.
Once the new server is setup, configure all the host names to be the same. Don't forget the ones you can only do in the shell.

On the old server, REMOVE the external host names, so that only the internal name is valid. Point all external traffic to the new server. Exchange will then proxy the traffic to the old server from the new one.

For email routing - Exchange knows where the user is and will route it accordingly. The send connector controls that and Send Connectors are org settings, not server.

Simon.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.