• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 302
  • Last Modified:

Movement of DC & Exchange servers

We are planning to move our DCs (Server 2008 R2) & Exchange servers (Exch 2010 SP3) to another Datacenter with different IP addresses & subnets.

What are the precautions need to be taken and what would be the impact after movement of DCs & Exchange. Kindly advice.
0
sanjayambre
Asked:
sanjayambre
  • 3
  • 2
3 Solutions
 
Red-KingIT ManagerCommented:
For the DC, I would recommend that you Promote a new DC with an IP address based on the new addressing scheme. Place it in a new Site in Active Directory Sites and Services. This Site should have the IP addressing scheme associated with it. Also take note of the replication frequency for domain information. By default this is longer between DCs in different sites than if the DCs were in the same site.
Once the new DC is in place and replicating changes you can then transfer the FSMO Roles to the new DC.
Once done you can then demote the existing DC and remove it from the domain.

I'm not familiar enough with exchange to suggest a migration strategy but a similar approach could be taken.
0
 
Jamie McKillopIT ManagerCommented:
Hello,

The first thing you need to do is create a new site in AD Sites and Services. You need then need to associate the new subnet with the new site. Assuming you are just packing everything up and moving it all at once, you would power up the first DC, re-IP it then reboot. Do the same with the other DCs. Once your DCs are up and you have verified there are no AD errors, you can start powering up and re-IPing your Exchange servers. If you have your roles separated, start with the CAS and HT servers before the mailbox servers. If you have your Exchange servers in a cluster, there will be additional steps.

If you have any receive connectors that are scoped by IP, you will need to change the IPs or subnets to the new ones.

You also need to make sure you change your MX records to point to the new IPs ans you need to make sure there is a PTR record for the public IP your Exchange servers are NAT'ed out as.

-JJ
0
 
sanjayambreAuthor Commented:
Thanks....it means that we can change the IP address for one DC initially and after rebooting, it will start communicating  with other DCs in site.

So IP addresses are not hardcode in any directory partitions or AD database, right?
0
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.

 
Jamie McKillopIT ManagerCommented:
No, IPs are not hard coded. When the server reboots, it will update DNS with the new IP. You will need to update the DNS servers on the TCP/IP properties of any servers or other systems with a static IP, including the DCs. You will also need to make sure your DHCP server at the new site is handing out the new IPs of the DNS servers.

-JJ
0
 
sanjayambreAuthor Commented:
Thanks JJ, will this applicable for exchange servers also.
0
 
Jamie McKillopIT ManagerCommented:
Yes.
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now