I recently performed the following change in my environment:
Created a new VM called DC2.dc.local and promoted it to domain controller and installed the DNS role.
Migrated all FSMO roles over to DC2.dc.local.
Ran dcpromo on DC1.dc.local and demoted it to member server and removed the DNS role.
Powered off DC1 and reimaged DC1.dc.local (it's gone and never coming back).
I have updated the clients to use DC2.dc.local's IP address as the primary DNS. DNS resolution is working from all hosts, I have all hosts can ping one another. I was repeatedly getting and error stating "Authorize Exception" when I attempted to log in to vCenter with "Use Windows session credentials", or I would get a standard error stating that the username or password is incorrect.
Did you find a solution?
We have exactly the same prerequisits and exactly the same problem.
After the old DC was removed VCenter no longer works.
Strange enough. AD is healthy and all other services like Exchange, SharePoint, MSSQL work without a problem.
Why is VCenter still referencing the old DC which no longer exists?
Seems that it is hard coded anywhere in VCenter configs during install.
Regards.