Omnissa Dynamic Environment Manager Release Notes

Omnissa Dynamic 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. 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.

Omnissa Dynamic Environment Manager Release Notes provides information about the new features and enhancements in each release. This page contains a summary of the new capabilities, issues resolved, and known issues that are reported in each version.

What's New

• Support for creating and editing agent configuration files from DEM Management Console. We are excited to introduce the addition of a new Agent Configuration tab within the DEM Management Console. This tab provides user-friendly options to edit important agent configuration files directly from the console, saving time and reducing the risk of manual errors that could affect the agent behavior. For more information, see Using Agent Configuration Tab.

• Enhancements to Config File Versioning. Individual versions of a configuration file can now be deleted directly from the Version History tab.

• Enhancements to the User Environment Configuration. All user environment settings previously exclusive to DirectFlex-enabled configuration files are now fully supported for non-DirectFlex configuration files. You can configure Shortcuts, File Type Associations (FTAs), and Environment Variables for non-DirectFlex config files.

• Support for Horizon Agent Auto Upgrade feature. The DEM Agent (the FlexEngine component from Omnissa Dynamic Environment Manager) can be installed or upgraded using the Horizon Agent Auto Upgrade feature, enabling Horizon admins to seamlessly deploy or update the DEM Agent through the Horizon Console. For more information, see Auto Upgrade of Horizon Agents and other Supported Agents and Using Horizon Agent Auto Upgrade to Install or Upgrade DEM Agent.

• Updated Components. This release updates the main product components. Application Profiler, Helpdesk Support Tool, and SyncTool are not updated.

Resolved Issues

We are always working to improve Omnissa Dynamic Environment Manager with every release. This release reports no major bug fixes.

Known Issues

• DEM-188: New Microsoft Teams does not trigger DirectFlex processing
  Launches of the new Microsoft Teams are performed by the AppInfo service. In older versions of Dynamic Environment Manager, AppInfo starting 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 2 in the HKLM\SOFTWARE\Immidio\Flex Profiles key (for Group Policy-based setups), or in the HKLM\SOFTWARE\Omnissa\DEM\Agent\Configuration key (for NoAD).

• DEM-574: Self-Support Tool only saves selected user-managed auto-start shortcuts that match the search filter
  When a user configures shortcuts for auto-start using the Self-Support Tool with a non-empty search filter, only the selected shortcuts that match the filter are saved.
  Workaround: Clear the search filter before saving.

• 2870360: 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\Omnissa\DEM\Agent\Configuration key (for NoAD).

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

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

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

• DEM-902: "Run once" does not work for user environment settings in silo-based non-DirectFlex config files
  If the Run once option is selected for a user environment setting configured in a non-DirectFlex configuration file in a silo, Error determining whether DEM setting should be applied - DEM path '\\domain\share\silos\...' does not start with Flex config files path '\\domain\share\general\' is logged at run-time. Because the run-once status of the setting cannot be determined, it is applied every time.
  Workaround: No workaround exists for this issue.

Documentation

Documentation for Omnissa Dynamic Environment Manager is located at Omnissa Product Documentation.

Internationalization

Dynamic Environment Manager content is available in English and Chinese. For details on Omnissa’s localization strategy, see the knowledge base article Announcing Omnissa Localization Support.

Support Contact Information

To receive support, access Customer Connect. For information about filing a Support Request in Customer Connect and using Cloud Services Portal, see the Knowledge Base (KB) article 6000005.