King Computer Solutions

Archive for the HyperV Category


How to check Microsoft HyperV integration components are running the latest version to stop storvsp event id 6 warnings

In the system EventLog you may see storvsp messages like this: A storage device in ‘TS2’ loaded but has a different version from the server. Server version 5.1 Client version 4.2 (Virtual machine ID C99F4CCB-89A4-4F3D-8FA5-ECB5DDD10B7F). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until […]


HyperV machine missing network card after restoring VHD on Windows 2012 server

Problem You have restored a VHD or moved it to a new HyperV 2012 Server from a 2008 server. When you restore and recreate the HyperV machine and start it up, it has no network connectivity. Running ipconfig shows media disconnected with no network card. Device manager shows no network device and Other devices showing […]


Backup virtual machine in hyperv using windows backup

To backup a virtual server using windows backup you first need to add the hyperv writer. To do this you can either edit the registry as below or download the microsoft fix it tool from-


Drive performance through HyperV virtual disk driver vs direct to physical disk

I was interested if there was any speed loss in running a virtual machine hard disk vs the direct physical disk on the host server. I suspected there should be an overhead from running through the virtual driver. The Hyper V virtual drives show up in device manager as Virtual HD ATA device on an […]


Converting Elastix Asterisk Linux to HyperV virtual machine

This tutorial will enable you to create or migrate an elastix asterisk voip server on a HyperV virtual machine. This uses the latest stable version of elastix (1.6 at time of writing), but I expect the v2 beta should work with the same methods. Download the Elastix 1.6 ISO from Create a new virtual […]


Convert Windows 2003 vmware vmdk to hyperv vhd and avoid bluescreen

The main problem you’ll have doing this is that HyperV does not recognise SCSI as a valid boot device, so if you’re VMWare machine is running using the default SCSI drive and you do the conversion from VMDK –