The steps and risk in swapping IP address of running 2x domain controller in same AD Site ?

Hi People,

I got 2x domain controller that is currently running:

OldDC2003 (Domain Controller / Global Catalog & DNS): 10.1.3.2
NewDC2012R2 (Domain Controller / Global Catalog, DNS, FSMO role holder): 10.1.3.200

they're both running fine and replicated with each other within the same AD site HQ.

I'd like to swap the IP address into:

OldDC2003 (Domain Controller / Global Catalog & DNS): 10.1.3.200
NewDC2012R2 (Domain Controller / Global Catalog, DNS, FSMO role holder): 10.1.3.2

Because there are lots of firewall and network switch to be changed. So what are the steps that I need to do and the risk involved ?
LVL 9
Senior IT System EngineerIT ProfessionalAsked:
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.

Senior IT System EngineerIT ProfessionalAuthor Commented:
I also have 13 other site offices with AD domain controller and DNS as well, so I'd like to know how it affects the replication if it is possible.
0
Zacharia KurianAdministrator- Data Center & NetworkCommented:
OldDC2003 (Domain Controller / Global Catalog & DNS): 10.1.3.200
NewDC2012R2 (Domain Controller / Global Catalog, DNS, FSMO role holder): 10.1.3.2

Changing the IP of your windows 2012 DC is fine and it is straight forward. But I am not sure of the OldDC2003.

The safe side is to create another DC in windows 2012  with a new IP, and get rid off the OldDC2003.
Then change the IP of the your FSMO holder to 10.1.3.2 and the new DC to 10.1.3.200.

Zac.
0
Senior IT System EngineerIT ProfessionalAuthor Commented:
I was under the impression that I can just swap the IP address on the NIC configuration and then manually update the DNS records accordingly.

Would that cause an issue with Active Directory ?
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.

Zacharia KurianAdministrator- Data Center & NetworkCommented:
Read the below post in EE.

http://www.experts-exchange.com/Software/Server_Software/Active_Directory/Q_26786369.html


You have to  make sure to populate the change of IPs in your other DCs.

Zac
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
albatros99Commented:
To avoid complication, you could point all DC's at the same DNS server so that all DC's are immediately aware of the new IP. Otherwise there could be an issue, especially if you're using AD-integrated DNS. When the DC's point to different DNS servers and you have to wait for replication you create a chicken and egg problem....
0
Senior IT System EngineerIT ProfessionalAuthor Commented:
@Zacharia Kurian: do you mean creating the another server to act as the 3rd IP address or staging IP while the both IP address is currently registered and used by running server ?
0
Senior IT System EngineerIT ProfessionalAuthor Commented:
The Technet article: https://technet.microsoft.com/en-us/library/cc758579%28WS.10%29.aspx somehow only suggest the IP to be changed into another free unused IP address, not the IP address that is in used by another Domain Controller.


So here's what I've been thinking based on your suggestion:

Changing OldDC2003 IP address:
1.      Turn off / shutdown the NewDC2012R2 server & unplug the network.
2.      Change IP address (to match the NewDC2012R2 IP).
3.      Open Command prompt and then run ipconfig /registerdns command.
4.      Restart the NETLOGON service on the current OldDC2003 server.
5.      Open Command prompt and then run dcdiag /fix command.
6.      Check the AD/DNS replication and for any other error.

Somehow, I wonder what could be happening in Steps #2 when the IP address of the OldDC2003 is now the same as NewDC2012R2 from the AD and DNS replication perspective ?

Since both of the IP address are used and registered by the running server, do I need to wait few hours or days before proceeding to the steps below:

Changing NewDC2012R2 IP address:
1.      Turn on the NewDC2012R2 server without the network connection.
2.      Change IP address (to match the OldDC2003 IP).
3.      Connect the network cable to the NewDC2012R2 server NIC.
4.      Open Command prompt and then run ipconfig /registerdns command.
5.      Restart the NETLOGON service on the current OldDC2003 server.
6.      Open Command prompt and then run dcdiag /fix command.
7.      Check the AD/DNS replication and for any other error.
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
Active Directory

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.