Moreover, since vSphere 6.5, the Update Manager (VUM) is integrated in vCenter. Since vSphere 6.0, the VCSA is really highlighted by VMware. You can also monitor the CPU and memory of the appliance.Īnd you can also update the appliance from this interface. You can connect from You can use root credential.Īs you can see in the below screenshot, you can have the overall health status from this interface.
The VCSA provides an interface for the monitoring. The URL is indicated in the above screenshot. You can now connect to the vSphere Web Client. Once the configuration is finished, you should have the below screen. To finish, click on finish to run the configuration.ĭuring the configuration, you should have a progress bar to inform you where you are in the process. Next you can accept to join the VMWare’s Customer Experience Improvement Program (CEIP) or not. In the next screen, provide SSO information to manage your vSphere infrastructure. Then, specify some NTP server to synchronize the time. In the step 2, we will configure the appliance. When the deployment is completed, you should have the below screen.Ĭlick on continue to process in the step 2. If you connect to the ESXi from the web interface, you can see that the VM is well deployed. While the deployment occurs, a progress bar will show you where you are in the deployment process. To run the appliance deployment, click on finish in the below screen. Otherwise you will have an error message. If you specify a FQDN in system name, be sure that the entry exists (with the right IP address) in the DNS server. In the next screen, specify the network configuration of the VCSA. Then choose a datastore where the VM will be deployed and click on next. More the virtual infrastructure is huge, more the VCSA needs vCPU, RAM and storage. In the next screen, you can choose the appliance size.
Next I specify the VM Name and the root password for the VCSA. I specify a running ESXi, the management port and the root credential. Then specify the ESXi or the vCenter Server where the appliance will be deployed. For this example, I choose the first one and I click on next. The second deployment model is recommended when you want share these services between multiple vCenter Server instances.
PSC manages SSO, certificate stores, licensing service and so on. Or you can separate the role as explain in the below schema. You can select to embed the Platform Services Controller (PSC) with the vCenter Server. Next you have to accept license agreement and click on next. In the first step, we will deploy the appliance and in the second one, we will configure it. In the next screen, the wizard explains you there is two steps to deploy the VCSA.
In this topic, I’ll show you how to deploy a standalone VCSA 6.5 from a client computer. The only con of VCSA is that it is a black box. The VCSA is free where you have to pay a license for the Windows vCenter. Moreover, with vSphere 6.5, the update manager is integrated to vCenter. The below table introduces the Windows versus VCSA scalability (vSphere 6.0 information):Īs you can see, there is no advantage anymore to use Windows vCenter. With vSphere 6.5, the VCSA support the simplified native vCenter High Availability which is available only for the VCSA (not for Windows). Since vSphere 6, the VCSA can manage more hosts and more VM and is more robust and scalable.