Additional Recommended Updates for MED-V 2.0 that Address Application Issues

imageHi everyone, Steve Thomas  here.  If you are using MED-V version 2.0, you are also using RDP 7.0 and the RemoteApps feature for application publishing. Both MED-V and XP Mode rely on this technology for guest application publishing to the host. Instead of the Windows 7 RDP client connecting to an RDS server, it is connecting to the virtual machine’s guest operating system. Virtual PC for Windows 7’s integration components enable this.

It is recommended to use Windows 7 Service Pack as the host operating system version however, if you have not updated to Windows 7 Service Pack 1, I would recommend installing these RemoteApp updates which address behaviors that can also appear in MED-V v2 environments:

2287493: The RemoteApp program is not terminated after the idle session time limit expires on a computer that is running Windows Server 2008 R2

2384602: The pop-up windows of a RemoteApp program may be hidden in Windows Server 2008 R2 and in Windows 7

2388381: You cannot start a RemoteAPP program that is hosted on a Windows XP SP3 virtual machine through Terminal Services Web Access or Remote Desktop Web Access in Windows Server 2008 R2, in Windows 7 or in Windows Vista

If Windows 7 Service Pack 1 has been installed on the MED-V Host, I would recommend these post-SP1 updates for RemoteApps/RDP:

2522743: You cannot use a calendar control in a RemoteApp application when you use the RDC 7.0 client to connect to the RemoteApp application from a computer that is running Windows 7 or Windows Server 2008 R2

2524668: The single sign-on feature does not work in Windows 7 or in Windows Server 2008 R2 when you try to start a full remote desktop connection through RD Web Access

2526629: The logon message is not displayed correctly when you connect to a RemoteApp application from a computer that has multiple monitors and that is running Windows 7 or Windows Server 2008 R2

Remember: MED-V V2 leverages RDP/RemoteApps technology. Troubleshooting and data collection of these scenarios often follows a parallel approach to troubleshooting an RDP client connecting to a Remote Desktop/Terminal Services server.

Steve Thomas | Senior Support Escalation Engineer

App-V Team blog: https://blogs.technet.com/appv/
AVIcode Team blog: https://blogs.technet.com/b/avicode
ConfigMgr Support Team blog: https://blogs.technet.com/configurationmgr/
DPM Team blog: https://blogs.technet.com/dpm/
MED-V Team blog: https://blogs.technet.com/medv/
OOB Support Team blog: https://blogs.technet.com/oob/
Opalis Team blog: https://blogs.technet.com/opalis
Orchestrator Support Team blog: https://blogs.technet.com/b/orchestrator/
OpsMgr Support Team blog: https://blogs.technet.com/operationsmgr/
SCMDM Support Team blog: https://blogs.technet.com/mdm/
SCVMM Team blog: https://blogs.technet.com/scvmm
Server App-V Team blog: https://blogs.technet.com/b/serverappv
Service Manager Team blog: https://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: https://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: https://blogs.technet.com/sus/

clip_image001 clip_image002