FSMO role and metadata cleanup

I have production server running in eval mode. To upgrade license I installed another server on hyper-V of same physical host and transfer all FSMO roles. After transfer repadmin was generating error on main server but it worked fine on secondary server (all these worked fine in lab test).
I tried moving FSMO back but it did not help, therefore, I put FSMO on guest again some worked from pshell, some transfer worked form ntdsutil and some worked from console.
Eventually, I tried removing ADDS form host machine and instead of completely removing it suggested me to make it workgroup and stayed with an alert action as promote to DC.
I removed DC from users and computer container, removed NTDS from AD sites and services but it does not allow me to remove DC name from AD sites services. Tried ntdsutil metadata cleanup and it still does not remove.
Option to make it a workgroup is grayed out and DCpromo /force does work either.
Is there any ways to cleanup from adsiedit or more granular level of cleanup. If hyper-v is the only service running I should be able to able to join it back to domain, as DC on hyperV stars automatically with physical host????

FINALLY IT IS IN WORKGROUP BUT DOES NOT CONNECT TO DOMAIN WHEN I AUTHENTI
LVL 4
pchettriIT DirectorAsked:
Who is Participating?

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

x
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.

pchettriIT DirectorAuthor Commented:
I had used one second ethernet card for hyperV and one for host. When I disabled the one NIC for host it shows as connected as domain instead of workgroup.
Another option is to switch the hyperv to primary network but it says it might change any static IP under the guest which I reluctant to change as guest VM is both DC and DNS
0
pchettriIT DirectorAuthor Commented:
RDP into host using the dynamic IP on second NIC and it was still showing as joined to domain. Unjoined from domain and successfully rejoin to domain doing RDP from first NIC to preserve same IP settings
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
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
Hyper-V

From novice to tech pro — start learning today.