piedthepiper
asked on
Demoting a DC and creating another
Basically a VM that is a DC (dc002) seems to have a corrupt VMDK file. The VM is up and functioning fine. You cant vmotion/svmotion it, cold clone it, clone the vmdk file or anything. They all fail with errors for the vmdk and vmware support are being pretty slow with helping
So the plan I have is to:
1. Demote the DC (dc002) using DCPROMO and then remove it from domain and power off
2. Create a new DC (dc004) with a new name and give it the same IP as the old demoted DC (dc002) and the do DCPROMO to promote it.
I have already created dc003 and its fully functioning and dc001 is a physical DC and is the PDC. It is a 2008 Domain
Am I missing anything?
So the plan I have is to:
1. Demote the DC (dc002) using DCPROMO and then remove it from domain and power off
2. Create a new DC (dc004) with a new name and give it the same IP as the old demoted DC (dc002) and the do DCPROMO to promote it.
I have already created dc003 and its fully functioning and dc001 is a physical DC and is the PDC. It is a 2008 Domain
Am I missing anything?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
When you demote it using dcpromo, it should clean everything up for you? I will double check its dns records are removed and give it a while to replicate across.
DC001 holds all the roles, and they all partake in DNS, the reason for using the same IP as dc002 for dc004 is in-case there are some machines out there using it for DNS
DC001 holds all the roles, and they all partake in DNS, the reason for using the same IP as dc002 for dc004 is in-case there are some machines out there using it for DNS
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Oh absolutely the clients use more than one dns server.
So the manual tidy up is the preferred option these days. The whole meta data cleanup?
So the manual tidy up is the preferred option these days. The whole meta data cleanup?
We prefer the manual approach, because often dcpromo fails.
ASKER
With The manual approach with 2008 you can do the metadata cleanup via the gui, Well that's my understanding anyway, so it should be pretty painless.
https://technet.microsoft.com/en-us/library/cc816907(v=ws.10).aspx
https://technet.microsoft.com/en-us/library/cc816907(v=ws.10).aspx
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Multiple solutions were followed.
I demoted the dc using dcpromo, it failed first due to FRS service not running ,enabled that and then tried again it demoted fine. I went thoruhg the GUI and made sure all references in AD for the DC were actually removed and double checked all DNS entries were removed.
I forced replication using repadmin, and waited a bit and then promo toed the new one, with the same IP. I ran dcdiag /v and repadmin /showrepl and all is well.
I demoted the dc using dcpromo, it failed first due to FRS service not running ,enabled that and then tried again it demoted fine. I went thoruhg the GUI and made sure all references in AD for the DC were actually removed and double checked all DNS entries were removed.
I forced replication using repadmin, and waited a bit and then promo toed the new one, with the same IP. I ran dcdiag /v and repadmin /showrepl and all is well.
and then create a new DC, and seize the roles, and then create a new DC, and seize the roles/transfer to this new machine.
and then do not power on the old DC, and force remove from AD to clean up.
do not use any old names.