vCSA 6.x installer error: “No networks on the host. Cannot proceed with the installation.”

Reading Time: 2 minutes

This is a quick post of an error I found sometimes while deploying a new vCenter server appliance with an embedded PSC on the vCSA 6.x installer.

The problem

In my case, I was trying to install vCSA 6.5 without DNS (this is why the system name has an IP address and the DNS is itself). Also, notice that the network section is empty:

If you try to continue with the installation, it will show you an error:

No networks on the host. Cannot proceed with the installation.



I checked the ESXi host and obviously, it has other port groups created in a standard virtual switch, then, which was the problem? Why I can’t see them in the drop-down list?


Checking on the internet I found this:

So, that web page mentions the “VM network” port group that is a default port group that is created once you deploy an ESXi host. In my case, it was auto-deployed with different port groups and that one didn’t exist.

Hence, I decided to create a port group called “VM Network” in the host that I am trying to deploy the vCSA and…it worked!

Now, as you can see, I can see that port group and I was able to continue the installation with success!

It seems that with you must have this port group if you are deploying a vCSA at least from your PC, so, bear in mind if you are trying to deploy a new vCSA and you don’t have the default port groups when deploying a vCenter Server.


I hope this helps if someone has this issue.

vSphere 6.0: New external PSC within existing SSO Domain

Reading Time: 2 minutes

Hello there!

A quick post talking about a new external PSC in vSphere 6.0 environments.

As you may now the vCenter product is composed by the PSC (Platform Services Controller) and the vCenter component.

Services provided by each component:

Platform Services Controller vCenter
vCenter Single Sign-On PostgreSQL or SQL Express (in 6.0 version)
VMware Certificate Authority vSphere Web Client
vSphere License Service vSphere Client
vSphere ESXi Dump Collector
vSphere Syslog Collector
vSphere Auto Deploy
vSphere Update Manager

Let’s go to the point. I am going to repoint a vCenter with an embedded PSC (a vCSA called “pokecenter”) to an external PSC I created in a Windows server called “digicenter” (I know is kinda original). Digicenter is already joined to the same SSO domain as pokecenter.

Note: If you have any problem when adding an external PSC to an existing SSO domain, check cmsso-util unregister command in the vCSA appliance. In my case, I had to re-install it three times and in the last one, I used the command.

More information in KB:

In the vCenter with embedded PSC, I will connect through SSH and repoint my vCenter to the external Windows PSC “digicenter”.

The command is: cmsso-util reconfigure –-repoint-psc –username administrator –domain-name vsphere.local –passwd VMware1!

Now, time to wait, it will take a couple of minutes as the text says:

 And after the pass, successful!


Hence, our vCenter “pokecenter” has an external PSC “digicenter”. We can check it in vCenter > Manage > Settings > Advanced Settings:

If found some problems when repointing to the external PSC,  make sure the time on both servers is the same (check NTP server), also DNS resolution of the external PSC. Give some time for the vSphere Client to initialize after the repointment.

Finally, be patient, I found some errors (SSO errors about the external PSC) when login to the vSphere Web Client but, after waiting about 10 minutes finally it initialized up successfully.