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 underlying operating system, a logon is required for accessing the published applications running under Windows XP.
In our Best Practices guide (http://technet.microsoft.com/en-us/library/gg548491.aspx) we recommend to disable this through group policy. Customers, however, often ask, “What if I want to use the same OU for both the Windows 7 host and the Windows XP guest workspace? How can I prevent a GPO containing the LegalNotice Caption and LegalNoticeText values from affecting the XP workspaces yet allow them to still affect the Windows 7 hosts?”
WMI Filter
The best way to do this is through a WMI filter. When you apply a WMI filter to a GPO, the GPO will only apply if the WMI filter (which is a WQL query) evaluates to TRUE. WMI filters are created and applied to a GPO using the Group Policy Management tool.
It is important to note that this will be best effective if the following conditions are true:
1.) The policy regarding legal notices are applied at the OU level
2.) The policies within the GPO for legal notice
Creating and Linking a WMI Filter to a GPO
To create and apply a WMI GPO filter, you must be a member of the Domain Administrators group, or otherwise be delegated permissions to modify the GPOs. You will then use the GPMC to create a WMI filter that will query for a specified version of Windows.
You will need to fully restart both the MED-V host and Workspace for this to take effect if the workspace has already been deployed.
If there is a mix of XP and Windows 7 in the same OU; which may occur while Windows 7 migration is occurring; I would try (meaning test this and tell me if it works) using the following WMI query in order to make sure that the yet to be migrated XP machines are not excluded from receiving this important GPO.
It is the same WMI Query that used to monitor the success of first-time-setup of the MED-V workspace
Set the namespace to root\microsoft\medv
Select * from FTS_Status where StatusCode != 0
This should be true for all non-MED-V XP machines; Windows 7 and XP alike (and those MED-V workspaces that failed first-time-setup).
Excellent point, Norm! I talk about this one a little bit on my personal blog:
blogs.technet.com/.../how-an-enterprise-administrator-can-determine-med-v-2-0-fts-completion-and-provide-remediation-quickly.aspx