The MED-V Blog

The Microsoft Enterprise Desktop Virtualization blog.

Now available: Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 – Localization Update

Now available: Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 – Localization Update

  • Comments 1
  • Likes

KBWe published the following new Knowledge Base article/update today that’s primarily to address localization but note that there are a couple additional fixes that it includes:

=====

Summary

This update for MED-V 2.0 provides the capability for localized content to be presented in both the MED-V Workspace Packager and the MED-V Host Agent. The MED-V Workspace Packager is available in 11 different languages and the MED-V Host Agent is available in 24 different languages. The language that will be shown to the user will match the current UI culture configured for Windows. For example, when the current UI culture in Windows is set to German, MED-V will display in German. If the configured language for Windows is not one of the supported languages, then the user will be presented with the default language, with the final default being the English UI.

This update also resolves two reported issues relating to the configuration of the memory on the virtual machine and to the publishing of application shortcuts.

More Information

Information on the localization update
This update for MED-V 2.0 provides the capability for localized content to be presented in both the MED-V Workspace Packager and the MED-V Host Agent.

  • This update for MED-V 2.0 provides the capability for localized content to be presented in both the MED-V Workspace Packager and the MED-V Host Agent.
  • MED-V automatically detects the current language setting (current UI culture) for Windows and uses this for the display of the MED-V Workspace Packager and the MED-V Host Agent.
  • The MED-V Host Agent patch can be used with workspaces packaged with previous versions of the MED-V Workspace Packager. Once applied, the MED-V Host Agent will be localized. It is not necessary to package new workspaces with the patched MED-V Workspace Packager to see localized content in the MED-V Host Agent.
  • The MED-V Host Agent patch will update the MED-V Guest Agent. If the patch is applied to a machine where a workspace has been installed and FTS has completed successfully, there are a few behaviors to be aware of:
    1. While the MED-V Guest Agent updates, applications will not be available.
    2. If applications are open when the patch is applied, a reboot will be required to launch applications.
    3. If credential caching is disabled, the user will be required to log into the MED-V workspace again.
  • The MED-V Workspace Packager is now available in 11 different languages: English (en-us), French (fr), Italian (it), German (de), Spanish (es), Korean (ko), Japanese (ja), Brazilian Portuguese (pt-br), Russian (ru), Chinese Traditional (zh-tw), and Chinese Simplified (zh-cn).The MED-V Host Agent is now available in 24 different languages: English (en-us), French (fr), Italian (it), German (de), Spanish (es), Korean (ko), Japanese (ja), Brazilian Portuguese (pt-br), Russian (ru), Chinese Traditional (zh-tw), Chinese Simplified (zh-cn), Dutch (nl), Swedish (sv), Danish (da), Finnish (fi), Portuguese (pt), Norwegian (no), Polish (pl), Turkish (tr), Hungarian (hu), Czech (cs), Greek (el), Slovak (sk), and Slovenian (sl).

Information on the additional fixes:
  • Configuration of Memory on the Virtual Machine: The previous limit for the maximum amount of memory that could be configured for a workspace to use was 2048 MBs. This limit has been increased to 3712 MBs which is the maximum allowed by Windows Virtual PC. Note that you configure the amount of memory to be used by the workspace using the “VmMemory”, “VmHostMemToGuestMemCalcEnabled”, “VmGuestMemFromHostMem”, and “VmHostMemToGuestMem” parameters of the “New-MedvConfiguration” Windows Powershell cmdlet.
  • Publishing of Application Shortcuts: Workspace application shortcuts were not copied to the start menu when the full path to the shortcut published by Windows Virtual PC exceeded 256 characters. This issue was mostly seen in configurations utilizing a long workspace name and long application shortcut names.
System Requirements
Windows 7 (Professional, Enterprise or Ultimate) release or SP1, x86 or x64, with 2GB of RAM minimum
The MED-V 2.0 patch requires that the MED-V 2.0 Workspace Packager and or MED-V 2.0 Host Agent already be installed and approximately 50 mb of disk space is available.
How to obtain the MED-V 2.0 Localization Update
The MED-V 2.0 Localization Update can be obtained from the Microsoft Download Center:
http://www.microsoft.com/downloads/details.aspx?FamilyID=3a185a14-5ab0-4260-ae6b-418b3ca77bf7
Installation Instructions

How to apply the MED-V Host Agent patch
1. Copy the MED-V_HostAgent_Patch.exe to any machine that has the MED-V Host Agent installed.
2. Launch the MED-V_HostAgent_Patch.exe and follow the prompts to apply the patch.
3. The user may be prompted to reboot if IE is running, as the patch updates the browser for MED-V URL redirection. The user may be prompted to reboot if the MED-V PowerShell modules are imported.
Note: If you are applying the patch via a software distribution tool, standard install parameters can be entered at a command prompt. For example “/qn /norestart” will install quietly with no UI and suppress any restarts.


How to apply the MED-V Workspace Packager patch
1. Copy the MED-V_ WorkspacePackager_Patch.exe to any machine that has the MED-V Workspace Packager installed.
2. Launch the MED-V_ WorkspacePackager_Patch.exe and follow the prompts to apply the patch.
3. The user may be prompted to reboot if the MED-V PowerShell modules are imported.

=====

The information above was published today in the following Microsoft Knowledge Base article written by Jeff Patterson:

KB2541024 - Microsoft Enterprise Desktop Virtualization (MED-V) 2.0 – Localization Update

J.C. Hornbeck | System Center Knowledge Engineer

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

clip_image001 clip_image002

Comments
  • I have my virtual setup but the update cannot locate workspace packager host agant yet they are runing

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment