Friday, March 01, 2013 6:50 PM
I am planning to change our Network IP range from the existing one.
We have Two 2008 R2 Dcs with 1 Exchange server 2010.
One of the DC We are running all the roles.
Now i am looking for the steps to change the IP range.
Friday, March 01, 2013 7:02 PM
you have to be more specific. What is your range now, what do you want to change it to. Why do you want to change it , ie what purpose. Do you use DHCP etc.
Sunday, March 03, 2013 11:52 AM
BEFORE starting check with the support tools(dcdiag, reapdmin, dnslint) that no errors exists.
Changing the ip addresses is not complicated. Please start with the DCs that are also DNS servers first and then go on with Exchange on all other machines.
After changing the ip address run ipconfig /flushdns and ipconfig /registerndns then check the DNS zone records that the new ip addresses are listed, then go on with the other DCs and run the ipconfig commands again, then do the other machines the same way.
Do not forget to change the subnets in AD sites and services for the new ones also. Additional check if switches/routers are set correct and if you use DHCP relay on them with ip helper addresses change them also.
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://msmvps.com/blogs/mweber/
Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
Sunday, March 03, 2013 3:28 PM
I would agree with Meinolf.
Changing the IP addresses is not complicated but it may cause long downtimes and complications if it is not properly handled.
First of all, I would highly recommend doing it out of Business Working Hours.
Once done, you will need to check that DCs and AD replication are in healthy status and this should be the same also from Exchange side. Before switching the IP addresses, you need to identify the client computers and servers that are not DHCP clients and are using static IP configuration. For these servers and clients, you need to update them manually after switching the IP addresses.
After switching the DCs, please proceed like the following:
- Make sure that each DC points to the other one as primary DNS server
- Make sure that each DC points to its private IP address as secondary DNS server
- Make sure that each DC points to 127.0.0.1 as third DNS server
Once done, run ipconfig /registerdns and restart netlogon on each DC so that DCs will register their new DNS records. I would recommend doing a check on your DNS zones to be sure that only the new DNS registrations for DCs were kept (Old DNS records for DCs should be gone and if not, please remove them manually).
As Meinolf mentioned, don't forget to update your AD sites and subnets configuration.
Warning! Any application or script that is querying the DCs with their IP addresses will fail after the switching.
This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
- Marked As Answer by Cheers ZHANGMicrosoft Contingent Staff, Moderator Friday, March 08, 2013 2:00 AM