Problem solve Get help with specific problems with your technologies, process and projects.

Finalizing a VMware vCD home lab installation

At the end of a VMware vCD installation, you must load the vCD components and Sysprep. Mike Laverick explains the steps and offers his final thoughts on creating a vCD home lab.

This series chronicles how to install VMware vCloud Director (vCD) in a home lab. VMware vCD is a new management product for private and hybrid cloud architectures. installing it at home offers IT professionals a safe setting to test and evaluate VMware's cloud product without jeopardizing production resources.

After installing Oracle Enterprise Linux and XE, the next step is the RPM installation process and configuring Secure Sockets Layer (SSL) certificates. This section covers installing VMware vCD components as well as final thoughts on the vCD home lab project.

VMware vCloud Director is a .bin file, and before it can be executed, you need to change the file permissions. You can modify the permissions through graphical tools by right-clicking the file and selecting its properties. Then choose "Allow executing file as program" in the Permissions tab.

Figure 1
(Click image for an enlarged view.)

If you prefer the command line, open a terminal prompt and use the chmod command to alter the file permissions with the following text (change the nonbold text to reflect your specific installation):

chmod u+x vmware-cloud-director-1.0.0-285979.bin

Execute the .bin file by typing "./" before the file name, which is similar to running a Microsoft PowerShell .ps1 file.


If you install vCD in an unsupported Linux distribution, such as Oracle Enterprise Linux, the installer will warn you. But despite this warning, you can proceed through the process.

The installer also checks whether the prerequisite RPMs are installed, and it will abort the installation without them. In the screenshot below, I did not install the compat-libcom_err RPM file.

Figure 2
(Click image for an enlarged view.)

If the prerequisite RPMs are installed, the .bin file will check for sufficient free disk space. Then, it will extract an RPM file called vmware-cloud-director-1.0.0-285979.x86_64.rpm to the same location as the .bin file. So, when you run the .bin file, you need read/write privileges.

 You can install vCloud Director in a standalone mode, which is suitable for home labs. So it's safe to select Y to run the configuration script, which can be run at any time with the following command:


The vCD configuration script asks for several parameters before vCD starts for the first time. These parameters include the following:

  • the specified IP address for the HTTP and console proxy services;
  • the location of the Java key store files and the SSL certificate password;
  • the IP address, hostname and TCP port number of your Syslog erver (optional);
  • the IP address, hostname and TCP port number for the Oracle database server (the default is TCP 1521);
  • the database service name; and
  • the database username and password.

After the configuration process, press Y to start the vmware-vcd daemon.

Figure 3
(Click image for an enlarged view.)

In the vCD configuration utility, many users will probably struggle with "Enter the database service name?" step. VMware has made this more confusing than necessary.

Both the script and VMware's online documentation suggest that it's likely "orcl". In my limited experience with Oracle, this hasn't been the case. In the installation of Oracle Express previously, the service name is XE.

I spent three days struggling with the Oracle database setup, and that experience inspired me to write this article. (I have catalogued my experiences with Oracle database setup on my blog.)

If you use the full production version of Oracle, the database service name is likely a fully qualified domain name (FQDN). You can see this name in some of the dialog boxes during the installation of the full Oracle 11g Enterprise product. The "orcl" text may be the database service name, but it's more likely to be the unique Oracle service identifier. And often, the database server name is the same string as the global database name".

Figure 4
(Click image for an enlarged view.)

To find the service name, or global database name, type the contents of the.tnsnames.ora file held in $ORACLE_HOME/network/admin.

(SID = CLRExtProc)


In the case of Oracle Express, this name should be XE. If you are unsure, check the tnsnames.ora file, which is found at the location below:


Managing Sysprep on VMware vCloud Director
As you create a new virtual machine (VM) from a template in vCenter, Sysprep (or the System Preparation tool) ensures that you gain a unique security identifier, Network Basic Input/Output System (NetBIOS) name and correct domain membership. VMware's vCD has a deployment engine that can also use Sysprep, for the same reasons. It allows users to select VMs from a published list, which VMware calls a "catalog."

