VMware Dynamic Environment Manager (formerly known as VMware User Environment Manager) | 15 OCT 2020 | Build

What's in the Release Notes

The release notes cover the following topics:

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. VMware 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

This release updates the main product components, VMware DEM FlexEngine and VMware DEM Management Console. Application Profiler, Helpdesk Support Tool, and SyncTool are not updated for the 2009 release.

Note: Application Profiler, Helpdesk Support Tool, and SyncTool, were last updated for the 9.9 release. Those updates were specifically for the name change from VMware User Environment Manager to VMware Dynamic Environment Manager.

If you are upgrading from a previous 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 if version 9.6 or later is already installed.
  • No need to upgrade Helpdesk Support Tool if version 9.6 or later is already installed.
  • No need to upgrade SyncTool if 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 for Dynamic Environment Manager is located on docs.vmware.com.

What's New 

  • Additional Comparison Operators for Conditions. You have the option of applying the Is less than and Is greater than operators to the following conditions: Active Directory Attribute, Active Directory Site Name, Endpoint Name, Environment Variable, Horizon Client Property, and Registry Value.
  • Self-Support Tool Supports Japanese. Japanese is available as a VMware Dynamic Environment Manager Self-Support Tool language.
  • Support of Running Tasks During Machine Startup and Shutdown. You can configure tasks to run during computer startup or shutdown.
  • Support of Active Directory Attributes in FlexEngine Configuration and Dynamic Environment Manager Settings. You can use Active Directory attributes in FlexEngine configuration settings (Group Policy, NoAD.xml, and computer environment settings agent configuration) and in Dynamic Environment Manager configuration files that accept environment variables.
  • Support of Active Directory Attributes and ViewClient Properties in Placeholders. You can use Active Directory attributes and ViewClient properties in placeholders within predefined settings.
  • Additional Windows Support.
    • Windows 10 Version 20H2 (October 2020 Update). See KB 57386 for the VMware Dynamic Environment Manager and Windows 10 Versions Support Matrix.

Other Notes

  • Product Rename. For 9.9 and later, the product name is VMware Dynamic Environment Manager.
  • Symantec Workspace Virtualization Deprecated. Symantec no longer supports Symantec Workspace Virtualization (SWV). Support for SWV is deprecated in VMware 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. VMware 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.


If you migrate from VMware Persona Management to VMware Dynamic Environment Manager, see https://techzone.vmware.com/resource/modernizing-vdi-new-horizon and http://kb.vmware.com/kb/2118056 for the required migration steps.

Resolved Issues

  • VMware Dynamic Environment Manager is not invoked at logon on Windows 10 Version 2004

    On very rare occasions, Windows 10 Version 2004 fails to call VMware Dynamic Environment Manager at logon when it is configured in NoAD mode. The result is that users of the affected desktops do not get their settings and other VMware Dynamic Environment Manager configurations.

    This issue is resolved in this release.

  • Windows Server 2016 resets the default web browser

    The Default applications - File type associations and protocols Windows Common Setting cannot be used to roam the default web browser choice on Windows Server 2016. Shortly after logon, Windows resets the default web browser setting.

    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.

  • Privilege elevation not working after first logon in NoAD mode

    If FlexEngine is installed in NoAD mode, occasionally privilege elevation might not function correctly after the first logon.

    Workaround: After installing FlexEngine in NoAD mode, create an empty registry value ProfileArchivePath under key HKLM\SOFTWARE\VMware, Inc.\VMware UEM\Agent\Configuration, for instance by running the following command: reg ADD "HKLM\SOFTWARE\VMware, Inc.\VMware UEM\Agent\Configuration" /v ProfileArchivePath /d "" /f

  • FlexEngine does not run after reboot

    When FlexEngine is configured in NoAD mode and computer environment settings support is enabled, FlexEngine sometimes does not run during the first session after a reboot.

    The issue is related to DEM logic that reverts computer settings at shutdown and can impact Windows functionality in some scenarios. By default, this logic is enabled and does not have any impact on the functionality. In non-persistent setups, there is no need to revert, and in persistent setups previously applied settings are automatically reverted before new settings are applied at the next boot.

    Workaround: Set REG_DWORD value RevertOnShutdown to 0 in the HKLM\SOFTWARE\VMware, Inc.\VMware UEM\Agent\​Computer Configuration key.

  • COM servers do not trigger DirectFlex processing

    In older versions of Dynamic Environment Manager, instantiating an out-of-process COM object hosted by a DirectFlex-enabled executable triggered DirectFlex processing. With the default DEM configuration, this behavior does not exist.

    To enable the old behavior, set REG_DWORD value DirectFlex to 1 in the HKLM\SOFTWARE\Immidio\Flex Profiles key (for Group Policy-based setups), or in the HKLM\SOFTWARE\VMware, Inc.\VMware UEM\Agent\Configuration key (for NoAD).

check-circle-line exclamation-circle-line close-line
Scroll to top icon