none
I need to move 3 VM servers including TFS to a new PC RRS feed

  • Question

  • Hello,

    Win 8/8.1

    I have to replace a PC (win 8) that has been running my 3 VM's for domain control, TFS and a build server.  I've studied the export and import process for Hyper-V.

    I want to ask if there are any hidden 'gotcha's' in making this move?  I want to keep everything named and operating exactly as it is right now.

    I had planned on exporting directly to the new PC's drive (win 8.1) that will hold the VM's.  I don't feel the need at this time to make copies for later, but will need to keep the same naming, etc.  Eventually these VM's will be moved to a dedicated server, so at that time will I follow the same steps?

    Any issues with the network connection, etc.?

    Thanks.

    Best Regards,

    Alan


    • Edited by Alan Wheeler Thursday, December 25, 2014 8:01 PM changed title
    Tuesday, December 23, 2014 8:43 PM

Answers

  • Hello,

    After moving the Hyper-V VM servers using export/import (using the Restore option) the servers came up just fine.

    However, there was a 'gotcha' with the TFS server.  The local copies of Visual Studio need to have the cache folders cleared to get rid of the old TFS server location.  I picked this up from several other posts.  This one was pretty good.

    The location to clear is: "user > {the user} > appData > Local > Microsoft > Team Foundation > 5.0 > cache".  Some of my machines had multiple version folders, such as 4.0.  I cleared both caches.

    I had another problem with the VM migration I'll put in another post.  The WMIService is not including the VM's in the list when queried.  See this post on the scripting forum.

    Best Regards,

    Alan


    • Edited by Alan Wheeler Thursday, December 25, 2014 8:22 PM added reference for follow on problem
    • Marked as answer by Alan Wheeler Monday, December 29, 2014 4:25 PM
    Thursday, December 25, 2014 8:00 PM