How do I move Exchange 2010 to a new IP subnet and new site?

I need to "migrate' my entire network to a new IP subnet. This includes a Windows Server 2003 R2 running AD and Exchange 2010 running on Windows Server 2008 R2. This is the only Exchange server on the network and it is running all 3 roles. I don't know if it makes a difference but I have a SonicWall NSA 2400 that is running anti-spam for this server. Here is what I tried:
1. Dismounted the Exchange databases and set them to start manually.
2. Set all Exchange Services to start manually (but did not stop them).
3. Shut down the junk store on the Exchange server.
4. Created a new AD site on the 2003 R2 AD server.
5. Activated DHCP scope.
6. Changed the IP address on the 2003 R2 AD server and moved it to the new site.
7. Flushed & registered the DNS cache on the AD server. (it did show in DNS with the new IP)
8. Rebooted AD server just to be sure
9. Changed the IP address on the Exchange server.
10. Flushed & registered the DNS cache on the Exchange server and waited for it to show in DNS.
11. Rebooted the Exchange server.
12. Checked connectivity between AD server and Exchange server (ping, etc.) and everything worked fine.
13. Manually started the Exchange services, starting with MS Exchange Active Directory Topology (it took a while but it did start)
14. Tried starting the other services manually and of the 18 that needed starting, 10 failed to start.
                      MS Exchange Address Book-error 1067
                      MS Exchange EdgeSync-error 1053
                      MS Exchange Information Store-error 2415
                      MS Exchange Mail Submission-error 1053
                      MS Exchange Protected Service Host-error 1053
                      MS Exchange Replication-error 1053
                      MS Exchange Service Host-error 1053
                      MS Exchange System Attendant-error 1053
                      MS Exchange Throttling-error 1053
                      MS Exchange Transport-error 1053
I know that the 1053 errors are essentially a timeout error but I'm not sure what was causing the timeout.  I couldn't find any direct correlation between service dependencies. Since the services would not start, I did not attempt to mount the databases.
I was able to retreat back to the previous IP/site settings and the Exchange server did recover after about 15 minutes. When I retreated back, the services would not start right away, but after starting the Topology service and then waiting, everything started back up (Happy Dance!)

I have been told by a contractor that an IP migration is possible with Exchange 2010, so now I need to know what I'm doing wrong (or missing) because I'd rather do this in house.

Thanks in advance for your help!
cella9533Asked:
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 GuideCommented:
For the time being what you do is to assign old IP as an additional IP to the domain controller and Exchange.
http://www.rackspace.com/knowledge_center/article/how-to-configure-additional-ip-addresses-in-windows-2008.
And restart exchange and check first.
If that is working we will continue to next step of changing IP


Remove old IP of DC first.
Then clear all the DNS entries of old IP of DC from DNS server. Configure the new DNS IP on exchange server network card as Exchange requires correct DNS IP to function properly and check it finds DC or no. Clear the DNS cache from exchange server by running "ipconfig /flushdns" . Check Exchange is working fine(i.e. check exchange services). if doesn't work run  "ipconfig/registerdns" from the DC and restart exchange or restart MS Exchnage AD topology service. It should work after a restart of exchange. Ensure you change the DNS IP on all clients.

Normally exchange will find the DC and connnect. Remove remove the DNS entries of Exchange old IP from the DNS server, remove old IP from Exchange server network card and see the servces, if it doesn't run type this command  "ipconfig/registerdns" to be sure that exchange name is registered in DNS.  http://social.technet.microsoft.com/Forums/exchange/en-US/1fd70f02-294f-4be1-99f5-ca104f704a46/changing-cas-server-ip-address?forum=exchangesvrgeneral
Make sure you change the NAT in firewall/route and receiving emails

Please check this as well
http://www.zerohoursleep.com/2010/01/5-things-to-consider-when-changing-the-ip-of-an-exchange-server/

If you have a DHCP server you just change DNS server IP in DHCP scope so it will get changed on all clients automatic provided your client's IP not configured manually.
0
cella9533Author Commented:
MAS,
Thank you for the information. However, the second link refers to changing the IP address but not the AD site. The last link refers to just changing the IP address and not changing the subnet or AD site. It seems that changing the subnet and/or site adds complexity to the situation. Given this information, do you think that adding the second IP will resolve the issues I am experiencing?
0
MAS (MVE)EE Solution GuideCommented:
Adding a second IP just to keep your mail flow.
If mail flows then you can work on the changing IP under the same default site. if it works with new IP, then create another AD site for the new network/subnet.
0
Introducing the "443 Security Simplified" Podcast

This new podcast puts you inside the minds of leading white-hat hackers and security researchers. Hosts Marc Laliberte and Corey Nachreiner turn complex security concepts into easily understood and actionable insights on the latest cyber security headlines and trends.

cella9533Author Commented:
I have concerns with this approach since it doesn't seem to address the actual problem of the Exchange services starting once the server has to connect to the AD server in the new site.
0
MAS (MVE)EE Solution GuideCommented:
You should have one AD  server in the new site and tag your exchange to that AD server.
0
cella9533Author Commented:
I only have one AD server, which I moved to the new site. How do I tag the exchange server to that AD server?
0
cella9533Author Commented:
I determined that the issue was being caused by DNS, specifically the Reverse Lookup Zone. It has been resoved and the migration to the new IP subnet was successful.
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
cella9533Author Commented:
The solution was not provided by another participating expert.
0
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.

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.