Vmware Virtual Infrastructure Client 2.0 Download

Posted on by admin

Jan 30, 2008 VMware Virtual Desktop Manager 2 is a desktop management server that connects users to virtual desktops in the data center. With VMware Virtual Desktop Manager 2, end users can securely access their virtual desktops using either a personal computer or thin client. Download VMware vCenter Converter Standalone. VCenter Converter Standalone converts physical machines and virtual machines to VMware virtual machines and configures VMware virtual machines.

Check back frequently for additions and updates to these release notes.

ESX Server Version 3.0.1 09/25/2006 Build 32039

VirtualCenter Version 2.0.1 09/25/2006 Build 32042

Last Document Update: 11/3/06

What's in the Release Notes

The release notes cover the following topics:

What's New in the ESX Server 3.0.1/VirtualCenter 2.0.1 Release

This release of VMware Infrastructure, comprised of ESX Server and VirtualCenter, offers the following improvements:

  • Support for selected 64-bit guest operating systems. For more information on 64-bit guest operating system support including important hardware requirements, see Details of What's New and Improved in VMware Infrastructure 3 and the Systems Compatibility Guide for ESX Server 3.x.
  • Improved upgrade support from Virtual Infrastructure 2 to VMware Infrastructure 3. For more information, see the Installation and Upgrade Guide.
  • Introduction of the esxupdate utility for upgrade deployment. For more information, see the Installation and Upgrade Guide.
  • NEW: Support for Microsoft SQL Server 2005 (SP1 only) as a database for VirtualCenter. See Requirements for Running VirtualCenter with MS SQL 2005 (KB 6565318) for information on using this database with VirtualCenter.
  • Support for servers based on the AMD 2000/8000 and Intel Xeon 7100 (codename Tulsa) series of processors.
  • Enablement of QLogic QLA 4050/4052 hardware iSCSI HBAs. See the ESX Server 3.x I/O Compatibility Guide and the ESX Server 3.x Storage/SAN Compatibility Guide for the latest support status because testing and certification is not yet complete at the time of these release notes publication.
  • Support for iSCSI arrays such as EqualLogic PS300 and NetApp FAS3000.
  • Support for Symmetric Multiprocessing (SMP) on Windows XP virtual machines.
  • Critical bug fixes related to ESX Server 3.0 and VirtualCenter 2.0.
  • Enablement for German and Japanese product versions.

    Note: Technical support services for VMware Infrastructure are currently delivered in English. German and Japanese speaking Support Engineers are available in a limited capacity during the operating hours of the local support center. For more information, see VMware local language support.

Look for additional details on these and other VMware Infrastructure 3 features in Details of What's New and Improved in VMware Infrastructure 3.

ESX Server 3.0/VirtualCenter 2.0 Feature Highlights

The ESX Server 3.0 and VirtualCenter 2.0 product lines offer an array of new features and enhanced functionality. Here are some highlights:

  • NAS and iSCSI Support
    ESX Server 3.0 can store virtual machines on NAS and iSCSI. iSCSI LUNs, like Fibre Channel LUNs, can be formatted with the VMware file system (VMFS). Each virtual machine resides in a single directory. Network attached storage (NAS) appliances must present file systems over the NFS protocol for ESX Server to be able to use them. NFS mounts are used like VMFS with ESX Server creating one directory for each virtual machine. iSCSI enabled through a software initiator (100% implemented as a software layer over TCP/IP) is fully supported in this release.
  • Clusters
    A cluster is a collection of hosts that can be managed as a single entity. The resources from all the hosts in a cluster are aggregated into a single pool. A cluster looks like a stand-alone host, but it typically has more resources available.
  • VMware DRS
    VMware DRS allows resources from all hosts in a cluster to be treated as a single, aggregated pool. When changes occur in the environment, DRS can tune the resource scheduling on individual hosts as well as use VMotion to rebalance workload across hosts in the cluster. When a virtual machine is powered on, DRS calculates the optimal host on which to start it, given current resource levels and the resource configuration of the new virtual machine.
  • Resource Pools
    A resource pool provides a way of subdividing the resources of a stand-alone host or a cluster into smaller pools. A resource pool is configured with a set of CPU and memory resources that are shared by the virtual machines that run in the resource pool. Resource pools can be nested.
  • VMware HA
    VMware HA (HA) increases the availability of virtual machines by detecting host failures and automatically restarting virtual machines on other available hosts. HA operates on a set of ESX Server 3.0 hosts that have been grouped into a cluster with HA enabled.
  • 64-Bit Virtual Machines
    64-bit guest operating systems are experimentally supported and visible in the Virtual Infrastructure Client interface, with full support available in future VI3 releases.
  • Remote CD/Floppy
    Using either the Virtual Infrastructure Client or Virtual Infrastructure Web Access, a virtual machine can access a CD or floppy device from the client's machine.
  • Hot-Add Virtual Disk
    ESX Server 3.0 supports adding new virtual disks to a virtual machine while it is running. This is useful with guest operating systems capable of recognizing hot-add hardware.
  • New Version of the VMware File System: VMFS 3
    There is a new generation of VMFS in ESX Server 3.0. Scalability, performance, and reliability have all improved. Furthermore, subdirectories are now supported. ESX Server system will create a directory for each virtual machine and all its component files.
  • VMware Consolidated Backup
    Consolidated Backup enables offloaded and impact-free backup for virtual machines running on an ESX Server system by allowing traditional file-based backup software to leverage VMware virtual machine snapshot technology and efficient SAN-based data transfer.
  • Virtual Infrastructure Client
    The VirtualCenter Client has been renamed the Virtual Infrastructure Client or VI Client to convey its ability to connect to a VirtualCenter Management Server or to individual ESX Servers. When connected to VirtualCenter 2.0, the VI Client provides full monitoring and management of multihost configurations and multihost functionality, such as VMotion, DRS, and HA. When connected to ESX Server 3.0, the VI Client provides the subset of functionality needed to manage the virtual machines and configurations of single hosts. In both cases, the VI Client contains all the functionality previously available through the separate Web-based Management User Interface (MUI) in ESX Server Server 2.x and provides an interface to configure ESX Server 3.0.
  • New Guest SDK Available

  • The VMware Guest SDK allows software running in the guest operating system in a VMware ESX Server 3.0 virtual machine to collect certain data about the state and performance of the virtual machine. Download the Guest SDK package from www.vmware.com/support/developer/
  • Tools Auto-Upgrade

  • VMware Infrastructure 3 (ESX Server 3.0/VirtualCenter 2.0) supports the ability to install or upgrade VMware Tools on multiple virtual machines at the same time without needing to interact with each virtual machine. Detailed instructions are provided in the Installation and Upgrade Guide.
  • Licensing Scheme

  • ESX Server 3.0 and VirtualCenter 2.0 introduce new licensing mechanisms based on FlexNet mechanisms. The first option is called 'License Server Based' licensing and is intended to simplify license management in large, dynamic environments by allowing licenses to be managed and tracked by a license server. The second option is called 'Host Based' licensing and is intended for smaller environments or customers preferring to keep ESX Server systems decoupled from a license server.

    Use 'License Server Based' license files to unify and simplify the license management of many separate VirtualCenter and ESX Server licenses by creating a pool of licenses centrally managed by a license server. Licenses for the VirtualCenter Management Server and for the VirtualCenter add-on features, such as the VirtualCenter Management Agent, VMotion, VMware HA, and VMware DRS are only available in this form.

    'Host Based' license files are not centrally managed and not dynamically allocated but might be placed directly on individual ESX Server hosts. Only the licenses for ESX Server and VMware Consolidated backup are available in this alternative form.

  • VMware Experimental Feature Support Definition

  • VMware includes certain experimental features in some of our product releases. These features are there for you to test and experiment with. We do not expect these features to be used in a production environment. However, if you do encounter any issues with an experimental feature, we are interested in any feedback you are willing to share. Please submit a support request through the normal access methods. You will receive an auto-acknowledgement of your request. We cannot, however, commit to troubleshoot, provide workarounds, or provide fixes for these experimental features.

