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 provide 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

• Condition – AD Username. Introducing a User Name condition for targeting policy assignments to specific Active Directory users. See Managing Conditions.

• Entitlement-Based Filtering in DEM Self-Support Tool. The Self-Support Tool now supports condition-based filtering for auto-start shortcuts. See Configuring Dynamic Environment Manager Self-Support to Allow Managing Auto-Start Shortcuts.

• Support Bulk Delete for Personalization Configuration Files. The Multi-select Delete capability in the Management Console now also applies to personalization configuration files. When Multi-select Delete is enabled, you can configure a Delete Limit to set the maximum number of files that can be deleted in a single operation. This limit applies across all configuration file types. See Managing DEM Management Console.

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

Resolved Issues

• 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.
  This issue is resolved in this release.

• DEM-1175: “Run once” does not work for user environment settings in non-DirectFlex config files when SyncTool is used
  If SyncTool is used and the Run once option is selected for a user environment setting configured in a non-DirectFlex configuration file, Error determining whether DEM setting should be applied - DEM path 'C:\Users\...\AppData\Local\...\FlexSync\...' 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.
  This issue is resolved in this release.

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-724: 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).

• DEM-725:

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

Documentation

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

Internationalization

Dynamic Environment Manager content is available in English, Simplified Chinese, and Japanese. 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.