iPhones and Exchange 2003

At my job I'm in the process of migrating our Exchange 2003 server from one HP server to another.  I did some testing with my email account and found that the iPhone integration stops working when I move my mailbox from exchange01 to exchange02.  The way things are setup the MX and A records point to the public IP address which is assigned to our Barracuda spam box, and from there it forwards it to Exchange01.  Exchange01 will then check and see which server the mail is on and work accordingly.  So mail works fine, Blackberry phones work fine.  However iPhones don't work at all.  The mail server that the iPhones point to originally is mail.alsformalwear.com, however the new mail server is called exchange02.alsformalwear.com.  The migration is going to take a few days with all the replication and getting everything moved over.  Once it is done I will be uninstalling exchange01 and then renaming exchange02 to exchange01 and changing the private IPs to the IPs that were on Exchange01, so after all that it should be the same and hopefully the iPHones will start working again.  I'm trying to find a way however to keep them working during the migration as most of our iPhone users are VPs and would like to have continued access.  Is there something I should do to get the iPhones to work on both servers at once?
Who is Participating?
Ivan_WindonAuthor Commented:
The issue has been resolved.  I found an article here http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_1798-Exchange-2003-Activesync-Connection-Problems-FAQ.html that talked about the needed changes to get ActiveSync working with the iPhones, and then we had to make a slight change to the ACL on the Cisco firewall.
Schnell SolutionsSystems Infrastructure EngineerCommented:

Do you have just one exchange 2003 server? Or you have a Back End - Front End configuration

It is not a good idea after having Exchange02 ready, to rename it to Exchange01 and use the same IP. There are many associations with the Exchange Server name and you can not just make it like this

If the objective is just to migrate the hardware. You can instal the same Windows version in another hardware using another name to avoid conflict and schedule an offline operation where you take away the original server, and them begin the process of restoring the new one from the data in AD making the process of recover

Another option is prepare the Exchange02 server as a totally a new exchange server into the organization and configure your pointers to use the new server. For example, you shall have a firewall or reverse proxy application that point to the exchange web address of your Exchange01 server, and you shall change this value to the one in Exchange02. It works having both servers at the same time, but confiuring the corresponding parameters during the process of the migration
Ivan_WindonAuthor Commented:
Okay, well it's been quite a while since I did a server migration with Exchange, and it was for a smaller company.  I think last time I just moved the mailboxes to a new server and then removed the old server and then reconfigured the outlook clients to point to the new server.  It will be harder at this company as there are many hundreds of accounts I would have to change as from what I have learned only 2007 and higher outlook clients will auto locate a new exchange server.  Which is why I was trying to keep the new server with the same server name and IP.  

I haven't actually began the migration yet, so there is time for me to change my migration plan.  Is there a document on the web that goes over what you suggested withe the restoring from the data in AD.  What is actually involved in doing this.  I currently have the new server setup with Windows 2003 Standard Server and Exchange 2003.  Exchange01 and Exchange02 both now show up in the management tool.  Neither is set as a front end, they are both just Exchange Servers.  All the mailboxes are still on Exchange01 (except for mine which I was using to test things out and see if everything still worked the way I expected it to).  

The second option is easy enough, however is there a easier way to reconfigure a few hundred outlook clients to point to exchange02 instead of exchange01?  If I can do that then I'll just go that route as I think that would be the easiest method myself.  Changing the mail.alsformalwear.com pointer to the new IP is easy as well, it's just the client configuration that has me worried with that step.
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Schnell SolutionsSystems Infrastructure EngineerCommented:

Yes, it is still supported in the way that you did it a long time ago. You can move the users from your old server to the new one and them configure the user profiles in order to use the new server. And it is true that after Outlook 2007/2010 and Exchange 2007/2010 you can automatize the server name configuration, of course... we are not upgrading to Exchange 2007 or 2010 in this case, so this is not an option

*** A ***

If we use the option of implementing a new Exchange server in the organization with a different name (Like you did it in your previous migration), you can consider one of the following options:

1a. If the movement is within the same Exchange Administrative group and the old server is still up outlook will correct itself and will make the redirection to the new server

2a. If the movement is outside the Exchange Administrative group you can use the Exchange Update Profile Tool (http://support.microsoft.com/kb/873214) in order to automatize the update in the profile

3a. If you take the old server away and just stay with the new one, you can temporally change your dns A/host record for an alias pointing to the Exchange02 server

*** B ***

If you want to stay with the same server name and just migrate to a new hardware and keep all yhe configuration everywhere, follow this procedure:

All the details available in: http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/default.mspx

In short steps it is:

1. Install the Operating System and its service packs of the production server and all the Exchange Prerequisites (asp.net, nntp, smtp, IIS, www, etc)

Note: The server will be installed/configured with the same name and IP but NOT joined in the domain. Possible in a separate network or disconnected

2. Turn Off the Original Exchange Server. Make a RESET of the computer account in Active Directory, connect the new one and joit it to the domain

3. Install Exchange using the DisasterRecovey switch: <ExchangeMedia>\Setup\i386\setup.exe /DisasterRecovery

4. Install Exchange service packs with the DisasterRecovery switch:  <SP_Media>\Setup\update.exe /DisasterRecovery

5. Copy the Exchange Databases to their specific drives, use the same storage or make a complete Data restore

Ivan_WindonAuthor Commented:
Yes, I think I am going to go with the A route and just finish the migration to the new server and then leave it as Exchange02.  We will then just change the clients to point to the new exchange02 server and then remove exchange01 from the network.  

I still have the issues that I started this entire message out with however.  It's good that I found out these other issues as well, however I'm trying to figure out why the iPhones don't work once the email is moved over to Exchange02, they work while they are on Exchange02 just fine.  Any ideas on that one?
Schnell SolutionsSystems Infrastructure EngineerCommented:

Let's see...

Do you mean? ...

1. Your users use iPhones on Exchange01, and when they are moved to Exhcange02 the iphone continues working, but after take way Exchange01 iphones don't work anymore,


2. Your users use iPhones on Exchange01, and when they are moved to Exchange02 the iphones stop working

Please, confirm me which one is the exact case and let me know how you handle the Exchange Publication for ActiveSync from the Internet

Ivan_WindonAuthor Commented:
I wasn't the one who configured it so it would work.  So I'm not 100% sure how we handle the Exchange publication from ActiveSync.  The latter is the case with us.  The phones worked on Exchange01, and when we moved to Exchange02 they stopped working.

My server migration is nearly complete on this end.  The DNS and MX records all point to the new exchange02 server, and all mailboxes have been moved.  Replication should be finished up soon with the public folders, then there is just one step left before I remove exchange01 from the network.  So I hope to have it all done by Tuesday or Wednesday.
Ivan_WindonAuthor Commented:
Thanks for pointing out the issue with my migration.  Probably saved me a lot of headache there.  It wasn't the primary reason for the question, however it turned out to be the most important part.  
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.