Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Movement of DC & Exchange servers

Posted on 2014-02-26
6
Medium Priority
?
300 Views
Last Modified: 2014-03-04
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
Comment
Question by:sanjayambre
  • 3
  • 2
6 Comments
 
LVL 9

Expert Comment

by:Red-King
ID: 39888591
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
 
LVL 37

Assisted Solution

by:Jamie McKillop
Jamie McKillop earned 2000 total points
ID: 39888848
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
 

Author Comment

by:sanjayambre
ID: 39891093
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
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
LVL 37

Assisted Solution

by:Jamie McKillop
Jamie McKillop earned 2000 total points
ID: 39891768
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
 

Author Comment

by:sanjayambre
ID: 39891809
Thanks JJ, will this applicable for exchange servers also.
0
 
LVL 37

Accepted Solution

by:
Jamie McKillop earned 2000 total points
ID: 39891814
Yes.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

With so many activities to perform, Exchange administrators are always busy in organizations. If everything, including Exchange Servers, Outlook clients, and Office 365 accounts work without any issues, they can sit and relax. But unfortunately, it…
Eseutil Hard Recovery is part of exchange tool and ensures Exchange mailbox data recovery when mailbox gets corrupt due to some problem on Exchange server.
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses

885 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