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.

Awarded MVP 2014 for the first time

As everyone else with some ITPro community engagement there is a date of the first day every quarter that makes the heart go a bit faster and the hopes for becoming one of the few privileged that get the Most Valuable Professional Award from Microsoft.

Today I got the award for my contributions in the Virtual Machine community 🙂


I have been during quite some time trying to give the community my sharings in virtualization and automation and helping out so that others can benefit and not having to reinvent the wheel again.

Thank you all that have been following me on this blog, twitter and at other social networks and I hope that you benefit somewhat from my scavenges in the wonderful world of IT!

I am looking forward to this year when I will together with my fellow MVP´s explore and work together to help out in the deployment of Cloud OS.


New version of Convert-WindowsImage.ps1 that support Gen2

So I noticed that the awesome Convert-WindowsImage.ps1 PowerShell script has been updated to version 6.3 and published during the Christmas holidays. The script is maintained by Microsoft Consulting Services and was originally created by Mike Kolitz.

I really like this script and have used it alot when creating new VM´s and I have been awaiting an update to support the Generation 2 VM´s with UEFI boot.

Here you can see that I have added the parameter -VHDPartitionStyle GPT to use for the generation 2 VM

Screen Shot 2013-12-30 at 21.59.28

You can find the script here.


New Disk2VHD(x) from SysInternals that can make VHDx

So I saw today that Mark Russinovich have released a new version of the Disk2VHD binary from SysInternals

One really nice new feature is that you can with this updated tool now create VHDX directly without needing to convert a VHD and that does not require a Windows 2012 or Windows 8 or later to be able to work. This tool can be used when doing P2V also.

As you can see on my screendump I have tested it on a Windows 7 and the checkbox with VHDX.

Screen Shot 2013-12-20 at 13.53.09

You can find it here on SysInternals page

Make running VM highly available in VMM 2012 R2

So I was helping a customer to migrate a VMware VM to their Hyper-V environment that is managed with System Center VMM, As I described in an earlier post I had some things that I did not like in the built-in v2v conversion that is part of the VMM.

In this migration I used Double-Take Move and this is a really nice software from Vision Solutions that allows you to migrate a running VM and will only get a few minutes downtime during the failover :-). The great thing is that the VM is replicated to the hyper-v host directly and you get a synthetic NIC and also a VHDx virtual disk.

There are though some small things that need to be considered and Double-Take does not do the whole part when used separately, when using it with Vision Solutions system center integration toolkit we can automate these things too, but for migrating just a few VM´s that is a bit of overkill. So what do we need to take care of,

  • DT does not set VLAN on the nic for the migrated VM, that can be done during the replication in VMM when the newly provisioned VM appears there and set the right vm network and bandwidth etc.
  • DT does not make the VM highly available during the migration, it can be deployed on the Clusterstorage volume though.
  • DT does not remove VMware tools during the migration so that has to be cleaned up after.
  • DT does not update/install the Hyper-V integration components.

So now to the main focus for this article, when the VM has been migrated to Hyper-V, how do I configure it to be highly available? When looking in the properties of the VM on VMM that option is greyed out

Screen Shot 2013-12-20 at 12.56.41

And trying to add it through the PowerShell cmdlets in VMM gives the following error message:

Screen Shot 2013-12-20 at 14.50.46

So the way to do it is with the Hyper-V and failover cluster cmdlets instead:

Screen Shot 2013-12-20 at 14.58.34

And then when refreshing the VM in VMM you can see that it is now highly available 🙂

Screen Shot 2013-12-20 at 14.21.48

The workaround option that is available in VMM to be able to make the VM highly available is to do a Live Storage migration to another CSV Volume/SMB share and in the wizard check the box for making it highly available but that involves file copying and goes painfully slower than the Add-VMToCluster on the running VM that already resides on a shared storage volume.

Screen Shot 2013-12-20 at 15.36.05

And this also (at least in my test environment) creates a copy cluster resource that has to be cleaned up manually cause the real one is running..

Screen Shot 2013-12-20 at 15.53.40

Passed exam 74-409 today!

Today I was in the mood to take a Microsoft exam and as MSFT so generously gives a cert voucher for free it was not so much to argue about 🙂

I already have the MCSE : Private Cloud

But now it was time for Microsoft Certified Specialist: Server Virtualization with Hyper-V and System Center (exam nr 74-409) and this exam reflects and measures the latest releases from Microsoft in Windows Server 2012 R2 Hyper-V and System Center 2012 R2.

The skills being measured can be found here.

