Solved

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

Posted on 2014-09-26
10
697 Views
Last Modified: 2014-10-22
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!
0
Comment
Question by:cella9533
  • 5
  • 4
10 Comments
 
LVL 24

Expert Comment

by:-MAS
ID: 40347290
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
 

Author Comment

by:cella9533
ID: 40349891
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
 
LVL 24

Expert Comment

by:-MAS
ID: 40351548
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
 

Author Comment

by:cella9533
ID: 40356786
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
What Should I Do With This Threat Intelligence?

Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

 
LVL 24

Expert Comment

by:-MAS
ID: 40356890
You should have one AD  server in the new site and tag your exchange to that AD server.
0
 

Author Comment

by:cella9533
ID: 40357050
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
 
LVL 24

Expert Comment

by:-MAS
ID: 40358150
0
 

Accepted Solution

by:
cella9533 earned 0 total points
ID: 40387246
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
 

Author Closing Comment

by:cella9533
ID: 40396408
The solution was not provided by another participating expert.
0

Featured Post

Why do Marketing keep bothering you?

Is your marketing department constantly asking for new email signature updates? Are they requesting a different design for every department? Do they need yet another banner added? Don’t let it get you down! There is an easy way to manage all of these requests...

Join & Write a Comment

Resolve DNS query failed errors for Exchange
Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now