A
Ace Fekay [MVP]
In
Sure you can.
During an off-production day (such as a weekend), move DNS first to the
other server. Whatever method you use would be fine to do this. If the zone
is AD Integrated, then that's even easier. You can also use the
Primary/Seconday method and let the transfer happen then make it a Primary.
Once you;ve done that, then change the IP addresses first of the two DCs.
Swap them. Then in DNS make sure the IP change is reflected. If not, you can
manually force registration for IP and SRVs:
ipconfig /registerdns
net stop netlogon
net start netlogon
This will allow now all your clients to use the same DNS IP.
Then to remove the DC, best practice dictates to manually move the FSMO
roles to the other DCs. If the server you want to get rid of is the GC, move
that to another server FIRST. DCPROMO will actually move the FSMO roles for
you, but may not optimize their locations for you. If you need more info on
optiomization, post back.
Then once all that is done, and confirmed that the FSMO roles (if you did it
manually) have been moved to the other servers, then run DCPROMO and demote
the machine properly. If you don't demote it properly, other errors *WILL*
occur.
--
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
uzi-m said:
Sure you can.
During an off-production day (such as a weekend), move DNS first to the
other server. Whatever method you use would be fine to do this. If the zone
is AD Integrated, then that's even easier. You can also use the
Primary/Seconday method and let the transfer happen then make it a Primary.
Once you;ve done that, then change the IP addresses first of the two DCs.
Swap them. Then in DNS make sure the IP change is reflected. If not, you can
manually force registration for IP and SRVs:
ipconfig /registerdns
net stop netlogon
net start netlogon
This will allow now all your clients to use the same DNS IP.
Then to remove the DC, best practice dictates to manually move the FSMO
roles to the other DCs. If the server you want to get rid of is the GC, move
that to another server FIRST. DCPROMO will actually move the FSMO roles for
you, but may not optimize their locations for you. If you need more info on
optiomization, post back.
Then once all that is done, and confirmed that the FSMO roles (if you did it
manually) have been moved to the other servers, then run DCPROMO and demote
the machine properly. If you don't demote it properly, other errors *WILL*
occur.
--
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory