Posts Tagged ‘xpmode’

Are you still Using MED-V? If so, do NOT install this update

If you are currently still running MED-V 2.0, be very aware of a known issue. If you install the RDP/RDC 8.1 update for Windows 7 SP1, you may notice after installing the update, you are seeing application crashes of the MED-V Workspace. This update is labeled KB2830477. It was originally released last year and there were sporadic reports of problems with MED-V hosts running it. It has recently been re-released (February 11, 2014) and I have noticed many more reports of this occurring. This issue has been reported for both XP Mode and MED-V in the Technet forums as well.

Right now, there is an investigation ongoing. I would advise in the meantime that you do not install this update on MED-V hosts. If you have already installed this update on MED-V hosts and are experiencing the problem, you can simply uninstall the update and the issues should disappear.

Please note that this is an optional update. This update is not needed for MED-V or Windows 7 functionality. It is not a security update either. It may provide enhanced features if you need to connect your Windows 7 host to Windows Server 2012 or Windows Server 2012 R2-based RDP Sessions or RemoteApps.

Here is the subsequent KB article on the update:

KB2830477: “Update for RemoteApp and Desktop Connections feature is available for Windows”

Categories: MED-V, RDS, VPC Tags: , , , , , ,

How MED-V Affects Windows XP End-of-Life Support Policy (It Doesn’t.)

Lately, I have many customers who are in the process or quickly planning their migration from Windows XP to Windows 7. Some of them are even looking to become early adopters of Windows 8. In the process of inventorying, rationalizing, and providing application compatibility remediation for their legacy applications, the need for leveraging MED-V for last-resort application compatibility remediation has created questions with regards to Windows XP supportability and how MED-V may or may not affect that. For application issues such as 16-bit remediation for x64, MED-V is the only option for enterprise customers.
Given that the supported MED-V solutions (v1 and v2) and its scaled-back VPC counterpart Windows XP Mode leverage the use of a Windows XP operating system instance, the question is always posed to me – Does the Windows XP EOL policy also apply to MED-V? The question may also be asked slightly differently but more pointedly: Does MED-V extend the Windows XP EOL policy?

The short answer is: No MDOP solution extends or affects the Windows XP Lifecycle end-of-life date for support. That date is firm and will not change. April 8, 2014 – as per the reference here:

MED-V Version 1

MED-V Version 1 is technically still in support however, only MED-V V1 workspaces containing the Windows XP operating system are. Even though MED-V V1 did temporarily allow for the use of Windows 2000 workspaces on Windows 7 when released in 2009, it did not extend the support date for Windows 2000 instances beyond the end of 2010. Since mainstream support for MED-V v1 ends on August 10, 2013 (per there is no confusion as there is with MED-V V2 since MED-V V1 will already be out of support by the time 2014 arrives. If customers running MED-V V1 have not already started looking for alternative means of application remediation going forward for Windows 7 and/or Windows 8, the time to start thinking about that is now. Note: MED-V (any version) is not supported on Windows 8.

MED-V Version 2 and Virtual PC for Windows 7

MED-V version 2 will be supported until December 4, 2016 (per
What this means is the actual MED-V and VPC7 code will be supported beyond the Windows XP EOL date – but the Windows XP code will not be. In essence, the host machine’s software will be fully supported until that date but no security or critical updates will be released for the guest operating system (other than potentially code fixes for elements pertaining to the MED-V guest agent.) Remember, MED-V is designed to only serve as a temporary solution for remediation. The end game should be the modernization or replacement of the application(s) in question. Also take heed the same applies for Windows XP Mode.

So the big question . . .

Finally, the last question I am always asked is: What do you recommend our end game date for leveraging MED-V should be?

My honest answer has never wavered: April 8, 2014 – if not sooner.

MED-V V2, V1, or XP Mode?

It looks like both MED-V v1 and v2 will be around for the remainder of the Windows XP support lifecycle. Because of this, I often I get asked the question, “Which version of MED-V should I be using?” as well as “Why should I be using MED-V instead of Windows XP mode?” The following table lists the differences in the basic feature set between versions 1 and 2 of MED-V. This decision making relies on comparing several factors. You also have to take into consideration that MED-V v2 was a complete re-engineering of the product. There is no direct upgrade path between MED-V v1 and v2.

 General Feature Differences between MED V1 and V2

This table focuses on the Primary feature changes and enhancements that drove development of the MED-V/Windows 7/Optimized Desktop Strategy. These include features added into the product as a result of customer feedback for version 1.

Feature MED-V V1 MED-V v2
Policy Source XML-based from Server Local Registry (can be deployed by policy)
Authentications Source AD AD
SSO Support Host-Client? No Yes
SSO Client-Workspace Yes Yes
Workspace Support Persistent and Revertible Only Persistent

General Component Differences between V1 and V2

If you are an experienced MED-V v1 users, you will need to be aware of  some functional component differences. The following table lists the differences between the installable components available between versions 1 and 2 of MED-V.

Component MED-V V1 MED-V v2
MED-V Policy Server Yes No
Image Distribution Server Yes No
MED-V Client MED-V Client MED-V Host Agent
MED-V Workspace MED-V Workspace (Manually Installed) MED-V Guest Agent (Auto-installed)
VM Preparation VM Preparation Tool MED-V Workspace Packager
MED-V Management Console MED-V Management Console MED-V Workspace Packager
Diagnostics Kidaroreport.exe MED-V Toolkit

Differences that Affect Enterprise Decisions

There will be many customers who have been surveying MED-V for enterprise deployments. Many may have looking at MED-V version 1 and are trying to determine whether MED-V v1 or MED-V v2 is suitable. The following chart outlines many factors that determine adoption in the enterprise. Use this to help you make that decision.

Feature MED-V V1 MED-V V2
Client Host OS Support XP, Vista, and Windows 7 Windows 7
VPC Engine VPC 2007 (VPC 6) VPC7  (Non VT requires Patch)
URL Redirection Basic (Bidirectional) Host-to-Guest only
Full Desktop Mode Yes Only through VPC
Reporting (SQL) Yes No
Policy Source Server (XML) Registry/GPO
Seamless Integration Yes – Manual Yes – Automatic
Application Publishing Foundation Kidaro RDP/RemoteApp
Console Yes Yes (Workspace Packer)
Integrated Image Distribution TrimTransfer/BITS/Pre-Staging Pre-staging Only (ConfigManager Integration with DCM)
WMI Support No Yes

 The Feature Comparisons between XP Mode, MED-V V1, and MED-V v2

Finally, how both MED-V v2 and v1 stack up in comparison with XP Mode is outlined in the table below. XP Mode is designed to be a consumer solution while MED-V is for the enterprise.

Feature XP Mode MED-V v1 MED-V v2
Seamless Application Compatibility Environment X X X
Host/Guest Folder Integration X X
USB/Smart Card Redirection X X
Dynamic Application Publishing X Manual X
Custom XP Image X X
Domain Joined X X
SCCM Integration (Bridged) (Bridged and NAT)
IE6 Web Redirection Bi-Directional Host to Guest only
Shared VHD Support X X
Guest Wake-to-Patch X
Automated First-Time-Setup X X
Packaging/Configuration Wizard X X
WMI Monitoring Interface X
Network Printer Syncing  Steve Thomas X
Categories: MED-V, VPC Tags: , , , , , , , ,