Hybrid Workspaces 23.1 Readme

March 2023

The information in this Readme pertains to Hybrid Workspaces Application Streaming and Packaging. Customizing applications to a virtual package and then delivering through application streaming on any platform with an HTML5 browser or even locally on a Windows OS device.

The following information is included in this Readme:

1.0 What’s New in Version 23.1

Hybrid Workspaces 23.1 includes the following updates:

Important note on the name change: Effective October 2022, the application's name is changed from Micro Focus Desktop Containers to Hybrid Workspaces.

1.1 Hybrid Workspaces - Application Streaming Server

This release includes several major features:

  • New Elastic Cloud feature allows deployment of Turbo application servers to your Azure tenant with a single click!

  • New Files API provides a unified programmable interface for browsing and managing connected storage providers. For more information, see the Files API documentation.

  • Other new features include:

    • New Launch on Install setting in the Workspace application settings allows applications to automatically launch upon installation on the device.

    • Workspaces can now be configured with default isolation and local user folder access settings. Workspace applications can inherit these settings from the workspace or specify application-specific settings.

    • JVM http(s) proxy settings can now be configured from the administration site.

    • New Shell Integration settings provide fine-grained control over application interactions with the host device, such as shortcuts, file associations, and shell extensions.

    • Azure Active Directory with OpenID Connect Single Sign-On integrations can now automatically connect OneDrive on login if the Azure application registration is configured to grant drive permissions.

    • New /install-services and /uninstall-services commands unvirtualize the API and administration sites in order to workaround certain antivirus incompatibilities.

    • Users now see a warning that their session is about to expire before being logged out automatically from the Portal.

  • Other improvements include:

    • Improved default application launch performance by enabling the assembly cache by default.

    • Expanded configuration options for workspace applications from the command line administrative tool.

    • Added click and drag support to reorderable controls on the administration site.

    • Added a Test action for file system storage providers on the administration site.

    • Updated the default federation source to hub.turbo.net to eliminate redirects.

    • Improved various error messages and text values.

  • This update includes fixes for the following issues:

    • Certain AppLocker configurations caused the Turbo Server service to fail to start due to a VM incompatibility

    • Notifications could incorrectly show on top of the Notice and Consent dialog

    • Dashboard session icons could display an incorrect state after refreshing the dashboard

    • Install on My PC could incorrectly install the latest version when attempting to install an older version in certain circumstances

    • Active sessions could experience T: Drive connection failures if the user's ticket expired during the session

    • Attempting to disable repository federation could fail in certain scenarios

    • Performance reports failed to export correctly in CSV format

    • Repository imports that specified a release number did not prioritize exact matches and did not support prefix matching

    • Active Directory synchronized item selections could fail to save if the results exceeded 1000 items

    • License management pages do not load when an invalid or expired license was installed

    • Certain file operation errors could result in handle leaks on the Portal server

    • The Turbo Application Server service could take a long time to restart in certain circumstances

    • Large numbers of webhook subscriptions with undeliverable target URLs could result in poor server performance

    • Turbo services could become unresponsive and fail to recover in rare circumstances

1.2 Hybrid Workspaces - Studio (Application Packaging Tool)

This update includes the following improvements and fixes:

  • The Turbo VM is updated to version 22.12.10

  • Load virtual side-by-side assemblies from pre-cache directory if configured

  • Fix for a crash when shell opening a .zip file

  • Support for App-V dynamic configuration import

  • Support for Windows Defender copy accelerator hook

  • Allow the --use-dll-cache flag when the pre-cache directory is configured to a network share

  • Fix for merge isolated registry keys going to the sandbox when not present on native machine

  • Fix for virtual services indicating that they are in a user session

  • Fix for a build error when using the privatize file setting

  • Support for 64-bit folders in ThinApp package import

  • Windows 11 compatibility updates

  • Fix for failed capture when a registry key name contains a newline character

  • Fix timeout when pushing large images to Turbo Server

  • Fix mount aliases being overridden by snapshot directories

  • Fix shell execute by explorer.exe via IShellDispatch interface

  • Stub executable files are now signed for standalone executable outputs

  • Fix crash in certain 64-bit standalone executable outputs

  • Updates to default capture exclusions

2.0 Product Documentation

The following sources provide information about Hybrid Workspaces:

3.0 Understanding the Upgrade Requirements

  • All application configuration documents and application certificates created with ZENworks Application Virtualization 8.x, 9.x, 10.x, and 11.x must be re-created in order for application streams to work with the Hybrid Workspaces standalone components.

    To generate a new certificate and regenerate the configuration files:

    1. In the Advanced section of the Hybrid Workspaces Studio, click the App Config button to regenerate the application stream configuration files.

    2. To generate a new site license certificate, click Advanced.

    3. In the Application Certificates dialog box, click Request Certificate.

    4. Specify the following information in the fields:

      • Organization: The organization name.

      • Unit: The user or unit name.

      • Allowed Portal Hosts: The allowed host names of the servers from which the application will stream.

    5. Click Request to request the site license certificate, then save the certificate to a desired location.

    6. Click the App Config button to regenerate the application stream configuration files again.

  • ZENworks Application Virtualization (ZAV) versions, Micro Focus Desktop Containers (MFDC) versions, and Hybrid Workspace versions always run side by side on a device. Running older versions (ZAV or MFDC) do not change in any way when running in a Hybrid Workspaces environment. However, if you open a ZAV or MFDC version in Hybrid Workspaces and save it, the package is being upgraded to the latest Hybrid Workspaces version and the older version becomes obsolete and should be decommissioned.