Key Features

• Create virtual datacenters
• Support multi-tenant environments
• Self Service Portals
• vSheild Security
• vCloud API and Automation

Basically sits on top of vCenter/ESX(i) and offers self service portals useful for multi-tenant environments.

Product Site

http://www.vmware.com/products/vcloud-director/

Will post more info on this later. Do ask if you have any questions..

This is an issue with Microsoft Windows Installer and does not affect all Windows 2008 systems. The problem can occur when the original install path from the older version of VMware Tools is invalid

To correct this issue, you must perform a forced uninstall and re-install of VMware Tools.

To uninstall and re-install VMware Tools:

1. Right-click on the virtual machine.
2. Click Guest > Install/Upgrade VMware Tools.
3. Open a Console to the virtual machine and log into the guest operating system.
4. Click Start > Run, type cmd, and click OK to open a command prompt in Windows.
5. Change the drive to your CD-ROM drive. For example, D:\.
6. Type setup /c and press Enter to force removal of all registry entries and delete the old version of VMware Tools.
7. In My Computer, double click the CD-ROM that contains VMware Tools.
8. Select setup.exe to install if Auto-Run doesn’t start.

Came across above error with vconverter 4.0.1 build 161434 and the older versions with server 2008 r2 64bit cold v2v convert.

Vconvert doesn’t properly support server 2008 64bit R2. Way around it is to change the Guest Operating System from virtual machine settings to Vista 64bit and vconvert will detect the vm and convert fine. After the conversion, change the OS back to server 2008 64bit R2.

vConvert won’t let you reduce the size of vm on virtual machine hardware 7. Only option is to use Thin Provision.

The Install Shield package of VirtualCenter files is a 16-bit application that uses 8.3 file notation.
Your system may have 8.3 file name creation disabled by the Administrators or Group policy in order to increase performance on an NTFS file system.
This message is shown because there is an unknown parameter passed to the msiexec command.
Typically, this error is because the installer does not quote the %TMP% and %TEMP% variables, and if they are configured with some blank space file path, the installation fails.

Solution:

Set the %temp% environment variable to use an 8.3 naming convention path (that is, C:\temp).
You must create a new temporary folder for the installation and set the environment variables %TMP%, %TEMP% to use it:

This can be changed from Systems Properties – Advanced – Environmental Variables.

” vmauthd.server.alwaysProxy=TRUE “