VMware Cloud Foundation (VCF) deployment progress in the UI is lost, and the wizard resets to the initial validation phase. This occurs if the VCF Installer appliance is powered down, migrated to a different ESXi host, and powered back up while a deployment is already in progress.
VMware SDDC Manager 9.0.x
VMware Cloud Foundation Installer 9.0.x
VMware Cloud Foundation 9.0.x
Power cycling and migrating the VCF Installer appliance terminates the frontend web service session, causing the UI state to decouple from the active backend domain manager deployment state. The VCF deployment wizard relies on an active session token to track progress. Rebooting the appliance destroys this token, causing the UI to default to a fresh state, even though the backend infrastructure has already been partially deployed.
To restore the deployment state in the UI using a previously exported configuration file:
Access the VCF Installer UI.
Select the Deploy Using JSON Spec option.
Upload the configuration JSON file that was exported prior to the appliance migration.
Select the Edit in Wizard function.
Proceed through the wizard steps. The installer will dynamically detect the existing, previously deployed components (e.g., vCenter Server, SDDC Manager, and vSphere Cluster).
Continue the deployment workflow from the restored state.
Providing the original JSON specification forces the frontend UI to reconstruct the deployment parameters. The "Edit in Wizard" feature polls the target infrastructure, recognizes the successfully deployed vCenter, SDDC Manager, and vSphere Cluster objects, and aligns the frontend UI state with the backend reality. This allows the installation process to resume successfully without manual API intervention.
If a configuration JSON was not exported prior to the UI session loss, the deployment cannot be resumed via the UI and must be resumed via the REST API by issuing a PATCH request against the execution ID.