MED-V: Troubleshooting Application Publishing in V2.

MED-V builds on top of the RAIL (Remote Applications Installed locally) model that is also in Virtual PC for Windows 7 and Windows XP Mode for Windows 7. Unlike XP Mode or Virtual PC (which put the applications in a specific Start menu Folder) MED-V V2 will scan the All Users Start Menu in the…

0

GPO Settings That Could Potentially Cause Issues with MED-V Features

Here’s one more article I found over on the TechNet Wiki that was written by Microsoft’s very own Steve Thomas. This one talks about some GPO settings that could potentially cause issues with MED-V features: ===== MED-V V2 leverages underlying VPC and RDP\RemoteApp technologies to facilitate support for URL, Print, and document redirection. In addition,…

0

MEDVHost.EXE Command Line Options

Here’s another great article I found over on the TechNet Wiki that was written by Microsoft’s very own Steve Thomas. This one goes through and explains the various MEDVHost.EXE command line options such as exit, FullScreen, RebootVM, toolkit and others: http://social.technet.microsoft.com/wiki/contents/articles/5093.aspx. J.C. Hornbeck | System Center Knowledge Engineer App-V Team blog: http://blogs.technet.com/appv/ AVIcode Team blog:…

1

Ramifications of Switching between NAT (Shared Networking) Mode and Bridged Mode with MED-V V2.

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…

2

How an Enterprise Administrator Can Determine MED-V 2.0 FTS Completion and Provide Remediation Quickly

Here’s a great article I found over on the TechNet Wiki that was written by Microsoft’s own Steve Thomas. This one shows how an enterprise administrator can determine MED-V 2.0 FTS completion and provide remediation quickly: ===== When deploying large amounts of MED-V 2.0 workspaces in the enterprise, Microsoft offers several flexible options for determining…

0

NAT Mode vs. Bridged Mode in MED-V V2

For MED-V V1, we made the following recommendations for MED-V workspaces running in NAT Mode (using VPC Shared Networking.) The article is found here: http://blogs.technet.com/b/medv/archive/2010/10/20/additional-recommendations-when-using-med-v-workspaces-configured-for-nat-mode.aspx For MED-V V2, those recommendations are still in place. But if you decide to use bridged mode instead of NAT mode, there are some important items to consider. If you…

2

How MED-V V2 Manages Memory of Virtual PCs

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…

1

MAC Address Management with MED-V V2 Workspaces

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

1

Using WMI Filters to Disable Legal Notices on MED-V Workspaces

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…

3

MED-V V2: Error: "Open virtual applications found." when launching MED-V applications

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…

1