Before You Begin

ESX Server, VirtualCenter, and GSX Server Compatibility

This release version requires or functions with the listed version of the following servers:

VirtualCenter version ESX Server version GSX Server version VMware Server version
2.0.1 2.0.1, 2.1.x, 2.5.x, 3.0, 3.0.1
2.0 2.0.1, 2.1.x, 2.5.x, 3.0
1.4 2.0.1, 2.0.2, 2.1.x, 2.5.x 3.1, 3.21.0
1.3, 1.3.1 2.0.1, 2.1, 2.1.1, 2.1.2, 2.5.x 3.1, 3.2
1.2 2.0.1, 2.1, 2.1.1, 2.1.2, 2.5.0, 2.5.1 3.1, 3.2, 2.1, 2.1.1 3.1, 2.1

ESX Server and Management Agent Compatibility

Please check the Systems Compatibility Guide for ESX Server 3.x for latest management agent compatibility.

Additional Information

For additional information, use the following sources:
  • SDK documentation package has been updated. For more information, see theVMware Infrastructure SDK page.
  • Windows 2000 must be updated with Rollup 1 for Service Pack 4. Download this Rollup fromhttp://www.microsoft.com/windows2000/server/evaluation/news/bulletins/rollup.mspx. Refer tohttp://support.microsoft.com/kb/816542/ for details. This fix is essential for VirtualCenter Server to operate correctly.
  • For information about third-party software and the new VMware Service Console firewall, see KB 2143.

Installation Notes for This Release

  • See the ESX Server Compatibility Guides before installing this software. It is important to verify that your server, I/O, storage, guest operating system, management agent, and backup software are compatible. These guides also address minimum requirements and scaling limits associated with this release. To view a guide, click one of the following links:
  • VMware strongly recommends that you read the Installation and Upgrade Guide for step-by-step guidance on installing and configuring ESX Server and VirtualCenter.

    Although the installations are straight-forward, several subsequent configuration steps are essential. In particular, read:

    • 'Licensing' in the Installation and Upgrade Guide
    • 'Networking' in the Server Configuration Guide
    • 'Security' in the Server Configuration Guide for firewall ports
  • If you are upgrading an existing ESX Server (and VirtualCenter environment), pay attention to the 'Upgrading' chapters of the Installation and Upgrade Guide.

Upgrading or Migrating to VMware Infrastructure 3

This release supports upgrading from ESX Server 2.x and VirtualCenter 1.x to VMware Infrastructure 3, which includes ESX Server 3.x and VirtualCenter 2.x. VMware highly recommends that you review the detailed upgrade instructions and guidelines that are provided in the Installation and Upgrade Guide.

VMware DRS and HA Recommendations

VMware Infrastructure DRS and HA clusters can include no more than 16 ESX Server hosts.

Known Issues for ESX Server 3.0.1 and VirtualCenter 2.0.1

