Nutanix for Hyper-V – the future for your datacenter!

Today I had the opportunity to see an Nutanix deployed cluster with Hyper-V. If you have not heard about Nutanix before I urge you to go and check out their website and see how it works. Basically their solutions use local storage for massive performance and their Controller VM has direct access to the disks (a set of SSD and HDD) that also has tiering and dedup and present the storage to the Hyper-V node with a SMB 3 file share, for resiliency the data is replicated to other nodes so in case of an failure your VM´s will start up on another node with all the data.


When you buy an Nutanix solution the Windows 2012 R2 is installed on delivery and you will only configure networking and add the nodes to the Active Directory, so getting your Hyper-V enironment up and running is quite a breeze with this 2U x 4 node solution and it can scale with more 2U sets and this can also be added after you are up and running to scale with your added loads!


As you can see on the features you get both TRIM and ODX functionallity with the solution allowing you to clone or create VM´s within the box in just seconds and also reclaim storage when removing data and VM´s! As you will always use the local controller VM there is no need for SMB Multichannel.

The nutanix will work with your System Center environment and can be automated with VMM and Orchestrator.

I will do a more thorough post about the configuration and setup when I get my hands on a Nutanix-platform!

Wait! Are you going to migrate your old legacy VM´s?

So I have in several posts described different ways on moving from one hypervisor to another with your VM´s. There are several different choices when it comes to the transitioning phase, some more automated than others.


But wait!! Yea I know the virtualization is Gods gift to the IT but it also carries some responsibilities. The technique gives you as the IT admin the possibility to run old legacy operating systems almost forever.

One big thing in the Move projects is to also take into account if the workload running can be upgraded within the OS, not just moved to another virtualization platform. Surely you do not want to describe on your CV that in your last employment you had Windows 2003 Servers as Domain Controllers for instance. Compare it with VHS, do you still watch movies and record stuff on the 80/90´s system?

Tangled video tape

First of all you can use the Microsoft Assessment and Planning toolkit to analyze what of your workloads can be upgraded ( I know, it does not look at your third party server applications that needs some brushing of and upgrading also)

When you have analyzed and got some workloads that can be migrated then check out this page on what tools and wizards you can use to actually smoothen the process for those windows roles and features running on your old and soon to be unsupported OS to an new version! As you can see below, Windows 2008 R2 is coming to the last date of mainstream support!


Yes I know that this often can be a quite burden on the IT department to carry out this kind of transformation projects and for several company-critical applications this can also become a serious cost that someone has to approve or maybe decide to decommission if they live outside of the support window!

Finally the MAT4Move has been released, but where to find it?

Now I found the release of the Migration Automation Toolkit for Double-Take Move. As I described in an earlier post I was waiting for this and now it was released.

It is as described in the readme, a technology preview and for users with PowerShell skills.

Screen Shot 2014-02-03 at 16.58.05

And it has not yet appeared on the Gallery but you can find it on the Vision Solutions Support site (where you will need an account to login), and on the Move download page you see it on the top :-)

Screen Shot 2014-02-03 at 16.44.46

 I will write a more thorough article about how the experience to use it compared to the Vision Solutions Double-Take System Center toolkit in a later blog post!

Test of Altaro Backup v4 for Hyper-V

There are some backup vendors that nowadays have support for Hyper-V and host level backup. I have been testing some of them but also wanted to check how the Altaro Hyper-V Backup solution works.

I cannot complain about the ease of installing and getting started on the Altaro solution. I like the install wizard that directly recognises if I am trying to install on a cluster node or a single hyper-v instance.


Screen Shot 2014-01-27 at 19.12.51

It is fully supported to install on a core or full version of Hyper-V 2012 and also 2012 R2.

When I tested to install on my one-node Hyper-V 2012 R2 cluster it found and promoted the node as a master controller.

Screen Shot 2014-01-27 at 19.14.03

It was really easy to configure the VM´s that should be included in the backup and then schedule a backup job.

Some really nice features in the Altaro are:

  • Offsite backup with wan acceleration
  • Exchange Item Level restore
  • Remote Management Console
  • Fast Hyper-V backup/restore
  • Compression/Encryption
  • Live Backup of Linux VM´s
  • Instant-Boot from backup

If you register then you get a trial that works in 30 days and have the full feature-set. You can also download the free version and that gives you the possibility to do backups on two VM´s forever :-) but with some limitations..


SCVMM 2012 R2 and deploying VM´s with altered name on vhdx

I observed a question on the technet forums regarding if it was possible to change name of the virtual hard disk when deploying a virtual machine or template from System Center Virtual Machine Manager, and the answer is yes.

Having a few hundred VM´s and all of them having the same name of the vhdx as the template might not look so good.

