5.5
Table Of Contents
- vCloud Director Installation and Upgrade Guide
- Contents
- VMware vCloud Director Installation and Upgrade Guide
- Overview of vCloud Director Installation, Configuration, and Upgrade
- vCloud Director Architecture
- Configuration Planning
- vCloud Director Hardware and Software Requirements
- Browsers That vCloud Director Supports
- Summary of Network Configuration Requirements for vCloud Director
- Installing and Configuring a vCloud Director Database
- Create SSL Certificates
- Installing and Configuring vShield Manager
- Installing and Configuring an AMQP Broker
- Download and Install the VMware Public Key
- Creating a vCloud Director Server Group
- Install and Configure vCloud Director Software on the First Member of a Server Group
- Configure Network and Database Connections
- Install vCloud Director Software on Additional Members of a Server Group
- Install Microsoft Sysprep Files on the Servers
- Start or Stop vCloud Director Services
- Uninstall vCloud Director Software
- Upgrading vCloud Director
- vCloud Director Setup
- Cell Management Tool Reference
- Index
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,” on
page 31.
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 Chapter 4, “vCloud Director
Setup,” on page 43.
Install Microsoft Sysprep Files on the Servers
Before vCloud Director can perform guest customization on virtual machines with certain older Windows
guest operating systems, you must install the appropriate Microsoft Sysprep files on each member of the
server group.
Sysprep files are required only for some older Microsoft operating systems. If your cloud does not need to
support guest customization for those operating systems, you do not need to install Sysprep files.
To install the Sysprep binary files, you copy them to a specific location on the server. You must copy the
files to each member of the server group.
Prerequisites
Verify that you have access to the 32- and 64-bit Sysprep binary files for Windows 2003 and Windows XP.
Procedure
1 Log in to the target server as root.
2 Change directory to $VCLOUD_HOME/guestcustomization/default/windows.
[root@cell1 /]# cd /opt/vmware/vcloud-director/guestcustomization/default/windows
3 Create a directory named sysprep.
[root@cell1 /opt/vmware/vcloud-director/guestcustomization/default/windows]# mkdir sysprep
4 For each guest operating system that requires Sysprep binary files, create a subdirectory of
$VCLOUD_HOME/guestcustomization/default/windows/sysprep.
Subdirectory names are specific to a guest operating system.
Table 2‑1. Subdirectory Assignments for Sysprep Files
Guest OS
Subdirectory to Create Under
$VCLOUD_HOME/guestcustomization/default/windows/sysprep
Windows 2003 (32-bit) svr2003
Windows 2003 (64-bit) svr2003-64
Windows XP (32-bit) xp
Windows XP (64-bit) xp-64
For example, to create a subdirectory to hold Sysprep binary files for Windows XP, use the following
Linux command.
[root@cell1 /opt/vmware/vcloud-director/guestcustomization/default/windows]# mkdir sysprep/xp
Chapter 2 Creating a vCloud Director Server Group
VMware, Inc. 31