The Known Issues are grouped as follows:


  • During an ESX Server 3.0.1 Scripted Installation on SCSI Controllers with cciss Driver, VMFS3 Volumes Might Not Be Correctly Created (KB 8577703)
  • Some USB Devices Fail During ESX Server Installation (KB 3655619)
  • ESX Server Installation Fails When a Root Partition of 100GB or Larger Is Specified (KB 3950560)
  • ESX Server Installer Is Unable to Format VMFS File Systems if the Storage Controller Returns an Unrecoverable Error for a LUN(KB 1476874)
  • Scripted Installation Prompts for Keyboard and Language Selections (KB 7997330)
  • License Server Writes Log Data to User Directory (KB 8019937)
Upgrade Issues
  • VMware HA Configuration Errors after VirtualCenter Server Update (KB 1000780) NEW
  • Upgrade of Legacy GSX Server or Workstation Templates Triggers an Error Message (KB 9889961) NEW
  • Migration Upgrade with VMotion Supports Upgrades Only from Specific Versions of ESX Server 2.x (KB 8479101) NEW
  • Using Virtual Center 2.0.1 UI Option to Upgrade Legacy Virtual Machine Hardware on ESX Server 2.x System Does Not Work (KB 132194) UPDATED
  • Migration Upgrade of a Virtual Machine May Create a Duplicate RDM (KB 8188562)
  • Upgrading Templates Across Incompatible ESX Server Host and VMFS Versions Fails (KB 218402)
  • Stacked Graph Chart Doesn't Display Virtual Machine Performance Data After Upgrading to VirtualCenter 2.0.1 (KB 6247518)
  • Preupgrade.pl Script Triggers a Warning when Run on ESX Server 3.0 (KB 538417)
  • When Upgrading Oracle Database, Error Message Might Indicate That Database Upgrade Has Failed (KB 2040533)
  • Bulk-Logged Option for SQL Server Database Needs to Be Enabled Before Upgrading (KB 2603739)
  • Queued Legacy Template Upgrades Block Subsequent Tasks from Running (KB 9297677)
  • RPM Version Numbers from CD and Tarball Upgrades Don't Match (KB 747254)
  • Auto-Upgrading Tools in NetWare Virtual Machines Produces Errors (KB 3431060)
  • Some Performance Data Is Not Displayed After VirtualCenter Upgrade (KB 5211358)
  • Boot Information Is Lost If MBR Location Is Changed During Upgrade (KB 5089096)
  • Changing MBR in a Scripted Upgrade Produces Error Message (KB 7926780)
  • Database Upgrade Fails Due to Insufficient Disk Space (KB 7434572)
  • After Upgrading from ESX Server 2.5.x to ESX Server 3.0.1, CPU Hyperthreading Might Appear to Become Disabled (KB 8451742)
  • When Upgrading VMware Tools with the rpm -Uhv Command for Red Hat Enterprise Linux 3.0 AS Guest Operating Systems, You Might See an Error Message (KB 1032429)
  • When Upgrading from VirtualCenter 1.x to 2.0.1, Database Upgrades Can Fail if the 1.x System Has Both an MSDE Database and a Production Database (KB 3438229)
  • Upgrade of a GSX Template Fails With Invalid Datastore Format Message (KB 1797556)
  • RDM Virtual Machines Display as VMFS Virtual Machines After Being Migrated from ESX Server 2.x Hosts to ESX Server 3.0.1 Hosts Using Upgrade VMotion (KB 3461997)
  • Upgrade Migration with VMotion Can Fail if CPU Utilization or I/O Load on a Virtual Machine or Host System Are Too Heavy (KB 7136768)
Backup Issues
  • Error in Configuration File Causes Communication Failure Between Veritas NetBackup and Service Console (KB 9480977)
  • Drive Letter Mount Points on the VCB Proxy Don't Match Drive Letters as Seen from NT4 Virtual Machines (KB 1389121)
  • Service Console Firewall Configurations Need to Be Changed after Installing Backup Agents (KB 3319174)
Server Configuration Issues
  • Changes in Software iSCSI Configurations Require Host Reboot (KB 7372490)
  • Misleading Time-Out Errors Occur When Rescanning iSCSI Storage Adapters (KB 47205)
  • Read-Only NFS Datastore Doesn't Allow Browsing for ISO Images when You Try to Connect a Virtual CD-ROM Device to an ISO File on the Datastore (KB 2827628)
  • Deleting Discovery Addresses Causes Problems when ESX Server Boots from iSCSI (KB 3217572)
  • Changes to Security Profile Virtual Machine Delegate Do Not Display Until After Reboot (KB 282669)
  • Data Corruption Might Occur if iSCSI Targets Do Not Implement SCSI Reservations (KB 1405590)
  • ESX Server Checks Out Multiple Licenses When Name Resolution Is Misconfigured (KB 9950090)
VirtualCenter, VI Client, and Web Access Issues
  • ESX 3.0 Hosts May Become Unresponsive While Multiple Clone, Migrate, or Power Operations Are Executed (KB 7298369)
  • Cannot Add VirtualCenter Permissions for Users or Groups with Long Names (KB 2589144)
  • Right Clicking or Removing a Disconnected Host Generates Error Messages (KB 6588824)
  • Web Access Doesn't Support Browsing the vmimages Folder (KB 294251)
  • VI Client Menus May Not Display Expected Choices (KB 1900576)
  • The 'Connect Exclusively to this Virtual Machine' Option Does Not Appear on the VI Web Access CD/DVD Configuration Screen (KB 8582994)
  • You Cannot Navigate to a Virtual Machine Using Web Access while the Virtual Machine Is Being Deployed or Cloned (KB 7194279)
  • When You Use Web Access with Internet Explorer, a Warning Doesn't Display when You Perform Power On Operations Resulting in Error (KB 525306)
  • When Performing Certain Operations in the Web Access GUI's CD/DVD Configuration Page, You May See the 'System Restart' Dialog Box (KB 8464334)
