Hello Glenn,
From your screenshots, there appear to be two different issues:
- Stage 1 reports that the installer cannot reach the Migration Assistant on TCP port 9123.
- You also mentioned that Stage 2 fails while starting the VMware Security Token Service (STS).
If you're migrating from a Windows vCenter Server to a vCenter Server Appliance (VCSA) 8, the first issue must be resolved before the migration can proceed successfully.
I would recommend verifying the following:
- Confirm that the VMware vCenter Migration Assistant is running on the source Windows vCenter.
- Verify that TCP port 9123 is listening on the source server (netstat -ano | findstr 9123) and isn't blocked by Windows Firewall or any network firewall.
- Ensure you're using the Migration Assistant version that matches the VCSA 8 installer. An older Migration Assistant may not be compatible.
- Verify name resolution (forward and reverse DNS) between the installer workstation, the source vCenter, and the ESXi hosts, as DNS issues can also cause migration failures.
If Stage 1 completes successfully but Stage 2 still fails at the VMware Security Token Service (STS), I'd recommend checking:
- The health of the STS service on the source vCenter.
- Certificate validity (especially STS and Machine SSL certificates) using the VMware certificate management tools.
- The migration logs under:
-
- %TEMP%\vcsaUiInstaller\logs\
-
- /var/log/vmware/upgrade/ (on the target appliance)
The specific log entry around the STS startup failure will usually identify whether the issue is related to certificates, SSO, or service dependencies.
Could you also clarify:
- Are you migrating from Windows vCenter 6.7, Windows vCenter 7.0, or an existing VCSA 7.0?
- Which exact build of vCenter 7 are you running?
- Does the failure occur during Stage 1 (deployment) or Stage 2 (data migration) after Stage 1 completes?