4 min read time

Introducing Hybrid Workspaces 24.7

by   in Portfolio

Today's workers demand access to their job-critical applications and resources regardless of where they are or the type of devices they are using. IT organizations need to meet that demand while ensuring security of their corporate resources and information.

Hybrid Workspaces provides secure access to resources from anywhere, on any platform. Applications can be installed locally or streamed to any device with HTML 5 support. Maybe your users require secure access to a health management application and related health files, a human resource application with employee personal information, or simply a word processor application and sensitive business documents. Hybrid Workspaces lets you meet these access requirements knowing that the system and data is secure. Or maybe your users need access to a legacy application that is no longer supported by current operating system platforms. The Hybrid Workspaces Studio Packager lets you isolate applications in a self-contained package that can be run locally or in a secure workspace, increasing the lifespan of your applications while isolating the device from potential vulnerabilities.

If you aren't already using Hybrid Workspaces, try it for yourself. Access your free trial today!

If you are using Hybrid Workspaces, check out the enhancements and fixes in the latest release, version 24.7.

Hybrid Workspaces - Application Streaming Server
The 24.7 release retains the same Server version number as the previous Server release but includes an updated Turbo VM to match the one used in Studio. This update provides the latest VM fixes made in Studio to ensure consistent container execution for both components (Server and Studio). The release also includes a fix for the issue of the Server Admin pages failing to load due to a certificate error (typically seen when using self-signed certificates).


Hybrid Workspaces - Studio (Application Packaging Tool)
The update to Studio includes the following improvements and bug fixes:

  • Inclusion of the Public user directory in Capture
  • Detection of 32-bit Default Programs entries during Capture
  • Comprehensive directory inclusion in Capture
  • Accurate evaluation of indirect Windows Registry strings during Capture
  • Proper display of login dialog when necessary for Publish operations
  • Correct completion status for the XStudio Query Capture operation
  • Resolution of a crash when %TEMP% and the sandbox location are on different devices
  • Fix crash in Acrobat Pro due to insufficient support of duplicated handles across virtual processes
  • Fix crash in Adobe Photoshop and Epic Unreal Engine due to incorrect static dependency initialization
  • Fix error in Print Preview for applications based on the Chromium Sandbox v125+
  • Fix hang in Autodesk Maya 2024+ when enumerating merge isolated directories
  • Fix error in Microsoft VSCode when installing extensions due to incompatibility when renaming virtual directories that have files opened for write access
  • Fix Microsoft Project not being discovered during Microsoft Office 365 capture
  • Fix missed file objects during Capture
  • Fix precacheable flag not being set during Capture
  • Fix crash in Autodesk Maya when creating a node in Hypershade tool
  • Fix hang in Microsoft VSCode when exiting the application
  • Add ability to inherit clipboard isolation settings from any layer
  • Add comparison tool for WinDBG traces to Debugger
  • Fix incompatibility with BeyondTrust security software
  • Fix path mapping for relative paths for Windows Side-by-Side assemblies
  • Fix HttpPassthrough flag to allow ShellExecute of http(s) urls to access virtual filesystem and registry
  • Fix repair dialog in Microsoft Outlook 365
  • Fix Capture of certain registry key names in all capital letters
  • Fix bootstrap process crash when using standalone executables as auxiliary layers
  • Fix computation of sandbox temporary paths across multiple processes
  • Fix crash in Microsoft SQL Server prior to version 2016
  • Fix potential locale table corruption when using DLL Injection
  • Fix inconsistency with trailing slashes for directories from NtQueryInformationFile
  • Fix parsing of ProgID verb parameters that use quotation marks
  • Fix ProgID capture in Microsoft Office
  • Fix Metadata editor panel to update correctly
  • Fix saving startup file architecture
  • Fix errors caused from invalid hives defined in .reg file during registry import
  • Fix XStudio Merge command to create standalone executables for .exe output files
  • Add options to XStudio Merge command to control inheritance of metadata and startup files
  • Add support for file renaming during Capture
  • Add HideElevated runtime flag to prevent virtual processes from seeing that they are running with elevated privileges
  • Remove delete option from Debugger log tree root node
  • Allow modification of Debugger log normalization rules
  • Add context menu items in Debugger log view to truncate a file from current position
  • Add keyboard shortcut to delete logs in Debugger log view
  • Exclude "@APPDATACOMMON@\Turbo" folder from Capture
  • Exclude "Microsoft Update Health Tools" folder from Capture
  • Add Apply Configuration feature to XStudio
  • Add Studio and VM version metadata to built images
  • Add capture of file associations and URL associations for Default Programs
  • Fix access to tsclient mapped drives on Windows Server 2022
  • Fix loading and initialization of executable static dependencies
  • Fix COM object registration for Microsoft Outlook 365
  • Fix handling of CLSCTX_ACTIVATE_32_BIT_SERVER and CLSCTX_ACTIVATE_64_BIT_SERVER COM flags
  • Fix manifest dependency resolution when using wildcard architecture
  • Fix capture of ProgIDs and Verbs for improved file association handling
  • Fix XStudio to build an image based on the output file type (.svm or .exe)
  • Fix Debugger parsing of logs which use DLL injection launch mode
  • Fix Microsoft App-V package import of system binaries

For more information, please see the Hybrid Workspaces 24.7 documentation.

Labels:

Information Governance
Information Management