Tag: medv v2

One of the most major feedback items about MED-V V1 was the lack of FTA (file type association) linkage between host documents and guest applications. This changed in MED-V V2. Through the use of RDP-redirected folders and the RemoteApp-style of FTA configuration, you are able to take advantage of this so long as the applications…

In July 2011, we published a blog on recommended hotfixes for Windows 7 computers running MED-V v2 (Additional Recommended Updates for MED-V 2.0 that Address Application Issues) referenced here: http://blogs.technet.com/b/medv/archive/2011/07/20/additional-recommended-updates-for-med-v-2-0-that-address-application-issues.aspx?wa=wsignin1.0 Here is an updated list of post-Windows 7 Service Pack 1 hotfixes we recommend you install for use with MED-V that address RDP/RemoteApp/RAIL-related issues. In…

In a previous blog article, I wrote about the differences between NAT and Bridged Mode in MED-V v2. The differences between the two were discussed in detail. You can find the article here: http://blogs.technet.com/b/medv/archive/2011/11/03/nat-mode-vs-bridged-mode-in-med-v-v2.aspx Often I get the question, “What if I want to change the networking mode? Can I do this after the MED-V…

The MED-V Host Agent controls how memory is allocated to the underlying VPC. This memory can be controlled either dynamically where the memory is allocated a certain amount based on host memory configuration or set using a static value. Dynamic Memory Dynamic memory is the default configuration. The following registry key is used to toggle…

In general, it is recommended to leverage the Virtual PC NAT mode (shared networking) when implementing MED-V workspaces. This will take care of any IP address and MAC address management issues. There may be reasons, however, for you to leverage bridged mode in place of NAT mode. Bear in mind, when you choose bridged mode,…

An issue that we have been seeing with MED-V in all versions is the issue of the use of the LegalNoticeCaption and LegalNoticeText values creating disconnects with the seamless user experience while running MED-V workspaces. While the legal notice is sufficient for logging on to the host, since the MED-V workspace is also running an…

When launching a MED-V application, a user may get the following message: “Open virtual applications found. The virtual machine cannot be opened while virtual applications are open. Save any unsaved application data, and then click Close All to continue.” This is caused when the user state/session has changed between the last time MED-V was launched…