vSphere 6.7 Update 1 Available

You have probably already seen this in the news already but vSphere 6.7 Update 1 has now released to download. Link Is below in case you need it:

vSphere 6.7 Update 1 Download Link


Also to get a bit more info on whats under the hood on the updated vSphere web client i would recommend the following:





So far VEEAM is the only thing ive heard so far that has an issue: https://www.veeam.com/kb2784

New Release: PowerCLI 11.0.0

New version of  PowerCLI released version 11

Heres a brief breakdown of the updates included:

  • Added a new Security module
  • Added new cmdlets for Host Profiles
  • Added a new cmdlet to interact with NSX-T in VMware Cloud on AWS
  • Support for vSphere 6.7 Update 1
  • Support for NSX-T 2.3
  • Support for Horizon View 7.6
  • Support for vCloud Director 9.5
  • Multiplatform support for the Cloud module
  • Updated the Get-ErrorReport cmdlet
  • Removed the PCloud module
  • Removed the HA module

Dont forget its easy to update your powercli version (see below)

Update-Module VMware.PowerCLI


And finally heres a link to the vmware article with all the info


vCloud Identifying Chain Linked VM’s

Currently working on a project to decommission a very old non updated vcloud infrastructure for a customer who wants to move back to vsphere. They don’t really utilize the full vCloud feature set as it was put in as part of a larger project that never came to fruition.  Part of the first step should be to see what chain linked virtual machines we have, as if not when we attempt to migrate them away we are just going to give ourselves a world of pain. The PowerCLI below should identify all the virtual machines within the VDC’s and how long the chain length is.


if( (Get-Module -Name "VMware.VimAutomation.Cloud" -ErrorAction SilentlyContinue) -eq $null)

{Import-Module VMware.VimAutomation.Cloud}

Connect-CIServer -Server "your vcloud director fqdn" -ErrorAction Stop

$VApps = Get-CIVApp

Foreach($vapp in $VApps){

$vms = $vapp.ExtensionData.children.vm

foreach($vm in $vms){

$CL = $vm.VCloudExtension.any.VirtualDisksMaxChainLength

if($CL -gt 1){

$info = $vm.Name + " chain length=" + $CL



PowerCli List HBA WWN’s

Whenever you get storage masked to your esxi node/cluster you always going to need to know what HBA WWN addresses are (assuming your using HBA not iSCSI etc) here is a quick powercli hba statement you can use to refresh your memory


For a cluster the following:

Get-Cluster clustername | Get-VMhost | Get-VMHostHBA -Type FibreChannel | Select VMHost,Device,@{N="WWN";E={"{0:X}" -f $_.PortWorldWideName}} | Sort VMhost,Device


And if you want to do a single host:

Get-VMhost -Name hostname| Get-VMHostHBA -Type FibreChannel | Select VMHost,Device,@{N="WWN";E={"{0:X}" -f $_.PortWorldWideName}} | Sort VMhost,Device



Perennial Reserved RDM’s

I got asked a couple of days about why an esxi server was taking roughly 45 mins to come back up after a reboot. Looking at the node when it eventually came back up showed that it had a number of RDM’s that were associated to virtual machines. Those virtual machines were mostly Windows RDM’s  used for MSCS. What was happening is that when esxi was booting it could see all theses luns and was trying to read the header, it was that delay in its attempts to read the header that was causing the 5 min boot time.

What was needed was to reserve those luns so that they were ignored on the boot scan. Using the powercli below we can define the target cluster, scan through the virtual machines within an identify all the raw devices and mark then as reserved.  It will then do this on each nodes in the cluster which reduced your boot time from say 45mins to a few minutes (depending on your hardware)


$TargetCluster = "Cluster Name"

$VMhosts = Get-Cluster $TargetCluster| Get-VMHost

$RDMDisks = Get-VM -Location $TargetCluster | Get-HardDisk -DiskType "RawPhysical","RawVirtual" | Select ScsiCanonicalName

foreach($VMhost in $VMhosts) {
Write-Host "Connected To Server : " $VMhost
$esxcli = Get-ESXCLI -VMHost $VMhost
foreach($RDMDisk in $RDMDisks) {
Write-Host "Setting Perennially Reserved On : " $RDMDisk
$esxcli.storage.core.device.setconfig($false, ($RDMDisk.ScsiCanonicalName), $true)

Studing For VCP6-NV (2V0-642) (UPDATE – I Passed ?)

Quick update i took the exam on Friday morning and happy to say passed with a score of 433 (300 is the pass mark).

Personally i think it was a tricky exam but not as difficult as i anticipated it to be, i used the references ive already mentioned before and bolstered it up with 2 pluralsight courses i got access to on a 6 month trial basis.

I’m not going to go into the question i was given but i would say if you follow the links ive provided and the VMware blueprint  you should be ok.



Im a VMware vExpert 2018

To add to an already amazing year in world of virtualisation, today I was named a VMware vExpert 2018 . I’m honoured, humbled, and proud of my contributions to this amazing virtualisation community. The vExpert list is constantly growing, and it’s amazing to be part of this list of experts.

vExperts demonstrate significant contributions to the community and a willingness to share their expertise with others.

Studing For VCP6-NV (2V0-642)

So not had a chance to post much recently as im studying for my VCP6-NV (2V0-642). Figured i would post a couple of the places i have been using:

  1. These excellent vBrownBag Sessions

2. VMware Hands on Lab (HOL)

3. NSX 6.2 Documentation


vSphere Web Client (Flash) And Windows 2016

Had an interesting one the other day,  deploying windows 2016 servers for a customer, setting one up as a jump server for support staff i naturally wanted to check that we could access the vSphere web console correctly using both flash and html variants.

By reading this post you can imagine that it didn’t work due to our old friend flash. However there is an easy fix

dism /online /add-package /packagepath:"C:\Windows\servicing\Packages\Adobe-Flash-For-Windows-Package~31bf3856ad364e35~amd64~~10.0.14393.0.mum"


Running this will get the respective flash component installed to enable you to use the web client again. More details are available at Technet Article


ESXi And Windows Domain Controller Time Source

Bit of an old reference for the day but one i must admit i have forgotten previously, when using a windows domain controller time source for your ESXi infrastructure you may notice that with the default settings you find that it wont synchronize.

Thankfully VMware have a workaround that requires a couple of changes on the ESXi hosts to change the NTP client settings. Instructions are even provided on how to configure you domain controllers w32time service to point to one of the many internet NTP services so you always have good/reliable time source configured.


For the ESXi client NTP changes heres the article reference https://kb.vmware.com/s/article/1035833


« Older posts