{"id":496,"date":"2016-12-15T07:59:06","date_gmt":"2016-12-15T12:59:06","guid":{"rendered":"http:\/\/www.amixa.com\/blog\/?p=496"},"modified":"2016-12-15T07:59:06","modified_gmt":"2016-12-15T12:59:06","slug":"quick-migration-of-windows-server-2008-r2-hyper-v-to-windows-server-2012-or-2016","status":"publish","type":"post","link":"https:\/\/www.amixa.com\/blog\/2016\/12\/15\/quick-migration-of-windows-server-2008-r2-hyper-v-to-windows-server-2012-or-2016\/","title":{"rendered":"Quick Migration of Windows Server 2008 R2 Hyper-V to Windows Server 2012 or 2016"},"content":{"rendered":"

Here are the proven and tested steps for migrating from Windows Server 2008 R2 to Windows Server 2012 or 2016.\u00a0 Note:\u00a0 You cannot IMPORT a VM from 2008 R2 into 2012 or 2016, so you have to do the whole process manually.\u00a0 That’s the reason for this post.<\/p>\n

    \n
  1. log into the existing 2008 R2 virtual machine and note the following\n
      \n
    1. memory and CPU config<\/li>\n
    2. IP addressing information (you need all the IP information, static IP’s etc.)<\/li>\n<\/ol>\n<\/li>\n
    3. Shut down the 2008 R2 virtual machine<\/li>\n
    4. copy the VHD from the 2008 R2 virtual machine to the new host.<\/li>\n
    5. On the new host open Hyper-V manager\n
        \n
      1. Edit disk<\/li>\n
      2. select the VHD<\/li>\n
      3. CONVERT to VHDX<\/li>\n
      4. this will take a while<\/li>\n<\/ol>\n<\/li>\n
      5. When that completes, create a new VM\n
          \n
        1. DO NOT attach the hard drive.\u00a0 Select “add a HD later”.\u00a0 (I have seen issues with attaching the hard drive as part of the setup here, so I skip it and do it separate)<\/li>\n
        2. Generation 1 VM<\/li>\n
        3. set the memory and CPU configs<\/li>\n
        4. complete the VM creation<\/li>\n
        5. edit the VM and attach the VHDX file as IDE 0 master<\/li>\n<\/ol>\n<\/li>\n
        6. Using the Hyper-V remote control interface (by double clicking on a VM)<\/li>\n
        7. Start the new VM<\/li>\n
        8. boot into windows<\/li>\n
        9. while on the desktop, after ~15-60 seconds you might see a “REBOOT” notification after changes are made to the OS.\u00a0 If you get this notification, go ahead and reboot.\u00a0 Otherwise, continue on.<\/li>\n
        10. at this point in the Hyper-V manager, you need to double click on the VM and remotely control it through the Hyper-V manager<\/li>\n
        11. while you are logged into the VM as administrator and at the desktop, insert the Hyper-V integration tools disc and upgrade the Hyper-V tools<\/li>\n
        12. reboot when that completes<\/li>\n
        13. log in again to the machine through the Hyper-V remote control interface<\/li>\n
        14. edit the network adapter properties and set it exactly as it was before.\n
            \n
          1. Note:\u00a0 During this whole process your OLD NIC will be hidden (because it’s gone now) and you will be given a new NIC and it will be in DHCP mode from the start.<\/li>\n
          2. you will need to edit that new NIC and put in the correct static TCP\/IP information if applicable to your setup.<\/li>\n
          3. ALL OTHER settings (machine name, IIS, DNS, etc.) will retain fine.\u00a0 Just edit the NIC and config the NIC the same way it was on the old VM<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

             <\/p>\n

            All done!<\/p>\n","protected":false},"excerpt":{"rendered":"

            Here are the proven and tested steps for migrating from Windows Server 2008 R2 to Windows Server 2012 or 2016.\u00a0 Note:\u00a0 You cannot IMPORT a VM from 2008 R2 into 2012 or 2016, so you have to do the whole process manually.\u00a0 That’s the reason for this post. log into the existing 2008 R2 virtual machine and note the following<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1,22],"tags":[95,8],"class_list":["post-496","post","type-post","status-publish","format-standard","hentry","category-random-bits","category-windows-server","tag-hyper-v","tag-microsoft-windows-server"],"_links":{"self":[{"href":"https:\/\/www.amixa.com\/blog\/wp-json\/wp\/v2\/posts\/496","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.amixa.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.amixa.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.amixa.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.amixa.com\/blog\/wp-json\/wp\/v2\/comments?post=496"}],"version-history":[{"count":1,"href":"https:\/\/www.amixa.com\/blog\/wp-json\/wp\/v2\/posts\/496\/revisions"}],"predecessor-version":[{"id":497,"href":"https:\/\/www.amixa.com\/blog\/wp-json\/wp\/v2\/posts\/496\/revisions\/497"}],"wp:attachment":[{"href":"https:\/\/www.amixa.com\/blog\/wp-json\/wp\/v2\/media?parent=496"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.amixa.com\/blog\/wp-json\/wp\/v2\/categories?post=496"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.amixa.com\/blog\/wp-json\/wp\/v2\/tags?post=496"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}