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?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Hypercat (Deb)Commented:
As long as you make sure that all of your FSMO roles are assigned to either dc001 or dc003, as well as DNS and any other network services that have previously been handled by dc002, then you shouldn't have any trouble demoting and removing dc002.

(The article header mentions Windows 2003 but is also applicable to Windows 2008.)
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Personally, I would power off the old DC.

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.
piedthepiperAuthor Commented:
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
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
The reason we do not run dcpromo and demote, is because often it fails, and you are left with a manual tidy up of AD, which we prefer today!

If it does not hold all the roles, there is no big deal, turn off, build a new one different IP Address, and just alter DHCP with the new DNS IP Address!

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

So what!

Anyway, what organisation only uses a single DNS ?

Do you clients not use at least two DNS entries, DC001 and DC002 ?

We would go all new, different IP.
piedthepiperAuthor Commented:
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?
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
We prefer the manual approach, because often dcpromo fails.
piedthepiperAuthor Commented:
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.
Jeff GloverSr. Systems AdministratorCommented:
Just do what you said you wanted to do. you have 2 other DCs and one is the PDC emulator from what you said. When you demote, the FSMO roles automatically move to another DC so don't worry about that. If the demotion fails, then do a dcpromo /forceremoval and then metadata cleanup. Why cause yourself trouble.
  Yes, I have seen DCPromo fail once or twice in the last 15 years (this is doing hundreds of promotions and demotions) but not enough to justify the time it takes to do a proper cleanup, which most people do not do,
  If it is just the vmdk file issues and teh server works fine, you had the process correct in the first place. Of course, it goes without saying, if you have other services on it, move them but.... Why work harder?

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
piedthepiperAuthor Commented:
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.
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
Operating Systems

From novice to tech pro — start learning today.