Virtual Machine Management Issues
  • Taking More than One Snapshot of a Suspended Virtual Machine Produces a Fault (KB 1424776)
  • Virtual Machines Deployed from Templates might Lose BIOS Settings (KB 8808589)
  • Reverting to Snapshots of Virtual Machines with Hot-Added RDM Virtual Disks in Physical or Virtual Mode Causes Virtual Machines to Hang (KB 9729125)
  • If a Virtual Machine Has Two Disks with Identical File Names, Stored in Different Locations, You Cannot Delete a Snapshot of This Virtual Machine (KB 5096672)
  • VMotion Fails Between Rev E and Rev F AMD CPUs (KB 3700586)
Guest Operating System Issues
  • SLES 10 Linux Guest Operating Systems May Cause Poor Networking Performance in Virtual Machines (KB 461197) NEW
  • Solaris 10 Guests with SMP May Hang When Powering On (KB 4484334)
  • Reset and Restart Options Do Not Work with Netware5 and Netware6.5 Guest Operating Systems (KB 2050857)
  • Guest Kernel Reports a Fault when Running Solaris 10 GA or Solaris 10 U1 in a SMP Virtual Machine (KB 3605018)
  • Solaris 10 Guest Performance Improved with Sun Patch (KB 9876622)
  • 32-bit Virtual SMP Solaris Guest Operating Systems Become Unresponsive if You Execute Certain CPU Commands (KB 5365186)
  • In Guests that Are Not ACPI Aware, Shutting Down the Guest Does Not Disable the Install Tools Option (KB 5498908)
  • Memory Allocated to Red Hat Linux on an AMD Kernel Is Not Available (KB 630279)
  • When Installing Solaris U2, Disk Errors Occur (KB 3174163)
Miscellaneous Issues
  • Using 4G Brocade Switch Version 5.0.4 Results in Failover Failure on ESX Server (KB 3641217)
  • MSCS Requires 2 GB Fibre Channel Drivers (KB 1560391)
  • VMware HA May Incorrectly Handle Temporary Host Network Isolation(KB 2956923)
  • On Systems Set to a Non-English Locale, VirtualCenter Does Not Install Correctly if the Installation Path Contains Non-English Characters(KB 2302421)

Known Issues for ESX Server 3.0 and VirtualCenter 2.0

Security Alerts for This Release

Please refer to KB 1107 for VMware product security alerts.

The Known Issues are grouped as follows:


  • Graphical Installer Might Fail to Load on IBM x445 Server with RSAII Adapter (KB 2148)
  • Display Goes Blank When Installing Using Remote Interface on Intel Blade Servers (KB 2149)
  • Cannot Log Onto VirtualCenter Server Using VI Client After VirtualCenter Server Upgrade or Installation (KB 2150)
  • Installing ESX Server 3.0 on IBM e326 or Dell-1850 Causes Keyboard to Become Unresponsive (KB 2152)
  • When Attempting to Do a BootFromSan Using LPe1150, the Link Never Comes Up on the HBA (KB 2288)
  • ESX Server 3.0 System with More than 128 LUNs Attached Fails to Install (KB 2154)
  • USB Keyboard and Mouse Are Not Usable After Installation and Reboot of VMware ESX 3.0 Server (KB 2280)
  • Virtual Machines' Raw Disks Cannot Be Upgraded to RDMs by the Upgrade Script (KB 2168)

Upgrade Issues

  • Some Storage Applications May Require Firewall Ports Be Opened(KB 2143)
  • Template Upgrades Do Not Work If the Host Is Running ESX Server 2.x (KB 2189)
  • Adding a Legacy Virtual Disk to a Virtual Machine Downgrades it to a Legacy Virtual Machine (KB 2137)
  • Creating a Virtual Machine Using an Existing Disk from a Legacy Virtual Machine Can Result in Anomalies (KB 2134)
  • Installer Crashes During RPM Transaction While Upgrading ESX Server 2.x to 3.0 (KB 2195)
  • ESX Server 3.0 Does Not Properly Support Upgrading Multi-Boot Installations (KB 2199)
  • Additional VI Clients Unable to Connect to an ESX Server Host During a VMFS2 to VMFS3 Upgrade (KB 2236)
  • Traffic Shaping Configuration Is Lost When Migrating or Upgrading Virtual Machine From ESX Server 2.x to ESX Server 3.0 (KB 2164)


  • Firewall Disabled Running Service Iptables Start (KB 2160)
  • Nessus Generates a Warning Indicating a VERITAS Backup Exec Security Advisory for Windows Servers (KB 2206)
  • Nessus Generates a Warning for Vulnerability at Port 9 with the Ascend Router (KB 2299)


  • Some Pre-Checked Items Cannot Be Checked Back to License Pool (KB 2170)
VMware Consolidated Backup (VCB) Issues
  • Only One Virtual Machine Appears in Legato Networker IM GUI After Backing Up Multiple Virtual Machines (KB 2144)
  • File-Level Backup of a Virtual Machine with an Uninitialized Disk Fails (KB 2147)
  • Warning on VCB Disconnect from VirtualCenter Server (KB 2151)
