vSphere Web Client vs. vSphere Client Appl. (c#)

VMware itself tells us to migrate to the new Web Client, because many of the new features are only available on the Webinterface and not integrated into the old vSphere Client Application.

BUT: there are also features, you’ll miss in the Web Client. You’d like to connect a ESX directly? Not possible. You like the Maps feature? You’ll miss it. Shame on you VMware.

Here’s my list of Features.

Only in vSphere Client Application

  • Maps for vCenter
  • old Plugins (most will work, not not all)
  • direct connect to ESX Host
  • Custom Attributes
  • Update Manager, editing Baselines

Only in Web Client

  • Tags
  • vSphere Replication
  • shared nothing vMotion
  • vmdk >2TB
  • vm Hardware v10


Florian Grehl created a more detailed list at his blog virten.net:

VMware itself also published a document “Which vSphere client should I use?”:

About Update Manager:

Get Pagefile usage of all running VM’s in inventory

Get Pagefile usage of all running VM’s in inventory

function Get-PagefileUsage {
$tabelle = @()
Get-VM | ? {$_.PowerState -like "PoweredOn"} | % { 
   $collect                =   "" | Select Name, PagefileUsage, TotalvRAM
   $collect.Name           =   $_.Name
   $collect.PagefileUsage  =   (Get-WmiObject Win32_PagefileUsage -ComputerName $_.Guest.Hostname).CurrentUsage
   $collect.TotalvRam      =   $_.MemoryMB
   $tabelle += $collect
$tabelle | Export-Csv $env:userprofile\Desktop\PagefileOverview.csv
Write-Host -fore yellow "Tabelle exportiert auf den Desktop als PagefileOverview.csv"

What does *CPU ready time* mean

In ESX / vSphere Environments you maybe already discovered a value called “CPU ready time”. And the confusing thing is, this value doesn’t tell you how long the VM was ready this day 😉

The whole definition can be found fully detailed in a VMware PDF here.

To get a quick explanation, I found a good forum thread where it’s explained quite good:

The rub comes when you have multi core VMs – regardless of the amount of CPU needed by the VM (lets say its a 4 core VM, and only needs 1 core worth of power), it needs to schedule onto 4 cores (because it is a 4 core VM).  While it is scheduled onto 4 processor cores, nothign else can use them, even though that VM isn’t really using all that they can do.  So, when you have a lot of low usage VM’s with 2 or 4 cores, you end up with problems scheduling them onto cores, and not so much the speed of the CPUs themselves.  Hence, the need to watch your CPU Ready times.

Source: http://communities.vmware.com/thread/130310