The latest updates to Turbo for PC and Turbo for Mac include significant performance improvements, end user control over cached application images, new management configuration options, improved cache management, and more.
Turbo for PC and Turbo for Mac will automatically update unless otherwise specified by your administrator.
New and Improved
This update includes the following new features and improvements:
- Improved! Session startup performance is now significantly faster.
- New! Locally cached application images can be viewed and removed by end users using the Manage Cache dialog.
- New! Turbo for PC uses garbage collection to remove files that are no longer used, such as sandboxes associated with old client versions.
- New! Automatic garbage collection for unused application images can be turned on using the turbo config --gci-interval command. Garbage collection will periodically check for images that have not been used in 30 days.
- The maximum size of the local image repository can be set via turbo config --image-cache-size.
- Application sources may be marked as trusted or blocked from the command line via turbo config --add-trusted-source|--block-trusted-source|--remove-trusted-source=[source]. See Turbo Client Security.
- Access to the local network from cloud applications may be enabled or disabled via turbo config --enable|--disable=localnetworkaccess.
- New turbo commit --working-dir=current-dir option sets the working directory of the committed image to use the active directory when the session is launched.
- New --no-auto-update installation flag for Turbo for PC disables automatic updates. Previously this option was included only as part of the standalone install process.
- Turbo for PC installation flags may now be passed to the MSI install package.
- The turbo installi and install commands will use the Start Menu icons, desktop shortcuts, file associations, and protocol handlers defined in the image configuration for desktop integration by default. Desktop integration options can be selectively disabled via new flags in the turbo installi command.
- The --offline flag has been added to the turbo installi command to disable querying the hub for VM and image updates and other network calls.
- The turbo install command now accepts the same execution parameters as turbo run.
- The --all-users flag can now be used with the turbo import and pull commands to save the image in the All Users image cache.
- The --no-run and --install flags are now available in the turbo new command.
- Logging for garbage collection and other Turbo Client events has been improved.
- Application launch and login failures now include more detailed error messages.
- Turbo for Mac has been updated to support ADFS2 clients.
This update includes fixes for the following issues:
- The turbo installi and install commands overwrite existing shortcuts. The behavior has been modified to add numbered shortcuts on subsequent installs.
- The turbo run command overwrites the local image with the hub image if the image name is identical.
- The turbo commit command applies incorrect file permissions when the image path is set to All Users.
- The turbo installi and install commands can generate incorrect shortcuts, icons, and file associations used for desktop integration if multiple images are specified in the container.
- Launch configurations are not re-downloaded if the local cache becomes corrupted.
- The Run in Cloud option fails when logging into an on-premises portal after previously logging into the Turbo.net Hub.
- The Control Panel Programs and Features entry may not be properly removed when the Turbo Client is upgraded.
- Turbo for PC does not clear the Username field on the Sign In dialog when using ADFS-based Single Sign-On.
- Turbo for PC crashes when the Server field on the Sign In dialog is cleared.
- Turbo for PC is unable to sign in using anonymous authentication.
- Turbo for PC window height may be too large when undocked from the desktop edge.
- Turbo for PC does not display Favorites in the application list when connected to a legacy Portal Server.
- Portable applications packaged with the Turbo Client are not compatible with legacy Hub Server 18.
- Turbo for Mac can fail to authenticate against certain Single Sign-On services.
The component version numbers for this release are:
- Turbo for PC: 19.4.1964.21
- Turbo for Mac: 19.5