Server Configuration IssuesNetworking
  • NIC Team Stops Working After ESX Server Upgrade (KB 2201)
  • VMware VirtualCenter and VMware ESX Server Provide Datastore URLs with Different Formats (KB 2305)
  • Intermittent VMotion/NFS/ISCSI Failures Can Be Caused by Duplicate IP Addresses on your Network (KB 2253)
  • Using Qlogic FC-HBA I/O Stalls on EMC Symmetrix (KB 2287)
  • Virtual Machines or Processes Hang When ISO Image Is Used from Service Console NFS Share (KB 2296)
  • VirtualCenter and 'esxcfg-vswitch - l' Show Different Number of Ports (KB 2091)
  • After VMFS Upgrade, VMX File Must Be Edited to Address Condition Producing Errors on Virtual Machine Startup (KB 2237)
  • NIC Stops Transmitting When Using Broadcom 5700 Rev 14 and 5701 Rev 15 for Heavy Traffic (KB 2242)
  • VI Client Loses Connectivity to the ESX Server System Host After Adding a new NIC (KB 2243)
  • SendTargets Processes Run by iSCSI Software Initiators May Cause ESX Server to Freeze(KB 3344257)
  • Some Storage Applications May Require Firewall Ports Be Opened(KB 2143)
  • In-Place Upgrade Only for Virtual Machines with RDM Disks (KB 2204)
  • MSCS Clustering Can Trigger an Unnecessary Failover to the Backup Server on the IBM FastT Series Arrays (KB 2161)
  • SAN LUNs Not Visible in VirtualCenter UI but Visible in MUI (KB 2278)
  • Using HP Insight Manager 7.5.1a, Storage Controller Adapters Are Not Shown (KB 2223)
  • Upgrading VMFS-2 Volume May Fail Due to Insufficient Free Space (KB 2210)
  • Doing Multiple vmfs Upgrades at the Same Time Just Upgrades the First One (KB 2211)
  • Additional VI Clients Unable to Connect to an ESX Server Host During a VMFS2 to VMFS3 Upgrade (KB 2236)
  • Cannot See the /vmimages Datastores Directory When Attempting to Mount an ISO Image on a VirtualCenter 2.0-Managed ESX Server 2.x Host (KB 2162)
  • When Using Serial Ports That Are Connected to Named Pipes, Relative Paths and Locations on VMFS Cannot Be Used (KB 2192)
  • Create Datastore Operation Might Fail if the Disk also Contains the ESX Server Service Console File System (KB 2240)
  • No Protection Against Deleting a Disk Backing File That Is Also Used by Another Powered-Off Virtual Machine (KB 2245)
  • Disabling the Qlogic PCI Device in BIOS Results in a PSOD (KB 2209)
  • NFS Mounts Are Restricted to 8 by Default (KB 2239)
  • Problems with Configuring qla4010 Card when ESX Server Boots from iSCSI (KB 2207)
  • System Time Accounting Incorrect for Software iSCSI (KB 2208)
VirtualCenter, VI Client, and Web Access Issues
  • Inaccessible Virtual Machines Are Named 'Unknown VM' (KB 2172)
  • Real-time Statistics Data Has Gaps for the Host in VirtualCenter 1.x After Being Managed by VirtualCenter 2.0 (KB 2198)
  • Intermittent SSL Warnings Appear During Logoff (KB 2169)
  • Server on Localized Operating System Fails to Recognize Certain Locales (KB 2178)
  • After I Move a Host out of a Cluster, the VI Client Inventory Doesn't Show the Host's Virtual Machines (KB 2165)
  • Error Message in VI Client Indicates That esx.conf.WRITELOCK Cannot Be Obtained (KB 2183)
  • After a Host Failure, when the Host Boots Up, the HA Service Does Not Start Up and an HA Error Occurs on the Host (KB 2300)
  • Browse Datastores Option of the VI Client Cannot Recognize .vmdk File Created by vmkfstools (KB 2171)
  • Unable to Log Onto the VI Client (KB 2184)
  • Incorrect Input Text in Configuration Wizards Can Cause Unhandled Exceptions (KB 2186)
  • Export Diagnostics Option in the VI Client Might Fail to Resolve Host Names on Other Domains (KB 2187)
  • VI Client Fails to Add a Host (KB 2257)
Virtual Machine Management Issues
  • Different Error Messages for the Same Event (KB 2174)
  • In Certain Fibre Channel Environments, VMotion Does Not Succeed and the Virtual Machine Remains Running on the Source Machine (KB 2265)
  • Some Virtual Machines Might Not Power on Even if Their Reservation Is Less Than the Unreserved Capacity of Their Parent Resource Pool (KB 2158)
  • Taking Snapshots of Upgraded Virtual Machines in Nonpersistent Mode Is Not Allowed (KB 2175)
  • Floppy and CD-ROM Settings Are Dimmed When I Switch Between Other Hardware Options (KB 2179)
  • Virtual Machine Startup/Shutdown Host Settings Require an Action and Delay Be Specified (KB 2190)
  • Virtual Machine Startup/Shutdown Host Settings Do Not Reflect Changes to Virtual Machine Settings (KB 2194)
  • vmware-cmd Doesn't Recognize Symbolic Links to VMFS3 (KB 2122)
  • Delays When Writing to a New Virtual Disk for the First Time (KB 2191)
  • Incorrect Error Message when a Virtual Machine Backed Up on ESX Server 2.x Is Restored to ESX Server 3.x (KB 2307)
  • The Virtual Machine May Still Be Running when VmPerl::VM::stop and 'vmware-cmd stop' Return (KB 2295)
  • Virtual Machine Powers Off if Attempting to Connect SCSI Device in a Powered On Virtual Machine (KB 2248)
  • Installing VMware Tools from Virtual Infrastructure Client Does Not Eject CD-ROM from a Solaris Guest (KB 2157)
  • Failure to Connect to CD-ROM due to Incorrect Path (KB 2303)
  • Re-Editing a Virtual Machine Before a Previous Edit Completes Fails (KB 2205)
  • Changing the Power Options in Virtual Machine Gives an Error Message if the Virtual Machine Is Powered On (KB 2251)
  • Unable to Run Tools Upgrader for Autotools Installation and Upgrade (KB 2121)
  • Intermittent Virtual Machine Failures with NIS-Enabled ESX Server Hosts (KB 2255)
  • VMotion Fails at 90% Progress when the Virtual Machine's Parallel Port Is Set to Write to an Output File (KB 2284)
  • The Virtual Machine Seems to Be Installing VMware Tools but the Tools Never Get Installed (KB 2277)

