Moving Domain Controller to another box.
Hi, we need to move a DC from one box to another.
The DC2 has also DHCP and WINS servers running.
There is anotehr , working DC (named DC1)o n the network that is working , serving clients and repricating with DC2.
What is the best prattice to perform the move without (m)any complications?
I plan to:
1.Promote the new box to a domain controller ( let's say DC3).
2.Stop DHCP service on DC2 ( DC1 is also a DHCP - it will serve the clients)
3.Stop the WINS on DC2
4.Transfer to DC1 any server roles that DC2 might have.
5.After replication is finished , demote DC2.
What am i missing? Any suggestions for a better plan/strategy?
What do I do about transfering the DHCP and wins services?
How do I let the new DC3 know about address leases , reservations etc. that existed on DC2?
I appreciate your input.
Thank you.
The DC2 has also DHCP and WINS servers running.
There is anotehr , working DC (named DC1)o n the network that is working , serving clients and repricating with DC2.
What is the best prattice to perform the move without (m)any complications?
I plan to:
1.Promote the new box to a domain controller ( let's say DC3).
2.Stop DHCP service on DC2 ( DC1 is also a DHCP - it will serve the clients)
3.Stop the WINS on DC2
4.Transfer to DC1 any server roles that DC2 might have.
5.After replication is finished , demote DC2.
What am i missing? Any suggestions for a better plan/strategy?
What do I do about transfering the DHCP and wins services?
How do I let the new DC3 know about address leases , reservations etc. that existed on DC2?
I appreciate your input.
Thank you.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
No offence Dushan but what on earth has a Certificate Authority got to do with moving a system from one DC to another? Have you made this post in error?
There is a plethora of information here. I am sure there is a document buried in there that will show you the exact step-by-step procedure. Unfortuantely I cannot research this for you right now because I have to run inro a meeting. Good luck!!
http://labmice.techtarget.com/activedirectory/dc.htm
ASKER
Thanks for your detailed input keith,
but we already have the DHCP scope split between dc1 and dc2 like that DC1 -: x.x.x.127 and the other one Dc2 - from .127 to .254.
If we backup the old Dc2 DHCP database( dhcp.mdb) and then restore it on the new one( DC3) would that be ok ?
Would reducing the address lease time to , lets say, 1 hour ( just for a short time) be helpful ?
but we already have the DHCP scope split between dc1 and dc2 like that DC1 -: x.x.x.127 and the other one Dc2 - from .127 to .254.
If we backup the old Dc2 DHCP database( dhcp.mdb) and then restore it on the new one( DC3) would that be ok ?
Would reducing the address lease time to , lets say, 1 hour ( just for a short time) be helpful ?
i would not use the backed up .mdb file, I'd recreate it on the new server.
Reducing your lease time down to one hour is a good idea. I assume you are doing this work out of hours in which case if someone should log on they will get a lease from your other DC. It shouldn't be that big a deal for you in truth.
Reducing your lease time down to one hour is a good idea. I assume you are doing this work out of hours in which case if someone should log on they will get a lease from your other DC. It shouldn't be that big a deal for you in truth.
Thank you :)
http://support.microsoft.com/?kbid=298138
Backup the CA Configuration,
Uninstall the CA,
Do the Domain Rename,
Install the CA,
Restore the CA Configuration.