| Updated on: 11 DEC 2019 VMware Dynamic Environment Manager (formerly known as VMware User Environment Manager) | 17 SEP 2019 | Build 9.9.0.905 |
What's in the Release Notes
The release notes cover the following topics:- About VMware Dynamic Environment Manager
- Updated Components
- Prior Releases
- Documentation
- What's New
- Other Notes
- Migration
- Known Issues
About VMware Dynamic Environment Manager
VMware Dynamic Environment Manager (formerly known as VMware User Environment Manager) offers personalization and dynamic policy configuration across any virtual, physical, and cloud-based environment. Dynamic 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 Dynamic Environment Manager.
Updated Components
For the 9.9 release, only the main product components, FlexEngine and Management Console, contain functional changes. The other products, Application Profiler, Helpdesk Support Tool, and SyncTool, only contain name-related changes (from VMware User Environment Manager to VMware Dynamic Environment Manager). If you are upgrading from a User Environment Manager version, you might only need to upgrade the main product, depending on which component version you are upgrading from. The following guidelines apply.
- No need to upgrade Application Profiler, as long as version 9.6 or later is already installed.
- No need to upgrade Helpdesk Support Tool, as long as version 9.6 or later is already installed.
- No need to upgrade SyncTool, as long as version 9.7 or later is already installed.
Prior Releases
Features and known issues from prior releases of the product can be viewed in the release notes for each release.
Documentation
Documentation for Dynamic Environment Manager is located on docs.vmware.com.
What's New
- Product Rename. For 9.9 and later, the product name is VMware Dynamic Environment Manager.
- Active Directory Attribute Condition. This is a new condition that checks if a specified Active Directory attribute matches the specified criterion.
- Extended Service Branch for Horizon. Dynamic Environment Manager 9.9.0 is an Extended Service Branch (ESB) release. See VMware Knowledge Base (KB) article 52845.
Other Notes
- Symantec Workspace Virtualization Deprecated. Symantec no longer supports Symantec Workspace Virtualization (SWV). Support for SWV is deprecated in Dynamic 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. Dynamic 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 Dynamic Environment Manager, see http://kb.vmware.com/kb/2118056 for the required migration steps.
Known Issues
- The "Windows Server 2016" Operating System condition incorrectly results in a match with Windows Server 2019
The VMware Dynamic Environment Manager agent incorrectly evaluates the Operating System condition when running on Windows Server 2019. If the Operating System condition is configured to check for Windows Server 2016, the Windows Server 2019 operating system is treated as a match.
Workaround: Combine the check for Windows Server 2016 with a second condition to ensure the agent is not running on Windows Server 2019. For example:
Operating system is Windows Server 2016
AND NOT Operating system is Windows Server 2019 - 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.
