Changing internal IP address range in an Active Directory Network with Exchange on site

OK, here is my position:

I have a customer who is running nice and smoothly on internal ip address range 192.168.1.x but along comes a company who has purchased my customer's business and wants me to change the ip address range as it will conflict with one of their other sites. The ip address range needs to be changed to 192.168.2.x.  To be honest the range is irrelevant but what is relevant is that this customer has two Domain Controllers and an Exchange on site server.  Can someone give me the correct working procedure for this exact scenario i.e. what needs to happen and when please?

My initial thoughts were to change the DCs IP addresses and update DNS on both DNS servers then change the IP address on the Exchange box and re-boot it but I am very nervous about doing so as it all sounds a bit too easy using this process.

They are running a mixed mode Domain with a 2003 and a 2008 R2 Domain controllers with Exchange 2010 sitting on 2008 R2.

I have already have the port forwarding on the new router and also the MX record change in hand.

Any guidance would be appreciated.

Thanks Rob
rob1210Asked:
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.

Steven WellsSystems AdministratorCommented:
Hi,
It will take a bit of effort, but if you change your primary DC first,  update DNS and Name Servers tab on DNS. Check internet working, routing etc. Then all other Domain Controllers.

then change each host's IP address, checking IP works throughout.

Change DNS settings on each host as you migrate.
Then you change DHCP scope and settings.
Rebooting workstations will deploy new IP address range and DNS settings.

Also think about any printers or fixed hosts that may have static IP addresses.

Think also about any firewall rules that reference old subnet.

Good planning should mean you can migrate subnet fairly easy as much of your information should be dynamic in DNS.

Hope this helps
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
rob1210Author Commented:
Many thanks for the reply Steven and it did help confirming my solution already
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
Network Management

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.