TIL, the key to smooth transition from windows vCenter to VCSA is making sure the windows vCenter is solid and simple. Back before the upgrade to 6.0 (U3), I went through and cleaned up any/all extensions/plugins/WTF that were giving off error alerts in the GUI.
That included a non removable Nexus 1000v install.
While the migration took some time, everything went by the book. Woulda been faster on faster storage, but that's always how it goes.
Do you have links to a doc on how to purge 1000v if it's been left as artifacts because I have one.
Same old extension removal through the MOB interface on the vcenter's webgui was enough for me after doing all the uninstalls, luckily.
Then when I did the individual host upgrades, I actually saved the host profiles and did clean installs.
That was to confirm any file bits were gone from the hosts.
----
EDIT: So, it looks like even though I told it to only install a PSC, the PSC somehow started acting like the vCenter and grabbed the licenses and other bits. So when the vcenter was reinstalled on the old windows VM, it acted as though the licenses were already in use and so forth.
Shutting down and deleting the old VMs seems to be the only way forward, since I can't restore easily since commvault was reliant upon vcenter in the vm backup/restore scenario.
The DR time lagged copy did fire up, but turns out the local admin password isn't what I thought it was and that was going to be a different fight to get it to boot from an external ISO.
So, forget it.
Nuke and pave on vcenter and go straight to VCSA plus PSC in preparation for 6.5, which will have to wait until the commvault is upgraded to v11.
Some fiddling will be required to get things back where I like them, but most of the settings appear to be preserved on the hosts, so that's more than plenty.
The alternative was waiting for 6+ hours for the backup to restore, assuming I got that working.