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

Solution: Embedded External URL references do not stay in the Active Browser when using MED-V Web Redirection

When using MED-V version 1, you have the option of controlling which web URLs will open in the host browser and which URLs will open in the guest browser. This only works with Internet Explorer because the mechanism MED-V uses to facilitate this is a simple BHO (Browser Helper Object) to intercept and redirect as…


MED-V V2 Beta availability in Q4 2010!

Microsoft Enterprise Desktop Virtualization (MED-V) removes the barriers to Windows 7 upgrades by resolving application incompatibility issues from legacy LOB applications and Internet Explorer 6/7 web apps. MED-V v2 Beta will enable customers to pre-configure MED-V workspaces that can be delivered to user desktops via System Center Configuration Manager or any electronic software distribution (ESD)…


A Closer Look at the MED-V Image and Data Repositories

One request I have seen often from my customers lately has been a request for an in-depth discussion on how MED-V handles images and metadata. If you have been working with MED-V, by now you are probably familiar with the basics of how MED-V handles images. MED-V version 1.0 SP1 works with Virtual PC images…

2

A look at multi-user scenarios in MED-V

In many Enterprise environments, there are multiple users logging onto a single workstation. What happens when multiple users use a workstation that has a MED-V Workspace? When managed properly, each user will be able to use the MED-V workspace and their assigned applications. There are two multi-user scenarios to consider for domain-joined workspaces: Scenario 1:…


Troubleshooting Event ID 52 Errors in MED-V 1.0

Has this ever happened to you? You prepare a Virtual PC image for use with MED-V and you get the following error: “Failed to start Workspace <workspacename>”. Event ID 52 This is immediately followed a list of five possible causes. I would like to go over these causes as well as the 6th potential cause….

2

Information on the message: “The MED-V workspace must be closed before Windows can be shutdown. Click Cancel and close the MED-V Workspace.”

When you run the MED-V Client on the Windows Vista or Windows 7 operating system, you may get a warning message when you attempt to log out of Windows while a MED-V workspace is still running: (Waiting for) MED-V The MED-V workspace must be closed before Windows can be shutdown. Click Cancel and close the…

4

MED-V printing options, plus some common printing related issues and resolutions

Printing in MED-V is pretty straight forward. You have two options for printing from MED-V workspaces: Printing from within the guest operating system and redirecting guest operating system printer output to the host printer subsystem (local printer redirection.) Local Printer Redirection This is where the MED-V published application uses the MED-V Local Printer object. This…

3