The steps are okay.. Ensure the ESXi hardware is supported to go for 6.7 before attempting to upgrade..
Step 1 and step 3, you can pick anyone as per your choice as end result is same..
If I were you, I'd definitely go with the vCSA in step 1. IMO migrating directly to the vCSA makes life a lot easier. No hassle with all the required upgrades/patches on a Windows platform which may include Windows Server version, SQL Server, Update Manager, ...
In case Update Manager is involved, I'd even consider to migrate to vCSA 6.5 U1 in step 1.
You must transition to 6.0 or 6.5 first. For more information see this:
Please consider marking this answer "correct" or "helpful" if you think your question have been answered correctly.
Thank you for suggestions, but currently I'm stuck during the process to upgrade from VCSA65 to VCSA67.
The migration from WINVC55 to VCSA65 went well and after ESX55 to ESX65 using the Update Manager.
The ESX wich is hosting the VCSA (previously WINVC) is on a network (192.168.100.22) while the VCSA is on another network (172.16.0.10): the VCSA don't manage the hosting ESX, but manages other ESX hosts!
During the Upgrade Stage2 process, appears the following error:
Now I don't understant why the VCSA must reach his hosting ESX!?!?!?!? And anyway...how can I solve this problem?? Is there some kind of workaround? Can I add a second nic to VCSA?
Thank you everyone!
Does routing work between the VLANs? Do forward and reverse lookups of all hosts and the vCSA work from both VLANs?
Of course not... they are on different network and the network are not routed.... I don't understand why the VCSA should reach the hosting ESX!? Is that a bug???