So how to solve this then, first of is when deploying new VM´s you should change the name and that can only be done in the VMM GUI when deploying to a host and not to a cloud. Notice that I create the VM from the template in the library view of the console.

Screen Shot 2014-01-20 at 12.20.07

When using this way the console automatically fills in the guest os name. When creating a VM from a template in the VM´s and Services view that has to be filled in manually.

Screen Shot 2014-01-20 at 12.22.27

So how to get the name of the VM also on the vhdx that holds the VM´s operating system, as I described above, you have to select deploy to a host and not a cloud (of course, when the VM has been created it can be updated with a cloud)

Screen Shot 2014-01-20 at 12.24.29

Then when you come to the configure settings view in the wizard, the option to change the vhdx name appears,

Screen Shot 2014-01-20 at 12.32.54

Surely you find that having vhdx that has the same name as the VM instead of the generic library vhdx name of win2012-std.vhdx more suitable?

In the next post I will show you how to change the names of the disks on already deployed VM´s.


VMM Configuration Analyzer for 2012 R2

In the upgrading of a VMM 2012 Sp1 to R2 I wanted to test and run the Configuration Analyzer. When clicking on the link from the VMM R2 GA media you should be observant that it points you to the wrong place though, as you can see on the following screendump there is a link on the splash screen.

Screen Shot 2014-01-17 at 09.59.27

And when pressing that link you will arrive at the following site, which is wrong! So do not start downloading the stuff from this as these files are for the VMM 2012.

Screen Shot 2014-01-17 at 11.04.08

The right site is at the following link: and looks like this, do also notice that it is an analyzer for the whole System Center suite so you can do analyzing of all your different SysCtr servers.

Screen Shot 2014-01-17 at 11.05.18

You can also at this technet site read more about how it works and what prerequisites you have to install first.

SCVMM VM property dialog crash console with missing vhd(x)

Today I was at a customer and they had an interesting error in their virtualization environment with Hyper-V 2012 and SC VMM 2012 Sp1 (yes I know, it is not R2 but we are working on it). One of their Hyper-V hosts had a hardware memory failure which lead to the host crashing and the VM´s restarting on other hosts..

during this the VM´s that was on that host got an error in the VMM db, looking and handling the VM´s from Hyper-V manager or failover cluster manager was no problem. Every time we tried to refresh the VM´s showed the following error and the job did not succeed.

Screen Shot 2014-01-14 at 14.36.51

And when we tried to look at the properties on the VM from VMM the console just died, and that happened every time..

Screen Shot 2014-01-14 at 14.28.50

So how could we find the VM´s that was suffering from this, well PowerShell could be used and with the following we could get the amount of VM´s and also easily get a list of the VM´s names.

Screen Shot 2014-01-14 at 13.26.15

So how could we fix this then,

There is a cmdlet in VMM with a parameter that can be used,  Remove-SCVirtualMachine -Force , this will remove the VM but not the virtual hard disk as it cannot find it..

Screen Shot 2014-01-14 at 16.20.21

But because we want to keep the VM we will do a bit of a workaround

  1. Stop the vm in VMM  by Stop-SCVirtualMachine own01  (even if the vhd(x) is not seen by VMM it will shut down the actual VM)
  2. Remove the VM from the cluster in Failover cluster manager or with powershell (this will only remove the cluster instance but not the actual VM)
  3. Start the VM in Hyper-V manager or with PowerShell  Get-VM own01 -ComputerName HV01 | Start-VM
  4. Remove the VM from the VMM with Powershell using the -force  Get-SCVirtualMachine own01 | Remove-SCVirtualMachine -Force (as I have removed the VM from the cluster VMM cannot find it and delete the vm´s xml file etc)
  5. Add the running VM to the cluster again with hyper-V PowerShell and failover cluster powershell using Get-VM own01 -ComputerName HV01 | Add-VMToCluster (Get-Cluster HVCL30)
  6. refresh VM´s in VMM and see that now the own01 vm can open properties

The reason I start the VM after removing it from the failover cluster is that VMM should think it is in stopped state, because that makes it easier to remove! And as in Hyper-V 2012 I can add a running VM to a cluster I do not have to keep the VM shut down during the whole process but just to get it into the right state in VMM :-)

Not the easiest way but hey who had said that VMM was self-healing 😛 And yes we are in the process of upgrading to R2 and hopefully this error will not reemerge in that version….


Creating Hyper-V 12 R2 Cluster from Windows Server 12/VMM

I got a question about an error that occured when creating a Hyper-V 2012 R2 cluster from VMM 2012 R2 and the errorlog stated the following:

“Error (25325) The cluster creation failed because of the following error: An error occurred while performing the operation.. “

