Moving Virtual Machine and Storage To Windows Server 2016 and Update VM Version

This tool will live migrate selected virtual machines including their Storage to Windows Server 2016 Hyper-V and Update VM Configuration Version automatically.

5 Star
805 times
Add to favorites
E-mail Twitter Digg Facebook
  • Host not on domain
    2 Posts | Last post March 05, 2020
    • Hi.
      May I use it on a host that is not a domain member?
    • Yes, you can do that.
      Thank You!
  • Thank You!
    1 Posts | Last post May 15, 2017
    • This utility works great!!!! Thank you!
  • i am facing issue with this tool.
    4 Posts | Last post May 15, 2017
    • Hi, i am testing this tool now but i am not seeing any activity to be performed by this tool. it discovers the workload of source Hyper-V server, then i select the VM and give the storage path of the destination server. then the result bar goes to end and nothing happens. 
    • Thanks Muhammad for your feedback,
      Could you please confirm that you are running the tool as Administrator?
    • Thanks for your reply Charbel,
      Yes I tried the tool with running it as Administrator and without. both cases the result is same. 
    • I was having the same problem...please follow this about setting up delegation fixed my problem...
  • Compatibility with 2008 R2 Hyper-V cluster
    2 Posts | Last post May 10, 2017
    • Can i use this tool in order to migrate VM's from a Win 2008R2 Hyper-V cluster to Win2016 Hyper-V cluster?
    • sorry, I didn;t read that is no verified with 2008R2
  • Individual VM migration
    2 Posts | Last post January 11, 2017
    • Could this tool be used to migrate one at a time individual VM's? If so, how can it be done?
    • Ah! never mind. I see how to do it. Thanks
  • i am facing issue with this tool.
    1 Posts | Last post December 29, 2016
    • Addition to below query. I am doing this testing between two separate clusters (Win2012R2 and Win2016) which are part of same domain. Thanks.
  • VM's with Share Storage?
    2 Posts | Last post December 20, 2016
    • Will this work if the VM's are located in a cluster shared volume, shared by both 2012 R2 Hypervisor and 2016 Hypervisor?
    • Yes it should work, but I did not test this scenario.
      Please share your feedback here when you run it.