Guest Operating System

You can find the latest version of the Guest Operating System Installation Guide by following these links: HTML PDF Japanese PDF.

  • Negative Numbers Sometimes Appear for Disk Sizes in SMC 2.1 on the Solaris 10 Operating Environment and Update 1 (KB 2215)
  • Cloning a Windows Virtual Machine Can Fail if the Virtual Machine Has a Nonstandard BootExecute Value (KB 2246)
  • Large Network Transfers Can Cause a Solaris 10 Virtual Machine's Network Connection to Hang (KB 2176)
  • Solaris 10 Update 1 Virtual Machines Might Not Properly Discover and Configure the Virtual Floppy Device, Virtual Parallel Port, or Virtual Serial Port (KB 2270)
  • If No DHCP Server Is Available When a Windows Virtual Machine Is Customized, the Virtual Machine Might Not Be Able to Join a Domain (KB 2262)
  • Solaris 10 U1 Guest Operating System Is Not Supported on EMC CLARiiON Series and Symmentrix Series Storage Arrays (KB 2289)
  • Customization of a Virtual Machine on a Linux Guest Might Fail (KB 2301)
  • Older Guest Operating System Exhibits Unusual Behavior (KB 2225)
  • Solaris Warning 'Stopped tracking Time of Day Clock'(KB 2250)
  • Dell PowerEdge 6850 Hosts Running ESX Server 3.0 Need A03 BIOS to Install 64-Bit Guests (KB 2087)
  • Display and Mouse Problems in Solaris 10 Virtual Machines (KB 2254)
  • Excessive Network Error Messages Detected in Solaris 10 Virtual Machine (KB 2258)
  • Installation of 64-Bit Red Hat Enterprise Linux, Updates 3, 5, 6, 7, and 8 SMP Kernel Occasionally Fails with Anaconda ImportError Message (KB 2260)
  • Red Hat Enterprise Linux Advanced Server 3.0 64-Bit Guest Produces Error on Intel VT Host (KB 2263)
  • 64-Bit Linux Guests with Computer Using More Than 4 GB of Memory Might Experience a Guest or vmware-vmx Panic (KB 2269)
Miscellaneous Issues
  • Hewlett Packard DL760 G2 Servers Issue Warnings Whenever You Load the VMkernel (KB 2145)
  • VirtualCenter's Datastore Browser Does Not Display Virtual Disk Files for Virtual Machines on ESX Server 2.x Hosts (KB 2203)
  • Auto-Start Is Not Run When Manually Restarting a Host in Maintenance Mode (KB 2214)
  • Disconnecting or Removing a Host Deletes a Scheduled Task (KB 2180)

Resolved Issues

The following are known issues in Virtual Infrastructure 3.0, which have since been resolved.

Install Issues

  • iLO2 Virtual Media on a ML570 G4 or DL570 G4 Fails (KB 2285)
  • ESX Server Installer Is Unable to See Disks if Both SAS and SCSI Controllers Are Used (KB 2167)
  • Customization Is Broken when WorkStation 5.x or VMI 1.5 Are Installed on the same Machine as VirtualCenter Server 2.x (KB 2297)

Upgrade Issues

  • Cold Migrating a Virtual Machine from ESX Server 2.x to 3.0 Fails (KB 2182)
  • Virtual Machines That Were Participating in Auto-Start Are no Longer Involved in Auto-Start (KB 2232)
  • Legacy Templates Fail After Upgrading Shared LUNs to VMFS-3 from Another Host (KB 2235)
  • Upgrade Relayout Virtual Machine Operation Fails (KB 2181)
  • VirtualCenter 1.x to VirtualCenter 2.0 Database Upgrade Using Oracle May Fail (KB 2304)
  • Upgrading from VMFS-2 to VMFS-3 May Make VI Client on ESX Server Unresponsive (KB 2233)
  • VMFS Volume Upgraded From VMFS-2 to VMFS-3 May Display as Read-Only After Upgrading (KB 2197)


  • VC License Server Settings May Override ESX Server Host Settings (KB 2212)
VMware Consolidated Backup (VCB) Issues
  • Using 'pre-command.bat' and 'post-command.bat' as Described in the README for the Netbackup Integration Module for VCB Does Not Work as Expected(KB 2249)
  • File-Level Backup with VCB Fails When Attempted With Six or More Virtual Disks on the Backup Proxy (KB 2185)
  • Backing Up Virtual Machine with vcbMounter from ESX Service Console Fails
    A bug preventing vcbMounter running on the ESX Server service console to back up a virtual machine hosted by a different ESX Server system has been fixed. You can now back up any virtual machine within a farm of ESX Server systems managed by the same VirtualCenter instance and sharing a common pool of virtual disk images. You back up a virtual machine by running vcbMounter on the service console of any ESX Server system in the farm. To use this feature with ESX 3.0.1, point vcbMounter to the VirtualCenter server managing the farm.