I have some knowledge in the subject and have done some implementations before and also had the previous title MCITP: Virtualization Administrator so I thought it should not be too hard, as always some questions have to be read more than once before choosing the right answer.

I used Marius collection of study tips and also the Microsoft Virtual Academy that with registration gives you the free voucher

Good luck in your free tryout 🙂



Nordic System Center Summit – Migrate to Hyper-V


The last two days I was on the road and presented my session on migrate to Hyper-V and that on the Nordic System Center Summit that was hosted by my company Lumagate. We visited both Stockholm and Oslo.

Both Travis Wright and Chris Ross from Cireson was with us and had some really interesting sessions!

In my presentation I described the different ways to migrate and how to prepare for a large migration and that in different ways of automation.

Here is the presentation:


And if you have a PC/MAC you can view the presentation directly here with PowerPoint Webapp

Password dump from a Hyper-V Virtual Machine´s memory

So earlier this week the twitter flow went bananas when Remko did a blog about how to extract the password in clear text from a VMware vmem file with the add-on from Benjamin, Mimikatz that extends the windebug.

I wanted to test if it works also in Hyper-V and it is not so much difference, the main difference is how to create the dump file and here I use the vm2dmp (thanks to Yusuf for supplying me with a vm2dmp.exe that works with 2012!!) with the right switches, in this case the VM is in saved state but you can also use snapshots or just the vsv and bin file.

Screen Shot 2013-11-29 at 16.33.16

And then when importing the dump into the windbg I can with the commands get the password for the user that was logged in on the Win 7 VM

Screen Shot 2013-11-29 at 15.26.19

I have tested this on a Windows 7 virtual machine and also on a Windows Server 2012 R2 virtual machine both running on Hyper-V 2012. This highlights the importance once more that it is crucial to make sure that only the right people have access to the virtualization hosts and the storage where the VM´s resides!

Experience on the V2V function in SC VMM 2012 R2

Last week I was at a customer and worked on setting up an new Hyper-V and SC VMM 2012 R2 environment and also connecting the VMM to their existing VMware. We configured the hosts with Bare-metal deploy and also configured logical switches in VMM. The setup and configuration with both VMM and Hyper-V was very smooth and it seems that they have worked a bit on the R2 release on that part 🙂

When the environment was up and running we also connected it to the customers vSphere 5.0 environment.

In-the-box of the VMM 2012 R2 there is only V2V when moving machines from vSphere to Hyper-V, the P2V function has been removed and is only available in VMM 2012 SP1 and earlier, a microsoft blog has described a way to use a workaround with a VMM 2012 SP1 but that does require a Hyper-V 2012 host and you have to run two VMM servers during the conversion process.

We have tested several VM´s and noticed some disturbing issues in the V2V process.

for a reason unknown the target does not get the source number of vCPU´s and memory setting so a VM that had 4 GB RAM in vSphere would get a static setting of 512 MB RAM, and if it had 2 vCPU in vSphere it got 1 vCPU in Hyper-V.


Screen Shot 2013-11-26 at 08.01.31

the next part was that the conversion created VHD´s on the new Hyper-V 2012 R2 and not VHDX for the converted virtual disks… At least it is fixed sized disks so we do not have to worry about partition alignment issues that is the case with the dynamic VHD´s.

And when we tried to migrate a VM with three virtual disks, the v2v process connected all of the to the IDE controllers and not as best practice, the data disks to SCSI… I changed it manually and successfully booted the VM.

Screen Shot 2013-11-22 at 11.29.59

 at last we found another bug or something regarding the networking and the migrated VM..

Screen Shot 2013-11-25 at 16.26.06

And when the VM was migrated it looked like it was connected to the right network in VMM as you can see on the following screendump from the VM network properties in VMM.

Screen Shot 2013-11-22 at 11.39.22

but when the VM booted it did not connect to the correct network and I had to go into the Hyper-V manager and look at the VM configuration and there it showed as no VLAN, once I corrected the issue and checked the vlan id and correct vlan number the VM was on the right network.

Screen Shot 2013-11-22 at 11.38.51

The Microsoft Virtual Machine Converter (MVMC) that could be used with the MAT has not yet come in a new version that supports vSphere 5.1/5.5 and equally important, the Hyper-V 2012 R2 hosts.. With the MAT you can customise it to set and configure both network inside of the VM´s and also configure correct vlan settings in the VM´s network card based on what the vSphere is configured with.

Maybe I have just been unlucky but all of these issues with the VMM V2V makes it a less desired solution when migrating from VMware in a larger scale.