check-circle-line exclamation-circle-line close-line

VMware User Environment Manager Release Notes 9.6.0

Updated on: 12 MAR 2019

VMware User Environment Manager | 13 DEC 2018 | Build 9.6.0.855

 

What's in the Release Notes

The release notes cover the following topics:

About VMware User Environment Manager

VMware User Environment Manager offers personalization and dynamic policy configuration across any virtual, physical, and cloud-based environment. User Environment Manager can simplify end-user profile management with a single and scalable solution. IT can simply map infrastructure (including networks and printer mappings) and dynamically set policies for end users. You can experience quick, personalized, and consistent access to your Windows workspace and applications.

For more information, see the product page: VMware User Environment Manager.

Updated Components

This release updates the main product components, VMware UEM FlexEngine and VMware UEM Management Console, as well as the Application Profiler and the Helpdesk Support Tool. SyncTool is not updated for the 9.6 release. If you are upgrading from version 9.4 or 9.5, upgrade all the product components except SyncTool. If you are upgrading from version 9.3 or earlier, upgrade all product components.

Prior Releases

Features and known issues from prior releases of VMware User Environment Manager can be viewed in the release notes for each release.

Documentation

Documentation for User Environment Manager is located on docs.vmware.com.

What's New

User Environment Manager 9.6.0 fixes a security issue. See the Important Fixes section. Also, User Environment Manager 9.6.0 provides bug fixes described in the Resolved Issues section, and the following enhancements:

  • Folder redirection improvements. More control over the location to which folders are redirected.
  • Configuration Changelog. Provides you with insight into the change history of User Environment Manager configuration files.
  • Additional Windows Support.
    • Windows 10 Version 1809 (November 2018 Update)
    • Windows Server 2019 Standard and Datacenter x64

Important Fixes

This release of VMware User Environment Manager addresses a security issue where malicious local users could under certain circumstances execute code with elevated permissions.

Other Notes

  • Symantec Workspace Virtualization Deprecated. Symantec no longer supports Symantec Workspace Virtualization (SWV). Support for SWV is deprecated in User Environment Manager and can no longer be enabled. Personalization configuration files for which support was enabled previously continue to work. All SWV support will be removed in a future release.
  • Secured Approach. User Environment Manager provides a secured by default approach by logging the users out in case the Flex config files path is not available at logon.

Migration

If you migrate from VMware Persona Management to VMware User Environment Manager, see http://kb.vmware.com/kb/2118056 for the required migration steps.

Resolved Issues

  • An error message, the requested security protocol is not supported, appears when you try to download configuration templates

    When you attempt to download a configuration template to a Windows system with a .NET Framework version that is not sufficiently up-to-date, the download might fail with the error message.

    The User Environment Manager Management Console uses the TLS 1.2 security protocol to securely communicate with the VMware Marketplace. Windows 8 and later systems come with .NET Framework 4, which supports the TLS 1.2 protocol. On these Windows versions, you can also enable the optional .NET Framework 3.5 feature. In this case, the Management Console uses the 3.5 version of the .NET Framework. However, if you do not apply Windows updates to the system after you enable this optional feature, .NET Framework 3.5 might not be sufficiently up-to-date.

    Windows 7 comes with .NET Framework 3.5. If you do not apply Windows updates, .NET Framework 3.5 might not be sufficiently up-to-date.

    This issue is resolved in this release.

Known Issues

  • HTML Access File Transfer

    VMware Blast HTML Access File Transfer depends on the VMware Blast "Configure clipboard redirection" policy setting. To enable download functionality, the "Configure clipboard redirection" policy must be set to "Enabled in both directions" or "Enabled server to client only" (see the "VMware Blast Policy Settings" section in the Setting Up Desktop and Application Pools in View guide for more information.)

    Workaround: HTML Access File Transfer also depends on the Horizon Smart Policy "Clipboard" setting. If this setting is configured to prevent copying from agent to client, the download functionality is disabled.

  • Cannot display button text on some Asian versions of Windows operating systems

    On some Asian versions of Windows operating systems, the button text in the Management Console, the Application Profiler, and the Helpdesk Support Tool might be missing.

    Workaround: Specify the /NoScale command line argument when you start the Management Console, Application Profiler, and the Helpdesk Support Tool.

  • Button text truncated on some Asian versions of Windows operating systems

    On some Asian versions of Windows operating systems, the button text in the Self-Support Tool is truncated if a German Multilingual User Interface is used.

    Workaround: No workaround exists for this issue.

  • Folder redirection of Roaming AppData does not function on Windows 10 Version 1803

    When configuring folder redirection to the AppData folder, the redirection fails for users on Windows 10 Version 1803 systems with the following error message in the log file: [ERROR] Error 0x80070057 redirecting 'AppData' folder to '\\server\share\...'

    Workaround: Upgrade Windows 10 Version 1803 to Build 17134.137 or later.

  • You might encounter limitations with the Windows 10 Start Menu Windows Common Setting

    Configuration settings for the Start menu itself, such as Show most used apps and Use Start full screen, are not saved.

    Workaround: No workaround exists for this issue.

  • You might encounter limitations with the Microsoft Edge Windows Common Setting

    The Open Microsoft Edge with setting and the default search provider are not saved. Also, Microsoft Edge settings cannot roam between systems with different bitness.

    Workaround: No workaround exists for this issue.