Server Configuration Issues

  • Service Console Networking Stops Working When Using vmxnet_console and Upgrading From ESX Server 2.x to 3 (KB 2202)
  • Eleven Connections Appear on the Database Server Even Though the User Set the Maximum Number of Database Connections to a Value Less Than Ten (KB 2302)
  • Using Intel e1000 NICs With Certain PCI IDs May Cause Kernel Panic (KB 2221)
  • Network Connectivity Is Lost and 'WARNING: Uplink: 1925: Couldn't allocate pkt for frame copy' Appears in the Log (KB 2274)
  • Configuring a Duplicate IP Address for VMotion Causes an Error (KB 2224)
  • ESX Server 2.1.x and 2.0.x Do Not Provide Expected Configuration or Information for Raw Disks (KB 2133)
  • A Mapped SAN LUN Added to a Virtual Machine Is Not Visible from the List (KB 2216)
  • Legacy Templates Will Fail After Upgrading the Shared LUN to VMFS-3 From Another Host (KB 2235)
  • Problems when Using Emulex Fibre Channel Cards in Extreme Failover Conditions (KB 2244)
VirtualCenter, VI Client, and Web Access Issues
  • 'A Specified Parameter Was not Correct' Error in the VI Client Interface When a Virtual Machine Is Powered On (KB 2173)
  • Changes Made for Database Password or Maximum Number of Database Connections to Be Created in VI Client Do Not Take Effect Until the VirtualCenter Service is Restarted (KB 2218)
Virtual Machine Management Issues
  • Cannot Power On Virtual Machine That Has two or More CPUs (KB 2159)
  • Creating a Virtual Machine or Disk on Host Client Fails When You Try to Create a Virtual Machine Disk Larger Than 262GB (KB 2177)
  • All Paths to a LUN Are No Longer Accessible and an Infinite Abort Loop Results (KB 2298)
  • Virtual Machine Cloning and Customization Operations Fail on Virtual Machines with Two Network Adapters Connected to One Network (KB 2200)
  • System PSOD:'Spin count exceeded (EventQueue, 448) - possibile deadlock' Message (KB 2306)
  • Windows Virtual Machines with Latency-Sensitive I/O Workloads May Slow Down in Four-Way SMP Configurations (KB 2231)

Guest Operating System

  • Remote Floppy Does Not Work in Solaris 10 Operating Environment, Update 1 (KB 2220)
  • 64-Bit Red Hat Enterprise Linux 4 Hangs During Installation (KB 2229)
  • Storage Drivers for the VMware LSILogic Storage Adapter Are Not Available in Windows XP (KB 2241)
  • Blue Screen On Windows 2003 SP1 When Mounting Volumes (KB 2267)
Miscellaneous Issues
  • VMotion Fails to Migrate Virtual Machine When Target System Runs ESX Server Version 2.5.3 or Lower (KB 2155)
  • Virtual Machine Changes to Snapshot-Consolidate Mode During Delete-All-Snapshot Operation (KB 2222)
  • HA Configuration Tasks Fail and an Error Message Appears When I Configure an HA Cluster (KB 2135)
  • Configuring HA Task Fails or Virtual Machine Failover Does Not Happen (KB 2259)
  • Template Upgrade Fails with Error, 'Name Already Exists' (KB 2196)
  • Re-enabling Never Takes Effect If you Re-enable After the Active Directory 'Enable Validation' Setting Is Disabled for a While (KB 2279)

Complete Desktop Virtualization Solution Now Available for the Enterprise and Supported by Dell, HP, IBM, NEC and Wyse Technology

PALO ALTO, Calif., January 30, 2008 — VMware, Inc. (NYSE: VMW), the global leader in virtualization solutions from the desktop to the data center, today enhanced its Virtual Desktop Infrastructure (VDI) solution with the new VMware Virtual Desktop Manager 2. Available immediately, VMware Desktop Manager 2 allows users to securely connect to their virtual desktops in the data center and gives IT administrators an easy and cost-effective way to manage virtual desktops. Major industry leaders, including Dell, HP, IBM, NEC and Wyse Technology, have embraced and extended VMware’s virtual desktop solution, making it a complete desktop virtualization solution for the enterprise.

VMware VDI integrates VMware Infrastructure 3 and VMware Virtual Desktop Manager 2 and provides an easy-to-manage desktop virtualization solution that takes advantage of virtualization technology used by more than 100,000 organizations. VMware VDI streamlines desktop management, reduces operational costs and provides business continuity capabilities that until now were available only for mission-critical server applications. By leveraging the capabilities of VMware Infrastructure 3, no other desktop virtualization solution offers comparable enterprise-class performance, reliability, security, manageability and seamless integration in a single solution.


VMware Virtual Desktop Manager 2 is a desktop management server that connects users to virtual desktops in the data center. With VMware Virtual Desktop Manager 2, end users can securely access their virtual desktops using either a personal computer or thin client. The product’s easy-to-use interface lets administrators manage thousands of desktops at once, and reduces the time it takes to provision a new desktop from hours to minutes.

