VMware vCloud suite 5.8 and Horizon View 6.0.1 product updates

Yesterday ( 9 September 2014)  VMware released updates to the vCloud Suite 5.8 suite and VMware Horizon View components.  Here is a overview of the updated products:

 

Error occurred during vCenter operation when editing a VMware Horizon View pool

When editing a VMware Horizon desktop pool in some situations the server error ‘Error occurred during vCenter operation’. appears.

1

The error hasn’t any useful information that says what is wrong. When this error occurs the vCenter Server is unable to find one or more objects listed in the desktop pool. When changing datacenter, cluster or host settings in vCenter the desktop pool must be updated to.  To resolve this error open the desktop pool, select the vCenter settings tab an check or update the Parent VM, Snapshot, Host or cluster, Resource pool and datastores. Also check if the ESXi host with local storage are not in maintenance mode! After updating these settings the error must be gone.

2

 

 

New free tool: Task Manager for Hyper-V

Task Manager for Hyper-V 1.0 is a new free tool from Veeam. Task Manager can connect to a individual Hyper-V hosts and display information about the host and the guest VMs. Real time CPU and memory utilization is displayed.  This can be useful when monitoring or troubleshoot Hyper-V server utilization. Task Manager for Hyper-V requires no installation and is free of charge.

2014-08-14_08h12_11

 

 

 

 

 

 

More information about Veeam Task Manager can be found here

Conflicting VIBS error when upgrading ESXi using the HP ESXi 5.5u1 ISO

When upgrading from VMware vSphere 5.1 Update 2 to vSphere 5.5 Update 1 using the HP 5.5u1 ISO (VMware-ESXi-5.5.0-Update1-1746018-HP-5.74.27-Jun2014) the following error occurred:

<CONFLICTING_VIBS ERROR:Vibs on the host are conflicting with vibs in metadata.Remove the conflicting VIBs or use Image Builder to create a custom ISO providing newer versions of the conflicting vibs. ['Broadcom_bootbank_net-bnx2 – 2.2.5d.v55.2-1OEM.550.0.0.1331820,'Broadcom_bootbank_net-bnx2x_bnx2 – 2.2.5d.v55.2-1OEM.550.0.0.1331820]>

2014-08-12_08h51_43

This issue occurs due to the version numbering of the Broadcom NX2 and Nx2x driver drivers within the HP Custom Image for ESXi 5.5 Update 1, which prevents the upgrade installation of these drivers in ESXi 5.5 Update 1.

To work around this issue use the VMware-ESXi-5.5.0-Update1-1623387-HP-5.73.21-Mar2014.iso. After the upgrade use VMware Update Manager to install the latest patches. Another work around is tocreate custom ISO with the “HP 5.5u1 ISO (VMware-ESXi-5.5.0-Update1-1746018-HP-5.74.27-Jun2014” using  ESXi Image Builder.

More information about this issue can be found here:

  • VMware Community thread, link
  • VMware KB article, link

Installing Update rollup 3 for System Center 2012 R2 Virtual Machine Manager

Update rollup 3 for System Center 2012 R2 Virtual Machine Manager is released this week. This update includes a Linux guest agent upgrade to support the following new operating systems:

  • Ubuntu Linux 14.04 (32-bit)
  • Ubuntu Linux 14.04 (64-bit)

This update also includes the following:

  • Host DHCP extension driver upgrade
  • Several performance improvements??????
  • Several Management Pack package improvements

And a huge list of issues that are fixed. More information can be found in the Microsoft KB article found here, link.

The update can be installed by using Windows Update, WSUS or manual downloading the files and execute them. After the installation of Update rollup 3 execute the SQL Script against the SCVMM database. The SQL script is listed in the Microsoft KB. Don’t forget to update the VMM agents on all the infrastructure server.

2014-08-01_14h21_25

The update of the VMM agents doesn’t require a reboot. The Update Rollup 3 agent version is 3.2.7672.0.

Host DHCP extension driver upgrade

Update Rollup 3 includes an VMM DHCP server extension update for the Hyper-V host.  When using Hyper-V Network Virtualization networks with dynamic IP address allocation, the VM may not get an IP address for a few minutes after the reboot. The new DHCP extension fix this problem. To check the DHCP Extension driver version use the following PowerShell command on the Hyper-V host:

Get-WmiObject -Class win32_product -Filter ‘Name = “Microsoft System Center Virtual Machine Manager DHCP Server(x64)”‘

The new Microsoft System Center Virtual Machine Manager DHCP Server (x64) version is 3.2.7672.0. More information about the installation can be found here.

For more tips see my earlier blog post “Tips for deploying SCVMM 2012 R2 Rollup 2”, Link.