Sonntag, 28. Juli 2019



HP’s done it again. They’ve managed to break their custom ESX ISO on the G6 and G7 servers. I suspect it’s the same for G8.
If like me you found yourself perplexed by the PSOD (pink screen of death) after upgrading from ESX 6.0 to 6.5, keep on reading for the fix (skip to the bottom for the download link to an already fixed ISO).

The issue

It seems the “hpe-smx-provider” driver version 6.5.0 from the ESX 6.5 ISO is causing the PSOD.

The fix and the drawbacks

(Simply) Replace the driver with it’s older counterpart (version 6.0.0) and reinstall (see below for the procedure or check the “download link” section at the very end for an already fixed ISO).  Unfortunately if you decide to create a custom ISO with the previous version of “hpe-smx-provider”, you will no longer be able to upgrade to any future ESX version and will need to do a full installation every time (thank you HP!). That being said, here is the procedure to customize the ISO:

Customize your own HPE ESX ISO

  1. Install PowerCLI from here.  At the time of this writing, the latest version was 6.5.0R1.
  2. Download both the ESX 6.5 and 6.0 offline bundles and save them to a convenient place (ex: C:\HP) — download from this link. To make it easier, rename them to something like and
  3. Open up PowerCLI and do the following:Add the 6.5 bundle

    # check that the profile was loaded and the vendor is HPE

    # clone the profile (feel free to specify whatever you like for the “vendor” when prompted)

    # double check the profile was indeed cloned

    # Remove the “hpe-smx-provider” driver from the clone

    # Add the 6.0 bundle

    # check the profile

    # check driver versions from both bundles

    # Add hpe-smx-provider version 6.00 to the custom profile

    # Export the profile to an ISO

Download links

The following images have hpe-smx-provider version 600. Nothing else was changed. The 6.5.0d (build 5310538) is running on an HP Proliant DL380 G7 since March 2018 and was also tested on a DL380 G6 for a couple of months. For convenience, I’ve also built a 6.7.0 ISO and at the request of a reader, 6.7.0 Update1 from April of 2019:

@THX to

Montag, 8. Juli 2019

Veeam Error – Changed Block Tracking Will Not Be Used For This VM Until You Upgrade the VM Hardware to Version 8.0 or Later on Server 2016

f you have recently upgraded your HyperV Servers or Cluster to Server 2016 and you are running Veeam, you may see the following error:
Changed Block Tracking Will Not Be Used For This VM Until You Upgrade the VM Hardware to Version 8.0 or Later
What this means is that Veeam will only perform FULL backups and not incrementals which is a bit of a crisis for most companies.
Fortunately this is easy to fix, you simply need to upgrade the “Virtual Machine Version” (not to be confused with the Cluster Version, if you are using a Cluster):
  1. On each of your HyperV hosts, shut down all of the VM’s
  2. Run the following PowerShell Command:
    Update-VMVersion *
  3. Run the following PowerShell Command to ensure that all VM’s are at “8”
    Get-VM * | Format-Table Name, Version
Once all of your VM’s are at version 8, you can restart your Veeam backup jobs and all will be well.
For more information on this process read this Microsoft doc.

Rename Onedrive Business root folder

Rename Onedrive Business root folder Here is what I remember: In the Office 365 web admin pages, change the organization name to a shorte...