“With VMware VDI, we’ve taken our desktop virtualization implementation to the next level and made our investment in VMware virtualization go even further,” said Steve Beaver, systems administrator at Florida Hospital. “VMware’s enterprise-class Virtual Desktop Manager 2 gives us a tightly integrated desktop virtualization solution that lets us rapidly provision new desktops to end users, reduce our support costs and manage desktops more efficiently across our organization.”

“The addition of VMware Virtual Desktop Manager to VMware VDI provides us with a complete desktop virtualization solution that extends our existing investment in VMware Infrastructure,” said Ian Mellor, network infrastructure and application consultant at the Association of Teachers and Lecturers. “This end-to-end solution enables us to leverage robust business continuity and disaster recovery capabilities while simplifying management, reducing operating costs and increasing control of our desktop deployments. Our users benefit from increased service levels while our IT staff benefits from reduced complexity.”

“Our customers are deploying VMware desktop virtualization solutions in greater and greater numbers,” said Jeff Jennings, vice president of desktop products and solutions at VMware. “Our expanded VDI solution now provides these organizations with a complete and integrated end-to-end desktop virtualization solution. Customers can now manage virtual desktops with greater levels of operational efficiency, flexibility, and security.”

VMware also works with numerous ecosystem partners to embrace and extend its desktop virtualization solution.

Vmware Virtual Infrastructure Client 2.0 Download Free

“Dell is simplifying client computing with Flexible Computing Solutions – validated offerings that centralize data and image control by combining hardware, software, services and support,” said Darrel Ward, director of Dell Product Group. “VMware’s Virtual Desktop Manager will help us build on our flexible approach to alternative computing with centralized data control and system management, while providing users anytime, anywhere desktop access.”

“HP and VMware have collaborated on solutions that leverage HP ProLiant and BladeSystem servers, HP Thin Clients and VMware virtualization,” said Scott Farrand, vice president of Industry Standard Server Software at HP. “The new VMware VDI offering provides manageability, security and reliability to enhance HP’s Remote Client Solutions portfolio, and complements HP platforms for our joint customers.”

“Desktop virtualization plays a key role in reducing complexity and costs for today’s end users,” said Jan Jackman, Global Technology Services VP of End User Services at IBM. “VMware Virtual Desktop Manager 2 is included as part of our Virtual Infrastructure Access (VIA) service product, which is offered as a project-based, managed service. This enables our joint customers to benefit from increased levels of manageability, mobility, reliability and security all for a low monthly fee per end user.”

“VMware’s VDI solution is an excellent platform for NEC’s Virtual PC Center solution because it supports virtual desktops running Microsoft Windows XPe,” said Ken Hertzler, director of Server Platform Group at NEC Corporation of America. “NEC looks forward to working with VMware on continued support of VMware Virtual Desktop Manager.”

“VMware Virtual Desktop Manager complements our support for the VMware VDI solution in our thin client products,” said Curt Schwebke, CTO of Wyse Technology. “As desktop virtualization continues to gain traction as a game-changing tactic to reduce IT complexity, we’ll continue to engage with VMware to develop effective desktop solutions for our mutual customers.”

Availability, Packaging and Pricing (in USD):

VMware VDI and Virtual Desktop Manager 2 are available today. Pricing for VMware VDI is based on a list price of $150 per concurrent user and is packaged into two bundled offerings: the VMware VDI Starter Edition and the VMware VDI Bundle 100 Pack. Both bundles include VMware Infrastructure Enterprise Edition for VDI (which consists of VMware ESX Server 3.5 and VirtualCenter 2.5) and the VMware Virtual Desktop Manager 2. The VMware VDI Starter Edition, which enables 10 virtual desktops, has a list price of $1,500. The VMware VDI Bundle 100 Pack, which enables 100 virtual desktops, has a list price of $15,000. Customers may add on to either edition by purchasing additional licenses in increments of 10, based on the list price of $150 per concurrent user.

A la carte pricing for VMware Virtual Desktop Manager 2 is also available to current VMware VDI users for $50 per concurrent user, and it can be bundled with VMware Infrastructure. Customers can also download a 60-day evaluation of VMware VDI from www.vmware.com/download/vdi/eval.html.

All prices here are list prices for purchase directly from VMware.

For additional information about VMware VDI, please visit: www.vmware.com/products/vdi/.

About VMware


Vmware Virtual Infrastructure Client 2.0 Download For Pc

VMware (NYSE: VMW) is the global leader in virtualization solutions from the desktop to the data center. Customers of all sizes rely on VMware to reduce capital and operating expenses, ensure business continuity, strengthen security and go green. With 2007 revenues of $1.3 billion, more than 100,000 customers and more than 10,000 partners, VMware is one of the fastest growing public software companies. VMware is based in Palo Alto, California and on the web at www.vmware.com.

Vmware Virtual Infrastructure Client 2.0 Download Windows 10

# # #


VMware is a registered trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.

This release contains “forward-looking statements” as defined under the Federal Securities Laws. Actual results could differ materially from those projected in the forward-looking statements as a result of certain risk factors, including but not limited to: (i) adverse changes in general economic or market conditions; (ii) delays or reductions in consumer or information technology spending; (iii) competitive factors, including but not limited to pricing pressures and new product introductions; (iv) the transition to new products, the uncertainty of customer acceptance of new product offerings and rapid technological and market change; (v) insufficient, excess or obsolete inventory; (vi) war or acts of terrorism; (vii) the ability to attract and retain highly qualified employees; (viii) fluctuating currency exchange rates; and (ix) other one-time events and other important factors disclosed previously and from time to time in VMware’s filings with the U.S. Securities and Exchange Commission. VMware disclaims any obligation to update any such forward-looking statements after the date of this release.