MED-V Solution: Error When Starting Workspace: "Reply Message Didn’t Arrive on Time"

When you attempt to start a deployed workspace from a MED-V client or test a MED-V workspace using a test image, you may get the following error: “Failed to start Workspace ‘<workspaceName>” Details show: “Unexpected error when trying to verify Workspace prerequisites. Internal error: Reply message didn’t arrive on time. original message ID: <messageID GUID>”…


MED-V Solution: Error in VM Prerequisite Wizard: "An unsupported version of Virtual Machine Additions is installed"

When preparing a Virtual Machine for deployment for use with MED-V, you will need to ensure that in addition to the MED-V workspace installation being installed inside the virtual machine, you will need to have the minimum level of Virtual Machine additions for Virtual PC installed as well. Upon completion of the workspace installation, it…


Dates that you enter in the Reporting column of a report can only be entered in the English (United States) date format in the Enterprise Desktop Virtualization tool

When you try to run a report in the Microsoft Enterprise Desktop Virtualization tool, the dates that you enter in the Reporting column of a report can be entered in the English (United States) date format only. For example, you cannot enter the date in the dd.MM.yyyy format. We have a workaround in the form…


Resolution: The MED-V Server service fails to start with Error 1053

When you attempt to start the MED-V Server service on Windows Server 2008 or Windows Server 2008 R2, you may get the following error: Error 1053: The service did not respond to the start or control request in a timely fashion. Additionally, the system event log indicates this timeout failure by a log entry that…

2

Solution: The Virtual PC engine may crash when attempt to start MED-V a workspace

When you attempt to start MED-V a workspace using a test image or a deployed image, the Virtual PC engine may crash and generate a Fault Report using Windows Error Reporting. Subsequently, the MED-V Workspace will fail to start. The Virtual PC engine crash will show the following fault: {virtual pc.exe, 6.0.210.0, unknown, 0.0.0.0, ffff08ef}…

1

Troubleshooting Reporting and SQL Issues with MED-V 1.0

While reporting is technically an optional feature of MED-V version 1.0, it is valuable in tracking errors, client events, and workspace usage statistics. You may encounter issues at various stages of setting up and using the reporting feature. I have composed a list of issues you may encounter when setting up reporting to SQL. Create…


MED-V tips for your Helpdesk Admins

I recently had a great question from one of our customers on how to best allow helpdesk personnel to troubleshoot issues with MED-V applications.  No, this wasn’t necessarily what we refer to as a break/fix type issue with MED-V itself, but rather how to allow remote helpdesk admins to access the Full Desktop in the…


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

MED-V: Tips on modifying the ClientSettings.XML file

With Microsoft Enterprise Desktop Virtualization (MED-V) , there may be situations where the ClientSettings.XML file may need to be modified directly to adjust features and timeout values that are not available through the standard interface for modifying workspace policies. These values, including configuration overrides and timeouts, can be adjusted by editing the ClientSettings.XML file under…