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

• User-Managed Auto-Start Shortcuts. A new feature that allows end users to choose which shortcuts established by administrators should be auto-started at logon. See Configure Shortcuts and Configure Dynamic Environment Manager Self-Support to Allow Managing Auto-Start Shortcuts.

• Config-file Overview. Added new Comments and Condition columns on the configuration file overview. Administrators can view additional information about the configuration files without accessing the files.

• Deprecate "Download Config Template". Deprecated support for default configuration template download from the Dynamic Environment Management console.

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

Resolved Issues

Note: The numbers included before the resolved issues are used for internal issue tracking system.

• AVA-23248: Whenever an App Volumes classic application package is delivered, Dynamic Environment Manager triggered tasks using the App Volumes logon-time apps delivered trigger can be triggered multiple times. As a result, the selected actions might run again causing unexpected results.
  This issue is resolved in App Volumes 2406.

Known Issues

Notes: The numbers included before the known issues are used for internal issue tracking system.

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

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

• 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\<Previous_Company_Name>, Inc.\<Previous_Company_Name> UEM\Agent\Configuration key (for NoAD).
  
  Note: To enable the workarounds of DEM-188 and 2870360 at the same time, DirectFlex must be set to 3.

• DEM-141: Default browser settings and .pdf file type association missing after applying February/March 2024 Windows Updates or later
  The Microsoft Windows Updates for February and March 2024 and later break the roaming of a user's default browser and .pdf file type association. The roaming of other file-type associations and protocols is not affected.
  This issue affects all currently supported versions of Omnissa Dynamic Environment Manager.
  Workaround: See the Knowledge Base (KB) article 97169.

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

• AVA-23846: Whenever multiple on-demand App Volumes applications are launched or an on-demand application is launched with a classic application package attached to the agent computer, Dynamic Environment Manager triggered tasks using the App Volumes logon-time apps delivered trigger can be triggered multiple times. As a result, the selected actions run again causing unexpected results.
  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.

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.