Vcenter and Vsphere 5.1 U1 released

The release notes can be viewed here:



Storage notes:

Of note on storage, SVmotion renaming of underlying files is fixed, but you must set the parameter and apparantly WWN’s are showing incorrectly in the web client.


Vcenter Operations upgrade from 5.0 to 5.7 on Vcenter 5.0 U2

We recently upgraded to the new VCOPS 5.7 that was released earlier this month and I wanted to document it here for any others that may be doing the same.  I had a few questions based on the install notes at the link below where it states what is needed if installing to 5.0.

In the release notes it states that you need to use the Suite license because your older 5.0 license will not work until you upgrade the license file.  Luckily, along with the .pak download there is a temp key you can download from VMware’s site.  Now, let’s get into the upgrade.

First, you will need to download the .pak file and if using 5.0 download the Suite license along with it.  If you have upgraded your license in the myvmware portal this may not be needed for you.


Log into the VCOPS web portal address which is https://your-vcops-address/admin/


Once logged in, click the update tab at the top and browse to your .pak file that you downloaded:


Choose update and you will get a updating bar while it begins to update and if you log back in you can monitor the update on the update tab as seen in the screenshot below. I  had an issue where I did not have enough space because of a previous upgrade.  In that case, you must login to the UI console and delete temp files from the command line documented in this KB


The update took about 10-15 minutes for me before it was fully done.  If you notice in the notes it mentions “Re-assign license to vcenter Operations Manager asset in the licensing Vcenter”.  This is because it uses the vcops suite.  At this point you either put in your upgraded suite license or use the temp one provided at the download section mentioned earlier in the article.

Put in the license and assign it to your VCOPS assset:


VSphere Management Assistant 5.1 Patch 1 Released

The VMA 5.1 has been released and it finally has a fix for the broken Resxtop certificate issue!  In the previous version you could not run resxtop against your hosts because of certificate issues.

Here is the VMware blog posting:

Release Notes:

Using VUM Powercli for VMTools and Hardware upgrades

We recently had a need to update all of our VMtools and Hardware versions across the enterprise using Vwmare update manager.  We had a special case where we have to update only a group of servers deemed non-production prior to our weekend downtime for production.  We were able to get a VM export list and then pass that list to the cmdlets for Remediate-Inventory.  You can also do this by using custom annotations or any other type of filter you want if you need to specify an exact group of VM’s.

I would like to note that this script does reboot your virtual machines. There are ways to update tools without reboots, but in my experience when doing a large number of VM’s it is best to update and reboot immediately. So, we schedule outage windows for this effort. That being said the newer versions do not require reboots on vmware tools updates 5.1+.

We had a grouping already created so we created a text file and import that:

$vmlist = Get-Content "$vmlist.txt"

The key to the whole thing is that in addition to Powercli you need to download the VUM cmdlets.  You have to have the exact matching Powercli and VUM cmdlets to match your VUM install.  In my case I had to get the 5.0 versions.  You can get the version you need from the release notes here: .

We needed to be able to update both tools and hardware together.  The way you can do this is to do a search for both baselines and set them to a variable using the Get-Baseline VUM powercli cmdlet. I have already attached the baselines at the top datacenter level within VUM for this script to work.

$baselines = Get-Baseline -targettype VM  | where { $ $}

Finally, we need to pass the $vmlist  variable to a foreach loop and then use the Remediate-Inventory command to invoke VUM to update the virtual machines.  I also chose to create a snapshot in case of any issues although if doing hardware you will not be able to revert.

$vmlist | % { Remediate-Inventory -Baseline $baselines -Entity $_ -GuestCreateSnapshot:$true -GuestKeepSnapshotHours 1 -RunAsync -Confirm:$false } 

There it is nice and simple! Here is the full script for any that choose to take it and modify for your needs. You could always pass a Get-VM object or whatever filter to get the list that you need.

Set-PowerCLIConfiguration -InvalidCertificateAction Ignore- Confirm:$false

#Enter in variables
$vcenter = Read-Host "Enter Vcenter Name" 
$vmlist=Read-Host "Enter Server List Filename without extension"
#Connect to Vcenter
Connect-VIServer $vcenter
$vmlist = Get-Content "$vmlist.txt"
$baselines = Get-Baseline -targettype VM | where { $"Tools") -or $"Hardware")}

#send list to Remediat Entity
$vmlist | % { Remediate-Inventory -Baseline $baselines -Entity $_ -GuestCreateSnapshot:$true -GuestKeepSnapshotHours 1 -RunAsync-Confirm:$false }

Disconnect-VIServer -Server * -Confirm:$false