Latest Version: 2.8 | January 31, 2010
RVTools is a windows .NET 2.0 application which uses the VI SDK 2.5 to display information about your virtual machines and ESX hosts. Interacting with VirtualCenter 2.5, ESX 3.5, ESX3i or ESX4i RVTools is able to list information about cpu, memory, disks, nics, cd-rom, floppy drives, snapshots, VMware tools, ESX hosts, datastores, switches, ports and health checks. With RVTools you can disconnect the cd-rom or floppy drives from the virtual machines and RVTools is able to list the current version of the VMware Tools installed inside each virtual machine. and update them to the latest version
On vHost tab field "# VMs" now only powered on VMs are counted.
On vHost tab field "VMs per core" now only powered on VMs are counted.
On vHost tab field "vCPUs per core" now only powered on VMs are counted.
On vDatastore tab field "# VMs" now only calculated for VM’s which are powered on.
Health check "Number of running virtual CPUs per core" now only powered on VMs are counted.
Health check "Number of running VMs per datastore" now only powered on VMs are counted.
During Installation there will be an application event source created for RVTools. This to fix some security related problems.
Some users run into a timeout exception from the SDK Web server. The default web service timeout value is now changed to a higher value.
New fields on vHost tab: NTP Server(s), time zone information, Hyper Threading information (available and active), Boot time, DNS Servers, DHCP flag, Domain name and DNS Search order
New Health Check: Inconsistent folder names.
Improved exception handling on vDisk, vSwitch and vPort tab pages.
VMware Infrastructure Management Installer | 29 Jan 2010 (Localized version)
VirtualCenter 2.5 Server Update 6 | 29 Jan 2010 | Build 227640
Virtual Infrastructure Client | 29 Jan 2010 | Build 227671
VMware Infrastructure Management Installer | 29 Jan 2010 (English only version)
VirtualCenter 2.5 Server Update 6 | 29 Jan 2010 | Build 227637
Virtual Infrastructure Client | 29 Jan 2010 | Build 227637
Guest Operating Systems Customization Improvements
Customization support for the following guest operating systems has been added in this release:
For more complete information about supported guests included in this release, see the VMware Compatibility Guide.
- Windows 7 Enterprise (32-bit and 64-bit)
- Windows 7 Ultimate (32-bit and 64-bit)
- Windows 7 Professional (32-bit and 64-bit)
- Windows 7 Home Premium (32-bit and 64-bit)
- Windows Server 2008 R2 Standard Edition (64-bit)
- Windows Server 2008 R2 Enterprise Edition (64-bit)
- Windows Server 2008 R2 Datacenter Edition (64-bit)
- Windows Server 2008 R2 Web Server (64-bit)
Support for Firefox 3.x Browsers with VirtualCenter Web Access
This release adds support for Firefox 3.x browsers with VirtualCenter Web Access. Firefox 3.x is not a supported browser for ESX Server 3.5 Update 5 Web Access with this release
Note: In many public documents, VMware ESX Server 3.5 is now known as VMware ESX 3.5, and VMware ESX Server 3i version 3.5 as VMware ESXi 3.5. These release notes continue to use the earlier convention to match the product interfaces and documentation. A future release will update the product names.
Source information: VMware
Information: VMware vCenter Upgrade Guide
The following information provides highlights of some of the enhancements available in this release of VMware ESX:
VMware View 4.0 support – This release adds support for VMware View 4.0, a solution built specifically for delivering desktops as a managed service from the protocol to the platform.
Windows 7 and Windows 2008 R2 support –This release adds support for 32-bit and 64-bit versions of Windows 7 as well as 64-bit Windows 2008 R2 as guest OS platforms. In addition, the vSphere Client is now supported and can be installed on a Windows 7 platform. For a complete list of supported guest operating systems with this release, see the VMware Compatibility Guide.
To use Microsoft Windows Cluster Service in VMware ESX you need to config you’r VM’s with independent persistent disks.
I deployed two Windows 2003 SP2 Enterprise 32-Bit VM’s with both 12 GB of OS disks and two NIC’s. I called these: VMPROS-CL01 and VMPROS-CL02.
VMPROS-CL01 with ip: 172.16.254.78 and for MSCS nic ip: 188.8.131.52
VMPROS-CL01 with ip: 172.16.254.89 and for MSCS nic ip: 184.108.40.206
Registered this VM’s in domain VMpros.nl
By connecting a single host or VC with VI Client I receive this error: “The requested operation is not implemented by the server”
My Virtual Infrastructure Client is configured with PassThroughAuth parameter set for Auto SignOn capabilities. With parameters: "D:\APPS\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe" -passthroughauth -s localhost
Solution: Use the Shortcut in your Menu Start > VMware > “VMware Infrastructure Client” of delete the passthroughauth parameter in the shortcut/target field.
Now I can connect my VC/Host with the VI Client without problems.
The VMware KB 1003926 is very helpful to support problems with your VirtualCenter Server service that won’t start. VMware updated this document 2 September 2009.
- You cannot connect to VirtualCenter
- If you try to connect to VirtualCenter, you see the error:
Cannot connect to host <server>: No connection could be made because the target machine actively refused it.
- If you try to start the VMware VirtualCenter Server service, you may see the errors:
By cloning of my my vCenter VM I get this error: “Number of virtual devices exceeds the maximum for a given controller”
- Convert template to virtual machine;
- Edit settings of virtual machine;
- Choose correct network for template;
- Convert virtual machine to template;
- Try to deploy new virtual machine from template to see if it works correct again;
- Converter 4.0 boot cd is missing
- Unable to perform a cold clone with Converter 4.0.
There is no boot CD for Converter 4.0 and it does not support cold cloning.
To perform a cold clone you must: