Deploying new VCF/VVF instance fails at the final validate and deploy stage

Products

• VMware vCenter Server

Issue/Introduction

• Deployment of a new VCF/VVF instance fails at the final validate and deploy stage with an error "The vCenter Server virtual machine is not connected to a distributed virtual port group or the dvpg has an association with non-management traffic type". Below screenshot confirms what it looks like in the installer UI.
  
  
  
  
• An existing vCenter Server is converged into the VCF/VVF and is connected to a standard switch.
  
  
• Migrate VMs from the Standard switch port group to the Distributed switch port group.
  
  
  Beginning of Expandable row content Screen reader table commands may not work for viewing expanded content, please use your screen reader's browse mode to read the content exposed by this button
   Error while migrating the VMs from port group network-## to dvportgroup-## Reference Token: ######

   A problem has occurred on the server. Please retry or contact the service provider and provide the reference token. Reference Token: ######

   A problem has occurred on the server. Please retry or contact the service provider and provide the reference token. Reference Token: ######

Environment

VCF 9.x

Resolution

1. Migrate the vCenter Server VM from Standard to Distributed Switch. The detailed instructions on how to perform the same can be found here- Migrating from Standard to Distributed vSwitch

Points to consider before migrating the vCenter VM to a Distributed Switch:

1. Migrating the Virtual Machine from a standard to a distributed switch also requires migrating the physical adapters. If the physical adapter that serves as an uplink to the Virtual Machine network also serves as an uplink to the management network of the ESXi Host, migrating it without a redundant NIC can cause the Host to become completely unresponsive, and the host network will have to be restored from the DCUI.  
2. In the best-case scenario, these changes are invalidated and rolled back automatically; however, until they are rolled back, the vCenter Server can go down or become unresponsive. Ensure a redundant NIC for the host's management network before proceeding with the migration.