Lairds Computer Services

Sysprep:
If you sysprep a machine after you have installed the Hyper-V role, sysprep removes the command to start it from the boot store.

To restore it, open a command prompt and type:

bcdedit /set hypervisorlaunchtype auto

And then reboot.


Machine List:
Hyper-V stores its installed virtual machines as shortcuts to the configuration files in the following folder:

%systemdrive%\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines

This folder contains shortcuts to <GUID>.xml files.  You can disconnect a machine by removing the shortcut from this folder.

Search for *.xml in the folder where the VMs are.  It is usually in the Virtual Machines subfolder.

Sometimes Hyper-V will complain about the permissions on the VHD as being wrong.  To fix this, examine the permissions on another VHD and modify the GUID below to match the GUID on the server (it is unique from machine to machine) and changing test.vhd to be the name of the vhd file:

icacls test.vhd /grant "NT VIRTUAL MACHINE\F70995EB-8B7D-98FC-1EBD-3638CD1AEC32":(R,W)

You will also need to restart the Virtual Machine Monitor service to pick up the changed permissions.


Moving a VHD back out of Hyper-V to Virtual PC:
In order to do this you will have to set the machine to redetect the HAL.  For Vista and later this can be done from either the command line or GUI.

Command Line:
bcdedit /enum /v
Copy the identifier for the Windows boot loader
bcdedit /set {identifier} detecthal yes

or

GUI:
msconfig->Boot Options->Advanced
Check 'Detect HAL'