Turbo Client and VM Updates, May 18

Users will be automatically updated to the latest version of Turbo Client and VM.

New and Improved

This update includes the following new features and improvements:

  • Turbo will attempt to encrypt data using the stronger TLS 1.2 protocol by default when configured with a secure hub.
  • Turbo Client always installs for the current user, even if Windows UAC is disabled. To install for all users, specify the --all-users flag.
  • Turbo performance has been improved on systems with Microsoft .NET 4.7.
  • The performance of the turbo logs command has been improved.
  • The turbo installi command creates Start Menu shortcuts with friendlier names.
  • Portable Application EXEs always use the VM version present at build time unless automatic updates are enabled.
  • The Firefox browser extension starts the Turbo Client when a user attempts to run an application from the Turbo.net website.
  • When executing turbo run with the --enable-sync flag, the container state will be pulled from the hub before starting.
  • The Visual C++ Redistributable 2008 layer is no longer a default dependency.

Bug Fixes

This update includes fixes for the following issues:

  • The Turbo Client uninstall process does not terminate running containers, which may result files that are not removed.
  • Synchronization operations are killed during Turbo Client updates, resulting in download failed errors.
  • The turbo fork command can cause an invalid state when used with installed containers.
  • The turbo subscribe command incorrectly marks new applications as updated.
  • The turbo containers and netstat commands print mapped ports in reverse order.
  • The turbo rmi -f command may fail with an “illegal characters in path” error.
  • Thr turbo run --ad-group-deny command blocks users who are not in the denied group.
  • The Turbo Launcher may crash due to a null pointer exception if a user logs out while a container is running.
  • Uninstalling the Turbo Launcher may leave a dead shortcut in the Start Menu.

Version Numbers

The component version numbers for this release are:

  • Turbo Client: 3.33.1538
  • Turbo VM: 11.8.1120.16

Turbo at Citrix Synergy in Orlando

Turbo.net will be hosting three events at Citrix Synergy in Orlando.

Whether you’re a container expert or just getting started, these briefings — one each for enterprise, higher ed, and the Citrix community — will bring you up to speed on the latest Turbo container technology for Citrix. We’ll also be previewing some exciting new developments.

And of course there’ll be drinks and food, an evening pool party, and networking with fellow Citrix professionals.

These invitation-only events are filling fast so contact your Turbo representative or DM us @turbohq soon if you’d like to attend.

Look forward to seeing you in Orlando!

 

New on Turbo.net in May

The following applications have been added or updated on Turbo.net for May:

Follow @turbobuild for up-to-the-minute updates, and send your requests to us at @turbohq.

Turbo Client and VM Updates, April 25

Users will be automatically updated to the latest version of Turbo Client and VM.

New and Improved

This update includes the following new features and improvements:

  • New! Add layers on the condition that a file or directory exists on the host system.
  • New! Portable Application EXEs work with the --startup-file and --isolate flags.

Bug Fixes

This update includes fixes for the following issues:

  • .NET Core fails to execute the dotnet run command due to a bug in the implementation of virtualized NT memory management.
  • Incorrect handling of the isolation for the FileExts registry key may cause a crash when an Open File dialog appears.
  • Portable applications built with the data synchronization option enabled fail to log in Turbo Hub Server when a non-default port is configured.
  • Data synchronization fails when the storage location path contains a backslash.
  • TurboLauncher fails to start an application from a Turbo Portal Server.

Version Numbers

The component version numbers for this release are:

  • Turbo Client: 3.33.1488.20
  • Turbo VM: 11.8.1120.13

TurboServer Update 17.0.493

TurboServer is an on-premise version of the Turbo.net Hub designed for enterprise environments.

The Turbo Server 17.0.493 update is now available at: turbo.net/server/download.

New and Improved

This update includes the following new features and improvements:

  • New! Support for Mozilla Firefox 50+ using the new extensions system.
  • Upgraded the Apache component to version 2.2.32.
  • A sample application is available by default when TurboServer is installed in Portal mode.

Bug Fixes

This update includes fixes for the following issues:

  • TurboServer does not update the Turbo Client component during an upgrade.
  • TurboServer does not allow anonymous users to launch containers past the trial expiration date.
  • TurboServer does not prompt the user to install Turbo Client when clicking on links that require it.
  • TurboServer creates a folder on the host system drive at C:\.

Version Numbers

The component version numbers for this release are:

  • Turbo Server: 17.0.493

Turbo Studio Update 17.0.886.13

Turbo Studio is an easy-to-use graphical editing tool for creating and editing Turbo  environments.

The Turbo Studio 17.0.8886.13 update is now available at: turbo.net/studio/download.

New and Improved

This update includes the following new features and improvements:

  • New! Build Portable Application EXEs with an on-premise Turbo Hub Server back-end in addition to the cloud-based Turbo.net Hub.
  • New! All official repositories from Turbo.net Hub are available to any user via the Template and Import application configuration wizards.
  • Improved! New isolation rules are applied when using the Template wizard to build ISV Application EXEs and Layers for Turbo Portal Server.
  • Image dependencies are packaged into ISV Application EXE outputs as well as applications pushed to Turbo Portal Server.
  • Temporary .XAPPL configuration backups are created when saving as a recovery option for data corruption.

Bug Fixes

This update includes fixes for the following issues:

  • Turbo Studio fails to communicate with the Turbo.net Hub when the Turbo Client has been logged in a Turbo Hub Server.
  • The mailto: protocol does not get captured correctly in a snapshot configuration.
  • Outputs are built with an incorrect file icon if a startup file is not defined in the configuration.
  • Turbo Studio ma fail to profile an application properly.
  • Turbo Studio may fail to harvest using the Microsoft Office 2010 recipe.
  • Turbo XStudio fails to import MSI installer files.

Version Numbers

The component version numbers for this release are:

  • Turbo Studio: 17.0.886.13
  • Turbo VM: 11.8.1120.8

Turbo Client and VM Updates, March 15

Users will be automatically updated to the latest version of Turbo Client and VM.

New and Improved

This update includes the following new features and improvements:

  • New! Isolate container processes with the IsolateProcessNames container VM setting. Example: turbo run --enable=IsolateProcessNames
  • New! Disable access to non-system drives (for example, everything other than C:\) with the IsolateNonSystemDrives container VM setting
  • New! Disable access to network file shares with the IsolateNetworkShares VM setting
  • New! Build Portable Application EXEs that use a private self-hosted Turbo Hub Server instead of the Turbo.net Hub
  • Improved! Optimized synchronization performance and memory usage
  • Synchronization process works properly through proxies when a self-signed certificate in the Windows certificate store is used
  • User interface improvements

Bug Fixes

This update includes fixes for the following issues:

  • The Firefox browser extension does not work if the Turbo.net client is installed for all users.
  • Applications launched via the Turbo.net browser extension may fail to start when many users are logged on the operating system at the same time.
  • Network route blocking does not block specified hostnames when using a proxy server.
  • Portable applications built with the data synchronization option enabled fail to start with a login error.
  • The turbo netstat command fails to find the specified container.
  • TurboPlay fails to load application models from the local filesystem or network share.

Version Numbers

The component version numbers for this release are:

  • Turbo Client: 3.33.1488.10
  • Turbo VM: 11.8.1120.8

New on Turbo.net in March

The following applications have been added or updated on Turbo.net for March:

Follow @turbobuild for up-to-the-minute updates, and send your requests to us at @turbohq.