You can deploy the vCloud Director appliance as an OVF template by using the vSphere Web Client (Flex) or the vSphere Client (HTML5).

You must deploy the first member of a vCloud Director server group as a primary cell. You can deploy a subsequent member of a vCloud Director server group as a standby or vCD application cell. See Appliance Deployments and Database High Availability Configuration.

Important: Mixed vCloud Director installations on Linux and vCloud Director appliance deployments in one server group are unsupported.

For information about deploying OVF templates in vSphere, see vSphere Virtual Machine Administration.

As an alternative, you can deploy the appliance by using VMware OVF Tool. See Deploying the vCloud Director Appliance by Using VMware OVF Tool.

Note: Deploying the vCloud Director appliance in vCloud Director is unsupported.

What to do next

  • Configure the public console proxy address, because the vCloud Director appliance uses its eth0 NIC with custom port 8443 for the console proxy service. See Customize Public Endpoints.
  • To add members to the vCloud Director server group, repeat the procedure.
  • To enter the license key, log in to the vCloud Director Web Console.
  • To replace the self-signed certificate that is created during the appliance first boot, you can Create an CA-Signed SSL Certificate Keystore for vCloud Director on Linux.