Here’s a new Microsoft Enterprise Desktop Virtualization (MED-V) Knowledge Base article we published today. This one talks about an issue where a restricted user can attempt certain actions that they don't have permission to yet get a (false) message indicating it was successful.
Microsoft Enterprise Desktop Virtualization (MED-V 2.0) URL redirection does not work and no temporary URL file *.mdvurl is created in %localappdata%\temp (e.g. C:\Users\username\AppData\Local\Temp\tmpE38B.tmp.mdvurl).
This can occur if the URLs in the MED-V URL list are not valid. An example would be a URL that has a trailing * such as:
To resolve this , navigate to the following registry location and remove the trailing * from any URL addresses listed. HKLM\software\microsoft\medv\v2\UserExperience\RedirectUrls
The only issue relevant to this problem is addressed in the first blog post listed below, in the first section, regarding the creation of the temporary URL file containing the URL to pass the guest via RDPcopy (*.mdvurl). All the other issues that cause URL redirect failures outlined in these two articles do not exist in this scenario.
Understanding and Troubleshooting MED-V v2 URL Redirection http://blogs.technet.com/b/medv/archive/2011/08/10/understanding-and-troubleshooting-med-v-v2-url-redirection.aspx
GPO Settings That Could Potentially Cause Issues with MED-V Features http://social.technet.microsoft.com/wiki/contents/articles/5127.aspx#Internet_Explorer_Policies
For the most current version of this article please see the following:
2671040 : MED-V URL redirection is not working and no *.mdvurl file is being created
J.C. Hornbeck | System Center & Security Knowledge Engineer
Get the latest System Center news on Facebook and Twitter:
App-V Team blog: http://blogs.technet.com/appv/ AVIcode Team blog: http://blogs.technet.com/b/avicode ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ OOB Support Team blog: http://blogs.technet.com/oob/ Opalis Team blog: http://blogs.technet.com/opalis Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/ SCMDM Support Team blog: http://blogs.technet.com/mdm/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/ The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
Hi J.C. Hornbeck,
I am creating a MED-V environment were I have taken two machines. On Machine I have installed VMware and on that Server 2008 r2. I have installed other features like DC, DHCP, IIS, Bits. On this server I have also installed MED-V server configuration manager.
On another machine which is Windows 7 enterprise. I have installed XP mode virtual PC as per the MED-V 2.0 trail guide.
I wanted to knw whether to add this XP mode machine in domain or simply do a sysprep and then later on using Workspace packager deploy on other client machines.
Which version of MED-V are you using? It sounds like V1 since you mentioned the "Server Configuration Manager."