|
Omnissa Dynamic Environment Manager 2111
|
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
- Resolved Issues
- 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 components, Omnissa DEM FlexEngine and Omnissa DEM Management Console, as well as Helpdesk Support Tool and SyncTool. Application Profiler is not updated for the 2111 release.
Note: Application Profiler was last updated for the 9.9 release. That update was specifically for the name change from Omnissa User Environment Manager to Omnissa Dynamic Environment Manager. If you are upgrading from a previous version, you do not need to upgrade Application Profiler if version 9.6 or later 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 OneDrive for Business.
Support for storing profile archives in OneDrive for Business. Removed the requirement for a Omnissa Dynamic Environment Manager profile archive Server Message Block (SMB) share and enhanced easy roaming from on-prem to cloud or between public clouds. - Enhanced printer mapping.
Support for configuring timeout and abort options for printer mapping. - Simplified Omnissa Dynamic Environment Manager FlexEngine launch configuration.
Removed the requirement for configuring Group Policy client-side extension to launch the FlexEngine. Also, removed the requirement of configuring logoff scripts. - Support for overriding Active Directory Group Policy.
Omnissa Dynamic Environment Manager now supports overriding Active Directory Group Policy using Omnissa Dynamic Environment Manager’s ADMX-based settings. - Support for multi-session App Volumes setups.
Updated Omnissa Dynamic Environment Manager Trigger from “All AppStacks attached” to “App Volumes logon-time apps delivered” to support configuring session-specific trigger-based actions. - Additional Windows Support.
Omnissa Dynamic Environment Manager now supports Windows 10 Version 21H2, Windows 11, and Windows Server 2022.
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.
- Removed some obsolete functionalities. Removed support for Symantec Workspace Virtualization, Microsoft App-V 4.x, Microsoft Office 2010, and older versions. Also, cleaned up the Management Console UI by removing the deprecated functionality used for configuring Microsoft Windows Group Policy settings.
Migration
If you migrate from Omnissa Persona Management to Omnissa Dynamic Environment Manager, see Modernizing VDI for a New Horizon and KB 2118056 for the required migration steps.
Resolved Issues
-
DirectFlex export does not occur on application close
In some scenarios, closing a DirectFlex-enabled application does not result in a DirectFlex export.
This issue is resolved in this release. -
SyncTool does not support application blocking and privilege elevation
Application blocking and privilege elevation are not supported when a user disconnected from the corporate network logs in and the SyncTool is configured using Group Policy.
This issue is resolved in this release. -
Path-based application blocking settings do not support DFS namespaces
On certain combinations of client OS and file server OS, application blocking configuration files that define path-based settings referencing a DFS namespace are processed incorrectly. As a result, application blocking functionality does not take effect for those paths.
This issue is resolved in this release.
Important: Ensure to enable the advanced "DFS namespace support for application blocking" setting. For more information, see DEM FlexEngine Advanced Settings in NoAD Mode and DEM FlexEngine Group Policy Object Advanced Configuration Settings in the Installing and Configuring Omnissa Dynamic Environment Manager guide at Omnissa Product Documentation. -
Start menu is not responding or missing icons on the second logon
On some Windows versions, the Windows Common Setting "Windows Explorer and view settings" prevents the Start menu from working correctly.
This issue is resolved in this release.
To resolve this issue on earlier versions, add these two lines to the Flex config file that references “Windows Explorer and view settings”:[ExcludeIndividualRegistryValues] HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced\StartMenuInit -
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.
This issue is resolved in this release.
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 Desktops and Applications in Omnissa Horizon 8 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/NoScalecommand 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, setREG_DWORDvalueDirectFlexto1in theHKLM\SOFTWARE\Immidio\Flex Profileskey (for Group Policy-based setups), or in theHKLM\SOFTWARE\<Previous_Company_Name>, Inc.\<Previous_Company_Name> UEM\Agent\Configurationkey (for NoAD). -
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.
Note: This issue does not occur when using OneDrive for Business integration.
Workaround: OverwriteFlex+ Self-Support.exein the installation folder with a copy from Omnissa Dynamic Environment Manager 2103 or 2106. No further configuration is required.
Alternatively, you can copyFlex+ Self-Support.exeandFlex+ Self-Support.exe.configfiles from Omnissa Dynamic Environment Manager 2103 or 2106 into another folder and launch the tool using the files you copied.
Was this page helpful?