You can add servers to a vCloud Director server group at any time. Because all servers in a server group must be configured with the same database connection details, you must use the response file created when you configured the first member of the group to supply this information when you configure additional members.


  • Verify that you can access the response file that was created when you installed and configured the first member of this server group. See Protecting and Reusing the Response File.

  • Verify that the vCloud Director database is accessible from this server.

  • Verify that the SSL certificates that you created for this server are installed in a location that the installer can access. See Create and Import a Signed SSL Certificate. The configuration script does not run with a privileged identity, so the keystore file and the path in which it is stored must be readable by any user. Using the same keystore path (for example, /tmp/certificates.ks) on all members of a server group simplifies the installation process.

  • Have the following information available:

    • The password of the keystore file that includes the SSL certificates for this server.

    • Password for each SSL certificate.


  1. Log in to the target server as root.
  2. Download the installation file to the target server.

    If you purchased the software on a CD or other media, copy the installation file to a location that is accessible to all target servers.

  3. Ensure that the installation file is executable.

    The installation file requires execute permission. To be sure that it has this permission, open a console, shell, or terminal window and run the following Linux command, where installation-file is the full pathname to the vCloud Director installation file.

    [root@cell1 /tmp]# chmod u+x installation-file
  4. Copy the response file to a location accessible to this server.

    All directories in the pathname to the response file must be readable by root.

  5. In a console, shell, or terminal window, run the installation file using the -r option and specifying the response file pathname.

    To run the installation file, type its full pathname, for example:

    [root@cell1 /tmp]# ./installation-file -r /path-to-response-file

    The file includes an installation script and an embedded RPM package.


    You cannot run the installation file from a directory whose pathname includes any embedded space characters.

    The installer prints a warning of the following form if you have not installed the VMware public key on the target server.

    warning:installation-file.rpm: Header V3 RSA/SHA1 signature: NOKEY, key ID 66fd4949

    When the installer runs with the -r option, it takes these actions.

    1. Verifies that the host meets all requirements

    2. Verifies the digital signature on the installation file

    3. Creates the vcloud user and group

    4. Unpacks the vCloud Director RPM package

    5. Installs the software

    6. Copies the response file to a location readable by vcloud.vcloud

    7. Runs the configuration script using the response file as input

    When the configuration script runs, it looks for the certificates in the path saved in the response file (for example, /tmp/certificates.ks) , then prompts you to supply the keystore and certificate passwords. If the configuration script does not find valid certificates in the pathname saved in the response file, it prompts you for a pathname to the certificates.

  6. (Optional) Repeat this procedure to add more servers to this server group.

What to do next

If your cloud needs to support guest customization for certain older Microsoft operating systems, install Sysprep files on all members of the server group. See Install Microsoft Sysprep Files on the Servers.

After the configuration script finishes and vCloud Director services are running on all servers, you can open the Setup wizard at the URL that appears when the script completes. See vCloud Director Setup.