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.

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.

So…

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.