Dropbox now on Turbo Drive!

Turbo is pleased to announce support for Dropbox in Turbo Drive!

The T: drive connects cloud storage services directly to Turbo applications. The T: drive works across all supported clients and does not require the Dropbox client.

To connect Dropbox, select Dropbox from the Connect dropdown on the Files tab.

Both Dropbox and OneDrive paths can be connected to a single Turbo account or workspace. Turbo also supports connection of multiple folders from a single storage service to a single Turbo workspace.

Turbo has many powerful storage customization capabilities for virtualized apps. And we’re here to help your organization use them to create the perfect storage environment for your users.

Contact us about advanced storage configuration

Security Update: TLS 1.0 and 1.1 Disabled on Turbo.net

Today we have removed support for TLS 1.0 and 1.1 for HTTPS connections to Turbo.net. TLS 1.2 is now required to use Turbo.net.

As a result, the minimum supported browser versions are now:

  • Apple Safari 7
  • Google Chrome 30
  • Microsoft Internet Explorer 11
  • Mozilla Firefox 27
  • Opera 17

This update improves the security of Turbo.net.

Note that Turbo continues to support executing earlier browser versions within Turbo containers.

Browser Sandbox now available on Mac!

We are pleased to announce the availability of Mac and cloud execution support in the Turbo.net Browser Sandbox.

The new Browser Sandbox can run containerized browsers in the cloud via an HTML5 interface that runs on any device with an HTML5-enabled web browser.

Try the new Browser Sandbox now at http://turbo.net/browsers.

You can also run browsers on your local desktop when using a compatible Windows device. Turbo.net automatically synchronizes containers between desktops and the cloud so your applications are available anywhere.

Local or Cloud

Turbo.net will automatically select the best execution option (Local or Cloud) based on your device type. To manually select an execution mode, click on the arrow on the Run button to expand run options and select the preferred execution mode.


More Browsers

The Turbo.net Browser Sandbox now provides all versions of major browsers including Internet Explorer, Chrome, Firefox.

Chrome and Firefox images are automatically updated as new updates are released. Every legacy version is available for execution on demand.

Browsers can be configured with any combination of plugins and runtimes, including Java, .NET, Flash, and Silverlight.

Browser Sandbox also includes nightly Chrome Canary and Firefox Nightly builds and Firefox Mobile. Containerized browsers are a easy and safe way to test and develop against non-production builds of Chrome and Firefox.


A set of popular browsers are available free to use for evaluation purposes.

Turbo.net Pro subscribers can use the new cloud functionality at no additional charge for session lengths up to 10 minutes. (Additional cloud session time available separately.)

The Turbo.net Pro subscription is just $9.95 per month and includes the ability to create customized browsers and applications, run containerized servers, use Turbo Studio, and much more.

Upgrade to Turbo.net Pro Now

We hope you enjoy this major upgrade to the Browser Sandbox!
-- The Turbo Team

Turbo Studio 17 Now Available

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

The latest version of Turbo Studio includes direct integration with the Turbo.net Hub, an installer based wizard alternative to snapshots, the ability to create portable container (single EXE) outputs, new subscription-based licensing, as well as support for the latest Windows operating systems.

Turbo Studio 17 is available now at: turbo.net/studio/download.

New and Improved

This update includes the following new features and improvements:

  • New! Studio 17 directly integrates with the Turbo.net Hub. Templates and import wizards are automatically updated with continuously updated Hub content.
  • New! New Portable Applications (.exe) output mode generates portable containers with Turbo Client embedded, all in a single EXE.
  • New! Create applications by installing the application (MSI or EXE) into a container console. This alternative to the snapshot process does not require a clean operating system and does not dirty up the host filesystem or registry.
  • New! Support added for Windows 10 “Redstone 2” pre-release versions.
  • Studio available in MSI format and scriptable legacy XStudio command-line tool.
  • Ability to configure the Minimum OS Requirement for images.
  • Internal Turbo VM version has been updated to 11.8.1060.

Bug Fixes