In the troubleshooting I found that the VMM 2012 R2 was running on a Windows Server 2012 Standard (which is fully supported). But as VMM uses the failover cluster cmdlets from the OS where installed it fails creating the R2 cluster as it is not supported to manage Windows 2012 R2 from a Windows 2012.

looking at the technet article regarding Server Manager it has a good table about support:

Screen Shot 2014-01-10 at 13.53.35


I have done some upgrades from VMM 2012 SP1 to 2012 R2 and have always in that process changed the operating system first to the latest version so this issue has not appeared for me before.

Testing to create a Hyper-V 2012 R2 cluster from a windows 2012 failover cluster manager gives the following error :

Screen Shot 2014-01-10 at 14.12.35

New version of Double-Take Move 7.0.1 with support for 2012 R2

I have had the the pleasure to work a bit with Vision Solutions and their product Double-Take Move that can be used when migrating between hypervisors or onto a public IaaS cloud like Azure. I have also made a test to migrate between generation 1 to 2 VM in Hyper-V R2. Last year I made a presentation on Nordic System Center Summit about migration alternatives and tools where I showed the System Center integration of Double-Take Move.

PowerPoint Presentation

Maybe you have seen the blog post from Migration Mark where he describes the extension of their MAT PowerShell toolkit so it now also support using Double-Take Move and as you can see if you have demands from end users and the company to keep the systems up during the migration then MAT4Move is the tool..

MAT4Move Summary
  • TYPE: Streaming disk conversion
  • PROS: More uptime than any other solution, migrate directly to Azure
  • CONS: Has a cost per VM, Requires an agent

Recently there has come an service pack update to this brilliant software that now also gives support for 2012 R2,  etc. One important update is that it now is possible to select synthetic NIC when migrating directly to a Hyper-V host, in the earlier version you only got a legacy and that is not what we want! Also the possibility to migrate to a VM replica residing on a SMB share. Here you can read more about some of the improvements:

  • Common improvements—The following improvements apply to both Double-Take Availability and Double-Take Move.
    • Windows 2102 R2 support—The following job types now support Windows 2012 R2.
      • Files and folders
      • Full server
      • Full server to Hyper-V
      • Full server to ESX
      • V to ESX
      • V to Hyper-V
      • Agentless Hyper-V
      • Agentless vSphere
      • SQL
      • GeoCluster
      • Data migration
      • Full server migration
      • Full server to Hyper-V migration
    • Adapter type on replica—This release allows you to select the type of adapter that will be used on a replica virtual machine for full server to ESX, full server to Hyper-V, full server to ESX migration, and full server to Hyper-V migration jobs.
  • Double-Take Move improvements—The following improvements apply to Double-Take Move migration jobs.
    • Alternate volume staging—With this release, you can stage the source’s system state data to an alternate volume on the target, if you do not have enough space on the target’s system state volume.
    • SMB share storage—This release allows you to store the replica virtual machine for a full server to Hyper-V migration job on a local volume or an SMB share.


Install LIS 3.5 on CentOS 6.3 and then upgrade to 6.5

Now that the Integration Services 3.5 has been released from Microsoft I wanted to try out to install them in a CentOS VM

Interestingly the support is for CentOS up to 6.3 and when reading the README file from CentOS in the dist that version is deprecated. According to the forums the CentOS version 6.4 and 6.5 has their own Integration services already in the distribution and that can be confirmed when I was testing out and trying to install 3.5 and still the modinfo said 3.1. The reason I was pursuing to install was that the nic in hyper-v said degraded..

Screen Shot 2014-01-03 at 15.32.01

So I tested some different cases ending up with the same result that the IS reported 3.1 and always the Network adapter as Degraded.

In the 6.3 version of CentOS there is no Integration Services by default so installing gives the following result

Screen Shot 2014-01-03 at 14.07.54

And when rebooting and checking the version I can see that I successfully installed the IC 3.5

Screen Shot 2014-01-03 at 14.15.36

The exiting part comes here where I now wanted to upgrade my CentOS 6.3 to 6.5 with “yum update” and as you can see on the next screendump I got version LIS 3.1

Screen Shot 2014-01-03 at 15.16.38

But my 3.5 rpm are still installed as you can see.

When checking the from the PowerShell side you can see that it first reports as version 3.5 and then when I have upgraded it says 3.1

Screen Shot 2014-01-03 at 15.52.33

One interesting bit in why I would like to do the LIS 3.5 upgrade on a CentOS 6.4/6.5 is that first after upgrade I get the integration services version from the host side as this is part of the new feature in 3.5, Key-Value Pair (KVP) Exchange that now works with Linux also. That is not part of the built in LIS 3.1 yet that CentOS/Redhat distributes.

Screen Shot 2014-01-03 at 16.02.20

Here you can read more about the new features in LIS 3.5.