Download SysCtr 2016 TP4 VHD´s with PowerShell

I have been using and publishing my script for easily download all the VHD´s for evaluating and testing the technical previews of System Center 2016 and now it is time for the TP4! These pre-installed VHD´s make it quite easy to spin up some of the System Center Suite as VM´s on your Hyper-V box within minutes once downloaded.

Here is the script for your convenience and start playing with the new release!



Creating VM´s with configuration version 5.0 on Hyper-V 2016 TP4

Creating a VM in the GUI on a Hyper-V manager with Windows Server 2016 TP4 makes a VM configuration 7.0 by default and once that is done it is not possible to move the VM to a Hyper-V 2012 R2 box.

So if you have a mixed environment and want to be able to move those VM´s to a 2012 R2 Hyper-V box you will have to use powershell to create that VM instead of the GUI. One alternative way is to create them on that 2012 R2 box and then move it to the 2016 but that is not as cool  😉

in the New-VM cmdlet there is a parameter -Version that you can use and set the configuration version to 5.0 instead of 7 and thus enabling it to be compatible with the older version of Hyper-V.

I have two examples in the screendump below where you can see the result,

Screen Shot 2015-11-23 at 13.43.46

My friend Didier has made a blog post about how you upgrade the configuration version if you do not need this backward compatibility and some new features requires the configuration version 7.

Trying to do a Checkpoint on a VM resulting in error 12700

Today I helped a customer that have issues with their new VM´s and doing backup using Veeam and also trying to do Checkpoints within VMM on their Hyper-V 2012 R2 environment.


Looking at the error message from VMM it showed quite clearly that it was just one of the VHDx that was having the issue and looking at where it was residing it showed the reason:

Screen Shot 2015-11-13 at 11.43.59

The file was residing on its own in a CSV volume and directly in the root folder, and as stated in the blog post from the Core Team the VM worker process (VMMS) does not have the relevant permissions on that level and thus getting a access denied error when trying to do a checkpoint.

So how do you solve it? By either manually or with live storage migration moving it into a subfolder which will give the right ACL´s and thus giving the VM worker process rights to create a avhdx file in that folder.

So watch out when you create new VM´s that you actually put all of the virtual disks that belong to it inside folders on those CSV´s!