MED-V v2: Differences between Shared and Separate Workspaces

When you package a workspace in MED-V, you will need to determine if this workspace will be deployed to a machine where multiple users will be logging on or a single user. If you will be dealing with multiple users, you have two options for deploying the workspace as outlined in the following article: http://technet.microsoft.com/en-us/library/gg548584.aspx…

0

TechNet Wiki: How to create a Workspace Package on MED-V 2.0

Here’s another article written by Microsoft Partner and MVP Leandro E. Carvalho that’s over in the TechNet Wiki. This one walks you through creating a new Workspace Package using Microsoft Enterprise Desktop Virtualization 2.0: Before users begin to use the old applications you need to create a package containing an image of Windows XP. MED-V…

1

MED-V: The Importance of Setting the UpdateServerProfileDirectory value in the SYSPREP.INF file

By default, the automatic copying of customizations from the Administrator profile to the default user profile will not occur with SYSPREP if using Windows XP SP2 (with Hotfix 887816) or Windows XP SP3. This is discussed in the following article: http://support.microsoft.com/kb/959753 To avoid the problems that may arise from this issue with MED-V, be sure…

0

Additional recommendations when using MED-V Workspaces configured for NAT Mode

In working with MED-V and supporting MED-V, I have found that there are three major areas that can be affected when using NAT mode instead of Bridged Mode with persistent mode MED-V workspaces. – Application Icons not displaying properly (or being cached properly) – Single-Sign-on (SSO) either does not work or has intermittent issues. -…

2

New Solution: A MED-V based Virtual Machine may periodically lose network connectivity

Microsoft Enterprise Desktop Virtualization (MED-V) Workspaces may periodically lose network connectivity due to one or more of the following reasons: 1.) Failure to retrieve an IP address via DHCP. 2.) DHCP Client loses current IP Address lease. 3.) Static IP address "disappears." This can occur if Symantec Endpoint Protection’s Network Threat Protection Module is running…

1

Behavior of Expired MED-V Workspaces Explained

If a user is attempting to start a MED-V Workspace and the user receives a message stating that there are no workspaces available, or they see list of workspaces and the one intended for the user is not available, this is usually because of one of the following reasons: · The workspace has not been…

1

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>”…

0