In this blog post I’d like to explain how to create Hyper-V virtual machine on Windows 10 to be compatible with Windows Server 2012 R2!
In the last couple of months my users are using Windows 10 on the local machines, (desktops and laptops) and sometime they need to move virtual machines created on the Windows 10 to Hyper-V hosts which have been using Windows Server 2012 R2 as OS.
When you create virtual machine on Windows 10, Configuration Version is 7.0 and you cannot change that or during virtual machine creation choose configuration version.
From the other side, virtual machine configuration version on Windows Server 2012 R2 is 5.0 and we cannot import virtual machine created on Windows 10 to Windows Server 2012 R2 because of differences on configuration version.
So, what we can do in that case?
The first; if we have virtual machine with configuration version 7.0, we can copy .VHDX on Hyper-V host with WS2012 R2, create new virtual machine and add copied virtual disk. But, we lost virtual machine configuration and checkpoints.
The second; we can create virtual machine on Windows 10 through PowerShell, where can choose virtual machine configuration version.
Here is an example, and full script you can download .ps1.
Last week Altaro published a great new eBook which contains information on how administrators can improve the performance of their Hyper-V infrastructure.
What you can learn in this eBook:
– Diagnosing and remediating Storage, CPU, Memory, and Network performance issues
– Using Windows Performance Monitor and PAL to facilitate system and VM monitoring
– Manage planning of Hosts, VMs, Storage, Networking, to minimize the risk of performance issues
You can download for free from here.
Few days ago I had a opportunity to upgrade/migrate production TFS 2013 Update 3 to TFS 2015 Update 1. The migration process is “straightforward” but as usual every time something goes wrong. Unfortunately, this time I didn’t have exception .
As I mentioned above, we had TFS 2013.3 but it wasn’t a clean installation, that was an in-place upgrade from TFS 2008 –-> 2010 –> 2013 in the last couple of years. This time I decided to do upgrade to the new hardware.
Here I’ll not explain how to migrate, I want to explain what type of error I had and how solve problem.
During the upgrade process I got error and warning…
[2016-02-15 20:13:22Z][Error] End of Central Directory record could not be found.
[2016-02-15 20:13:19Z][Warning] Invalid zip file in process template MSF Agile For Project Server 2007, End of Central Directory record could not be found.
[2016-02-15 20:13:20Z][Warning] Invalid zip file in process template MSF CMMI For Project Server 2007, End of Central Directory record could not be found.
When you try to find resolution on the Internet you will find NOTHING! But luckily error is obvious. We need to delete problematic Process Templates. Open Process Template Manager from the Visual Studio, find the problematic templates and delete them.
When you are done, have to repeat whole procedure. Backup databases, restore, upgrade… and at the end you will have successful TFS upgrade
Thank you Ognjen for your precious help