MED-V Host Agent Setup fails with “MED-V Host Agent requires Windows Virtual PC 7 version 6.1.7600 or higher”

Hi everyone, Mark Stanfill here and today I wanted to take a minute to quickly tell you about an issue I recently ran into where the MED-V Host Agent Setup (MED-V 2.0 Host Agent) fails with the following error message: MED-V Host Agent Setup MED-V Host Agent requires Windows Virtual PC 7 version 6.1.7600 or…

0

An important note regarding the deployment of MED-V 2.0 when Windows 7 SP1 is already installed

When installing the MED-V 2.0 Host Agent, you must first deploy the Virtual PC components. If you have not installed Windows 7 Service pack 1, the requirements are straight forward: http://technet.microsoft.com/en-us/library/gg548583.aspx The Virtual PC Engine can be downloaded and installed here: http://go.microsoft.com/fwlink/?LinkId=195918 However, please note, the VPC packages have changed to allow for the KB958559…

0

"Last Restart" component in the MED-V virtual machine setup script is not needed and will increase workspace first time setup time

When configuring Script Actions for the Virtual Machine first-time setup in the MED-V management console, it is important not to add in an additional “Restart Windows” action at the end as it is not necessary. The first-time setup will always reboot the guest at the end of the last script action. For example, if a…

0

How to configure an Image Repository using IIS

The following post describes how to configure an image repository using IIS. An image repository is an optional server that is used for image distribution (where administrators upload new images and client computers check the server every 15 minutes and update their image if a new one is available). An image distribution server requires the…

1

Uninstallation of MED-V component does not remove all configuration files

After uninstalling and reinstalling Microsoft Enterprise Desktop Virtualization, you may notice one of more of the following symptoms: Errors relating to previous corruption in configuration remain. Old Policies remain. Errors reading the XML configuration such as: Service cannot be started. System.Exception: Failed reading the file C:\Program Files\Microsoft Enterprise Desktop Virtualization\Servers\ConfigurationServer\ClientSettings.xml. Please make sure it exists…

1