This update includes fixes for the following issues:

  • Projects containing dependencies on the Turbo.hub Hub fail to build.
  • Containerized ProgIds are not fully isolated.
  • Renaming a folder incorrectly fails with a message that the resource is used by another process.
  • Failure to deinitialize and flush streams may cause missing file writes in specific scenarios.
  • Virtualized applications can crash if started from multiple paths.
  • Product version is not set correctly when the metadata field is set to inherit from the startup file.
  • Trailing spaces are trimmed incorrectly for file paths with arguments.
  • The command-line XStudio.exe tool does not recognize some encodings for the license file.
  • An error may occur pushing a XAPPL configuration with a service to the local repository or the Turbo.net Hub.
  • Many user interface fixes and improvements.

Version Numbers

The component version numbers for this release are:

  • Turbo Studio: 17.0.794.0
  • Turbo VM: 11.8.1060

Getting Turbo Studio 17

Turbo Studio 17 is available for download at turbo.net/studio/download.

Any Turbo.net user with a Pro subscription can use Turbo Studio 17 by signing in with their account. Studio may be used in a limited fashion by Free users for evaluation purposes.

The ISV upgrade to Turbo Studio 17 is available for free to all licensed users of previous versions of Studio on active maintenance. For commercial users of previous versions, a new license key is available from the account management page of your Turbo.net account.

We hope you enjoy Turbo Studio 17!

Tour: Containerizing .NET, Java, and ASP.NET applications

Tour: Subscribing a XenApp farm to Turbo.net

Need to subscribe an entire XenApp farm to a set of containerized applications?

Turbo.net now provides tools to automatically push Turbo channels to XenApp servers, including making necessary updates to the XenApp configuration. Turbo.net’s Citrix tools support XenApp 6.5 and forward.

Step-by-step instructions for the xa7-subscribe and xa6-subscribe tools have been added to the Turbo Citrix tour:


From Zero to Containers in 90 Minutes

The new Turbo Walkthrough takes you from zero to proficiency in core container concepts in 90 minutes.

Start your container experience now at: turbo.net/tour

You can follow along with the Turbo Walkthrough with any modern desktop or server version of Windows, including Windows 7, 8, or 10; and Server 2008 R2, 2012, or 2016.

Stay tuned as we continue to add new topics over the coming weeks. Want to see more on a specific topic? Tweet to us at @turbohq.

Dublin Turbo Containers Talk

Video from Claudio Rodrigues’s talk Introduction to Turbo Containers is now available on YouTube.

Claudio will also be giving this presentation again at future E2EVC events.

You can send feedback on this talk to Claudio at @crod.

Improved Error Handling in TurboScript

Turbo.net provides thousands of images ready to go in the Turbo.net Hub. But if one of those doesn’t do the trick, TurboScript is a great way to create your own images.

In the past, TurboScript error messages were often confusing, leaving you clueless about the cause. A script may look correct but gives a parse error when executed, with no further information.

For example, could you have spotted what’s wrong in this example?

Useless Error Message
Here is another example. What equal sign is wrong and why?


The latest Turbo Client now provides much more explanatory help text for any failed command, including inline information and suggestions. Let’s retry the above examples with the newest clients.

First example: Aha, the import command needs a type specified!


Second example: Looks like the hosts command doesn’t need a equal sign:



The newest Turbo Client including error handling updates is now available on Turbo.net. If you already have Turbo installed you will be automatically upgraded within 72 hours. Enjoy!

Running Containers as Different Domain Users

By default Turbo containers will run in the security context of the user executing the turbo command. But what if we need to run as a different user?

In this example, let’s run SQL Server Management Studio as a different domain user than the currently logged in user.  In our scenario we have the Turbo Sandbox Manager installed in the local profile, which is the default behavior.

Our first attempt is to just use the runas command to execute the command turbo run ssms2012:

> runas /user:user@domain "turbo run ssms2012"
Enter the password for user@domain:
Attempting to start turbo run ssms2012 as user "user@doamin" ...
RUNAS ERROR: Unable to run - turbo run ssms2012
5: Access is denied.

Unfortunately with the Turbo Sandbox Manager installed in my local profile I cannot use runas to run SSMS in the user context I want since it does not have access to that user’s profile!

One workaround then is to install Turbo for all users via MSI and then use runas:

> runas /user:user@domain "turbo run ssms2012"

This works well — except we may not want to reinstall the plugin, or may not want to install it for all users.

We can solve this by using runas with the /netonly flag:

> runas /netonly /user:user@domain "turbo run ssms2012"

The /netonly flag forces the application to use the runas account for remote resources and the logged in account for local resources.