Hyper-V – Migrate from One Failover Cluster to Another

Hyper-V has been a great addition to our environment but the process of getting a task done is not as straight forward as some would hope. I had trouble with migrating servers from our old Hyper-V cluster to our new one, so I decided I would help others out with a simple guide.*

*Nothing is ever as easy as it seems.

Hopefully you have gotten as far as creating a Hyper-V cluster or server. If not, no worries, I will have a guide up for that too.

I am starting out in the Failover Cluster Manager and I have my two clusters expanded.

clustersOnce we are in the correct area, we need to choose which Virtual Machine we want to move and remove the Role from the cluster. To accomplish this, right-click the role that you want and select Remove.

Hyper-V removeOnce you select Remove a pop-up window asking if you are sure you want to continue. Select Yes.

3This will take a couple of seconds to remove that role. While waiting on that you can open up Hyper-V Manager and navigate to the correct server. Before we try to move any servers, you have to make sure the same settings (i.e. Virtual Switch Manager…) has the same switches created to save any problems in the future.

4Once you are in the Hyper-V Manager we can now try to move the server from one cluster to another. First you need to go into Active Directory and configure the two Hyper-V machines the ability to talk to one another. That is detailed in this post here: Active Directory Settings

If you have not set up your machines to accept migrations you will run into this error:

HVMoveErrorEven after making the changes in Active Directory a couple of reboots and a little bit of time fixed this error if it does not work right away.

Another problem that I ran into was I had Snapshots or Checkpoints with the server that had old virtual switches that did not belong anymore. Either you need to delete those or create the virtual switches on the new servers so the virtual machine will transfer. Here is an example of them:

14Once you get that far you may run into this error next.

15This is telling you that the hardware is not compatible, luckily there is somewhat of a simple fix. First shutdown the virtual machine. Once that is powered off, right-click the virtual machine and go to Settings…

VMsettingsFrom there expand the Processor and select Compatibility. Within Compatibility check the box Migrate to a physical computer with a different processor version.

17Once this setting has been made, we can finally move the virtual server to the new physical host. Right-click the virtual machine and select Move…

5It is pretty simple, I used the defaults and selected a specific location that would move the whole virtual machine and it’s files to the same location.






11Make sure that all of the settings are correct and select Finish. This should be it and you can watch it move and set up a perpetual ping to the running virtual machine and only see a single packet drop. Pretty neat!


19That should be it! I may update this post to also include some Powershell commands that will accomplish the same thing but can even be scripted!

Hyper-V: Active Directory Authentication for Moving

Moving virtual machines between two separate Hyper-V environments is a little tough. One major problem that occurs is an authentication error that the two environments are not able to authenticate for the transfer. These are the steps to make it work.

This is a Windows 2012 R2 environment. First you will need to navigate through Active Directory to the correct server you want to transfer to. Right-click and go to Properties.

hypermove1Once in Properties go to Delegation.

hypermove2In Delegation select the third radio button: Trust this computer for delegation to specified services only. Leave Use Kerberos only selected. Next go to Add…

hypermove4Once in Add… a new window will pop up. Go to Users or Computers…

hypermove5Input the computer or server that you want to have the capabilities to transfer from. Say you have Server1 and want to transfer to Server2. Right now we would be in Server1 changing the properties and want to transfer from Server2. Server2 is the server we would like to input. Once we enter the server in, all the services  we can select from will populate.

hypermove6There are two that we need. The first one you can see on this screen: cifs the other one that is required is Microsoft Virtual System Migration Service. Select both of those and hit OK.

hypermove7When the settings are applied the process has to be done again for the other server. Each server should have the same settings pointing to the other server that you want to move between. Once each server has been set accordingly, there are settings to double check inside of Hyper-V Manager.

On the right hand side of Hyper-V Manager should have all the actions listed. We need to go into the Hyper-V Settings…

hypermove8Once inside there on the left hand side go to Live Migrations and ensure that it is enabled. There are default settings listed that can remain the same unless you want to edit those.

hypermove9Next to Live Migrations there is a plus sign to drop down the Advanced Features. There are a couple of settings to change. They moved some things around in 2012 R2 that made this a little confusing. I’ll post the 2012 R2 first and the regular 2012 configuration. You will notice with 2012 there is no Advanced Features.

hypermove10Here is the Windows 2012 configuration.


Once these settings are complete you can hit OK to apply the settings and attempt the move from one server to another. This is just the beginning of moving machines and setting the correct settings, in the more advanced posts we will go over some errors that occur and how to overcome them.


First Post

I have thought a lot about my first post on this site and I have come to the conclusion that an introduction is the way to start it off. The About Me section has a small amount of information on it but I would like to elaborate. I am in to almost all aspects of computers. I do not intend for this to be solely system admin related because I hope like many, I am into just about every aspect of computers. I would love to post interesting things that I worked on and did from a RaspberryPi to an actual Windows/Linux server. I have ambitions in security, which I have attended the last three years at Defcon (19, 20, 21) and I do not plan to miss anymore. I have an Arduino that I have not accomplished anything with along with two RaspberryPi’s. I come from a long history of trying to see how things work and are put together; my first degree was going to be in electrical engineering but I changed to network administration. What I am getting to is that the possibilities are endless right now in this age and I figured a blog documenting my journeys was the way to go.

Recently I was promoted from a help desk employee to the system administrator and it has been the challenge of a lifetime. I have had to forget everything I thought about and learned on the help desk to have the capacity to relearn how an administrator does work. I am not here to call anyone dumb, more or less that is what I am I figure. Nothing seems to go right even if it is simply laid out on TechNet to just ‘type these two commands’. I thought copying files was just as easy as well click and drag. I have learned about robocopy, which I will elaborate on eventually. I guess that is a little back story that was not needed. I felt that just diving right in with technical documentation was not the road I wanted to take.

Off we go!