The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Services bundled with vCenter Server Appliance (2002531)
Services included in vCenter Server Appliance
- An Autodeploy service is bundled with vCSA.
- The appliance is capable of acting as a TFTP server using the atftpd daemon that is built into SUSE Linux. The TFTP server is pre-configured to share the /tftproot/ folder, which contains the gpxe images for Autodeploy.
- The appliance is capable of acting as a DHCP server using the dhcpd daemon built into SUSE Linux.
- The Autodeploy service is automatically registered as a vCenter Server Extension.
Syslog Collector Service
- The Syslog Collector Server is installed by default, but is not registered as a vCenter Server Extension. To collect the required logging information, you must log into the console or connect to vCSA using SSH and manually collect the log files generated.
ESXi Dump Collector Service
- The ESXi Dump Collector Server is installed by default, but is not registered as a vCenter Server Extension. To collect the required core dump information, you must log into the console or connect to vCSA using SSH and manually collect the log files generated.
vSphere Web Client
- The vSphere Web Client Service is bundled with the vCenter Server Appliance. Unlike the standalone version of this server, the service need not be configured to connect to vCSA. By default, the service is aware of vCenter Server on the appliance.
Services that are not included in vCenter Server Appliance
vCenter Update Manager
- There is no Linux-based equivalent to Update Manager. You can install the Windows-based Update Manager on a Windows guest and register the Update Manager plug-in when connected to the vCSA with a vSphere Client. For more information, see the vSphere Update Manager Documentation.
vCenter Converter Standalone
- There is no Linux-based equivalent to Converter Standalone. You can install the Windows-based Standalone Converter on a Windows guest and import converted machines connecting to the vCSA as a destination. For more information, see the vCenter Converter Standalone Documentation.
- The vCLI is not included as part of vCSA. If you want vCLI in an appliance, use the vSphere Management Assistant (vMA) Appliance. For more information, see the vSphere Management Assistant Documentation.
- PowerCLI and all other PowerCLI extensions require PowerShell, which runs only on Microsoft Windows-based systems. For more information, see the vSphere PowerCLI Documentation.
Limitations of vCSA
- vCSA supports connection between vCenter Server and vCenter Server components by IP address only if the IP address is IPV4-compliant. To connect to a vCenter Server system in an IPv6 environment, you must use the fully qualified domain name (FQDN) or host name of the vCenter Server. The best practice is to use the FQDN, which works in all cases, instead of the IP address, which can change if assigned by DHCP.
- vCSA does not support Linked Mode. This is because the Microsoft ADAM dependency is provided by Microsoft Windows-based platforms.
- The vCSA 5.0 GA uses an embedded DB2 Express database.
- The vCSA 5.0 Update 1b, vCSA 5.1, and vCSA 5.5 all use an embedded vPostgres database. The appliance can also connect to supported Oracle databases.
- vCSA 5.1 is supported to use a Oracle RAC database if it is running version 126.96.36.199.0 or higher. For more information, see vCenter Server and vCenter Server Appliance SSO cannot communicate with Oracle RAC and NON-RAC Databases (2041262).
- vCSA 5.1 does not support Microsoft SQL database connectivity.
- Security Support Provider Interface (SSPI) is only supported with a Kerberos mechanism when vCSA is in a Windows domain.
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.