As with vCenter, for this arrangement to work, you must copy the various flavors of Sysprep to vCD. Then, run a special script that compiles the Sysprep files into a format that can be used with the system.

The easiest way is to copy the Sysprep files from vCenter to a temporary location on the vCD host with something like WinSCP. or to locate copies of Sysprep on a file server. (In my line of work, I build and rebuild vCenter instances frequently, so I always have a copy available).

Also note the folder names of this temporary structure that you need to create to run the compile script is totally different from vCenter. So if you try the first method, you have to rename folders with the move command (mv). (At VMware, it looks like the vCD team doesn't speak much to the vCenter team!)

Folder name on vCenter

Temporary Folder name on vCD


No Equivalent Directory











Note: With Windows 7 and Window 2008, Sysprep is stored locally within the C:\Windows\System32 directory structure. Therefore, you don't need to copy those files to vCenter or vCD.

You don't have to copy the winxp_64 version of Sysprep if you're 100% sure your cloud will never run this flavor of Windows. But when you run the compile script, it warns you when directories are empty. In my case, I copied the Sysprep files over to the tmp location.

Figure 5
(Click image for an enlarged view.)

Then, I ran the deployment package script.

cd /opt/vmware/cloud-director/deploymentPackageCreator/
./ /tmp/sysprep/

As you can see in the screenshot below, I received an error because the win2k3_64 directory was empty. I've never run this version of Windows in my lab environment.

Figure 6
(Click image for an enlarged view.)

Once the script finishes, restart the vCD daemon for the changes to take effect. You can restart it with the following command:

service vmware-vcd restart

Finishing up the home lab installation
Now you can connect to your vCD server through a Web browser by entering There are some caveats; for example, I use a Mac, though it's not officially supported.

VMware currently supports Internet Explorer and Mozilla Firefox on Windows and Firefox on Linux. In my brief experience with vCD, Firefox on a Mac works. But I was unable to install the Remote Console plug-in, which allows a vCD user to open a window on a VM to interact with it.

Regardless of the OS and Web browser, you must install Adobe Flash, because the main administration tool is based on Adobe Air. The Web browser must be 32-bit, because vCD does not support 64-bit Web browsers.

When you first connect, you will receive a warning that your vCD certificate is untrusted. You can confirm the connection by viewing the certificate details, as illustrated in the image below.

Figure 7
(Click image for an enlarged view.)

The first time you log into vCloud Director, you will see a "run once" welcome screen. This screen allows you to configure the basics, such as accepting the licensing agreement, inputting your vCD evaluation license key and creating a vCloud administrator account.

Figure 8
(Click image for an enlarged view.)

Even getting this far withinstalling vCloud Director is a bit of a struggle -- especially if you're not skilled with the Linux and Oracle databases. There's a dizzying array of user accounts and passwords to remember. I guess that befits the first release of a product; version 1.0 products are notorious for obtuse setups and postconfiguration phases.

It's unlikely that many enterprises will run vCD in a production environment, but they may want to kick the tires for a proof of concept. In the near term, public cloud vendors will likely be the sole users of vCD.


Mike Laverick (VCP) has been involved with the VMware community since 2003. Laverick is a VMware forum moderator and member of the London VMware User Group Steering Committee. Laverick is the owner and author of the virtualization website and blog RTFM Education, where he publishes free guides and utilities aimed at VMware ESX/VirtualCenter users, and has recently joined as an Editor at Large. In 2009, Laverick received the VMware vExpert award and helped found the Irish and Scottish VMware user groups. Laverick has had books published on VMware Virtual Infrastructure 3, VMware vSphere4 and VMware Site Recovery Manager.

Dig Deeper on VMware how-tos

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.