vCenter 7 - VAMI keeps coming up "Unable to get deployment status.", UI woks though

[COS]

Lab Environment to do proof of concept:
HPE DL380 Gen8
Windows 2016 server
VMware Workstation 17 Trial

VAMI keeps coming up "Unable to get deployment status.", UI seems to wok though.

I go to https://10.9.8.26:5480 then it redirects me to https://10.9.8.26:5480/configurev2/#/ and prompts for creds.

I authenticate and it comes up with "Unable to get deployment status."

At the console there is a message that says "Failed to start services. Firstboot Error."

I have tried steps in this thread but no luck: https://communities.vmware.com/t5/VMware-vCenter-Discussions/Can-t-access-VAMI-quot-Unable-to-get-de...

I have already redeployed 6 times to VMware Worstation.

Also, "A" record and "PTR" exists.

NSLOOKUP seems fine...

Update: 7/9/2023 8:13PM

Blew out the vcenter7 again and redeployed fresh (again) and I am still getting the message "Unable to get deployment status."!!!

Thanks

[Sachchidanand]

Please go through the following KB:

https://kb.vmware.com/s/article/55746

Regards,

Sachchidanand

[Kinnison]

Hi,

My very personal opnion, I go against the tide, but in your place I would deploy a "nested" host running a recent version of ESXi configured with adequate vCPU and RAM memory and then I would deploy a VCSA object in the traditional way and thus save myself a whole host of problems and annoyances.

Or, if there are no substantial compatibility problems, I would install "bare metal" ESXi and all the rest on that host as systems built around "virtual machines" and also in this case I would save myself problems and annoyances and and also very easily overall better performance.

Regards,
Ferdinando