Omnissa Dynamic Environment Manager Release Notes

About 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. 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. To learn more, see Omnissa Product Documentation.

What's New

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

• Extended Service Branch for Horizon. Dynamic Environment Manager 2111.1 is an Extended Service Branch (ESB) release. See Knowledge Base (KB) article 86477.

Resolved Issues

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

• Windows 10 and Windows 11 incorrectly logged as "Version 2009"
  The detailed OS version information in the FlexEngine log file is always logged as "Version 2009" for Windows 11 and Windows 10 Version 20H2 or later.
  This issue is resolved in this release.

• Privilege elevation does not work if LSA protection is enabled
  If LSA protection is enabled in Windows, DEM's privilege elevation functionality does not work and the log file contains log messages like "Cannot launch elevated task '...' (token infrastructure not available)" or "Privilege elevation is not initialized properly – privilege elevation settings are not applied".
  This issue is resolved in this release.

• ADMX-based computer settings do not apply at startup
  In some scenarios, ADMX-based computer settings can be processed during computer startup without the corresponding registry settings being applied.
  This issue is resolved in this release.

• Path-based export skipped on Citrix
  In some Citrix setups, an error can occur that causes the path-based export to be skipped. The log file contains log messages like "Error 1733 determining user name for this session", "Logon time: <error>", and "Unable to determine whether multiple sessions are active -- skipping path-based export".
  This issue is resolved in this release.

• Membership check for local administrators group fails
  Upgrading to DEM 2111 or later and using Group Policy for agent configuration results a difference in group membership condition evaluation for administrator users because different tokens are being used.
  This release adds an option to check the full token in group membership conditions.

• Self-Support Tool does not show all applications
  When using Omnissa Dynamic Environment Manager with SMB profile archives share, the Self-Support Tool sometimes does not show all applications.
  This issue is resolved in this release.

• Horizon Smart Policies configuration might not be considered at logon
  In NoAD mode, some Horizon Smart Policies configuration might not be considered at logon.
  This issue is resolved in this release.
  Workaround: Create an empty REG_SZ value ProfileArchivePath in key HKLM\SOFTWARE\<Previous_Company_Name>, Inc.\<Previous_Company_Name> UEM\Agent\Configuration of the base image.

• Elevated tasks dialog does not escape pipe symbols in arguments textbox
  Processing an elevated tasks config file containing strange characters in the command-line arguments reports [ERROR] Relative path '' is not supported for privilege elevation.
  This issue is resolved in this release.
  Workaround: Manually replace pipe symbols in the arguments of an elevated task with [Flex#%PiPe%](case-sensitive).

• DEM does not run during first logon after a reboot
  In some scenarios, the DEM agent does not run during the first logon after a reboot. Subsequent logons work as expected, until the system is rebooted again.
  This issue is resolved in this release, but the fix is disabled by default. To enable it, create a REG_DWORD value WinlogonFix in key HKLM\Software\<Previous_Company_Name>, and set it to 1.

Note: Performing an uninstall while the WinlogonFix=1 setting is configured results in Winlogon events 6000 and 6001 in the application event log at subsequent logons, complaining about "winlogon notification subscriber <Previous_Company_NameUEM>". To prevent this, remove the WinlogonFix setting before uninstall.

Known Issues

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

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

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