We had a failing domain controller which holding PDC FSMO role, and lots of services (firewall, proxy, application authentication...) depend on its dns name or ip address.
We cleaned up, its metadata from NTDSUTIL, DNS and every possible location. But we were not to promote a newly created vm ad a new domain controller, with same name, and same ip address.
We find too, that in repadmin /replsum, we still find a trace of this failed domain controller, (1722) The RPC server is unavailable.
We tried to promote the new vm with another vm, and same ip adderss, and it didn't work. As if the metadata cleanup is not completely successful.
On internet, i found that there might be some stale objects in ADSI, configuration partition, LostAndFound folder, cleared that folder, but still the same thing.
I'd like if anyone can give me a hint or steps to do that might help to bring things up and running again.
Thank you in advance,