Omnissa Dynamic Environment Manager Release Notes

Omnissa Dynamic Environment Manager 2106 | 15 JUL 2021 | Build 10.3.0.993

What's in the Release Notes

The release notes cover the following topics:

• About Omnissa Dynamic Environment Manager
• Updated Components
• Prior Releases
• Documentation
• What's New
• Other Notes
• Migration
• Known Issues

About Omnissa Dynamic Environment Manager

Omnissa Dynamic Environment Manager™ offers personalization and dynamic policy configuration across any virtual, physical, and cloud-based environment. Omnissa 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: Omnissa Product Documentation.

Updated Components

This release updates the main product, Omnissa DEM Management Console. This release does not update Omnissa DEM FlexEngine, but the Omnissa Dynamic Environment Manager 2106 installer installs the 2103 version of Omnissa DEM FlexEngine.

Also, Application Profiler, Helpdesk Support Tool, and SyncTool are not updated for the 2106 release.

Note: Application Profiler was last updated for the 9.9 release. That update was specifically for the name change from User Environment Manager to Omnissa 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 Omnissa DEM FlexEngine if version 2103 is already installed.
• No need to upgrade Helpdesk Support Tool if version 2103 is already installed.
• No need to upgrade SyncTool if version 2103 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 Omnissa Dynamic Environment Manager is located at Omnissa Product Documentation.

What's New

• Omnissa Dynamic Environment Manager integration with Omnissa Workspace ONE UEM (Unified Endpoint Management).
  • Removes the requirement for a Omnissa Dynamic Environment Manager configuration Server Message Block (SMB) share
  • Creates a Omnissa Dynamic Environment Manager config profile file, which contains all the Omnissa Dynamic Environment Manager configuration settings, using the Omnissa Dynamic Environment Manager Management Console
  • Stores the Omnissa Dynamic Environment Manager config profile file in Workspace ONE UEM
  • Delivers the Omnissa Dynamic Environment Manager configuration to endpoints using Workspace ONE UEM smart groups for flexible targeting
  • Supports integrating an existing Omnissa Dynamic Environment Manager deployment with Workspace ONE UEM without losing any of your existing Omnissa Dynamic Environment Manager configuration
  • Supports switching from integration mode, which uses a Omnissa Dynamic Environment Manager config profile file, back to standalone mode, which uses a Omnissa Dynamic Environment Manager configuration SMB share, without losing any of your existing Omnissa Dynamic Environment Manager configuration

Caution: The Omnissa Dynamic Environment Manager integration with Workspace ONE UEM feature is available with Omnissa Dynamic Environment Manager 2106. The feature is dependent upon the Workspace ONE UEM release with the corresponding integration feature enabled. You must upgrade both products for the integration to work. However, at this time, the Workspace ONE UEM integration feature is not released. Therefore, only enable integration in Omnissa Dynamic Environment Manager after Workspace ONE UEM releases this integration feature and you upgrade to that release.

Other Notes

• Product Rename. For 9.9 and later, the product name is Omnissa Dynamic Environment Manager.
• Secured Approach. Omnissa 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 Omnissa Persona Management to Omnissa Dynamic Environment Manager, see Techzone and KB 2118056 for the required migration steps.

Known Issues

Note: For any instance of <Previous_Company_Name>, please replace this string with the actual name of the previous company.

• HTML Access File Transfer
  Omnissa Blast HTML Access File Transfer depends on the Omnissa 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 Blast Policy Settings section in the Setting Up Desktop and Application Pools in View guide at Omnissa Product Documentation 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.

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

• 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\<Previous_Company_Name>, Inc.\<Previous_Company_Name> UEM\Agent\​Computer Configuration key, or add the RevertOnShutdown="0" attribute in the FlexRepository\AgentConfiguration\Computer.xml file.

• 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.
  Workaround: 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\<Previous_Company_Name>, Inc.\<Previous_Company_Name> UEM\Agent\Configuration key (for NoAD).