Difference between Web Client and Fat Client (and PowerCLI 'client') - vSphere 5.5

Note that VMware vSphere 5.5 VM's can be managed with VMware Workstation 10 and higher.

This article is an attempt to maintain a comparison between vCenter Web Client and the vCenter .net Client (aka, Fat Client).

Feature	.Net Client (Fat Client)	Web Client	PowerCLI
VMotion VM between Datastore AND Host at the same time	No	yes	yes
VMotion between Hosts	Yes	Yes	Yes
Vmotion Between Clusters	No	Yes	Yes
VMotion Between Datacenter	No	Yes	Yes
VMotion Between vCenters (requires Linked Mode)	No	Yes	Yes
Schedule vHardware Upgrade	No	Yes	Yes
Edit VM's with VMX-10 vHardware Supported Versions[vi]: http://kb.vmware.com/kb/2007240	No	Yes	Yes
Hot Add vCpu & vMem to VM While Power On -- Windows 2008 and lower	Yes	Yes	Yes
For Windows 2012r2	No	Yes	Yes
vCenter UpdateManager Scan	Yes	Yes	Yes
vCenter UpdateManager Patch	No	Yes	Yes
Alerts - Acknowledge and Clear	Yes	Yes	Not Native
Host Profile Creation	Yes	Yes	Yes
Host Profile Editing	Limited	Yes	Limited

 

Vmware has pretty much screwed up Host Profiles. It worked great in 4.0. Got worse with 5.0/5.1. It's no better in 5.5. The mitigating aspect of HostProfiles is that you can script away with PowerCLI most of the HostProfile frailties. That said, why use HostProfiles at all if you can standardize a VMhost configuration with scripts?

Improve and Increase VMotion Performance

1           Improve VMotion Performance

Configuring Multi-NIC vmotion in vSphere 5.5 provides much improved performance for VMOTION by creating a vmotion vmkernel for each NIC on a vswitch.  Muli-NIC vmotion began support since vSphere 5.0.  

1)      Select t vSwitch for Vmotion that contains 2 or more VMNIC utilized for vmotion.

2)      Create a VMkernel vmotion portgroup and give it the name "vmotion01″ and assign IP address on the supported VLAN.

3)      Repeat, and create a second VMkernel Interface and give it the name "vmotion02″.
The vSwitch should appear with 2 vmkernel Portgroups as follows:

Figure 8 VMotion Multiple Portgroups

4)      Per Figure 9, edit the vmotion01 NIC Teaming  tab assigning vmnic1 NIC-port as active and all others as "standby."

5)      Go to the settings of vmotion02 and configure a different NIC-port as active and all others as "standby."

vmotion01 vmnic configuration	vmotion02 vmnic configuration

 

Reference: Multi-NIC VMotion configuration: http://kb.vmware.com/kb/2007467