Turbo partners with Perinova in Germany and Switzerland

Turbo.net is pleased to announce a partnership with Perinova IT-Management GmbH of Germany.

Perinova will provide Turbo.net enterprise consulting and implementation services in Germany and Switzerland.

“Perinova has offered its clients consulting and support in the field of application virtualization for over 10 years. Perinova has years of experience working with Turbo technologies in third-party products. This new direct partnership strengthens our existing cooperation and offers our mutual customers in Germany and Switzerland access to Perinova’s unique experience and depth in Turbo containerization and application virtualization technologies.”

For more information on Perinova IT-Management, visit their web site at http://perinova.com.

If you are interested in joining the Turbo Partner Program, please contact partners@turbo.net.

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.

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.

Citrix Receiver Desktop Now in the Citrix Sandbox

In a previous article we introduced the Citrix Sandbox. At that time, the Citrix Sandbox contained the Citrix Receiver Web client, which runs the Receiver plugin within a browser.

We are happy to announce that the standalone Citrix Receiver is now also available in the Citrix Sandbox.

What is the Citrix Sandbox?

The Citrix Sandbox channel on Turbo.net lets you instantly run any version of Citrix Receiver.

Turbo allows multiple versions of Receiver to run side-by-side on the same desktop. This makes testing new versions of Receiver or deploying old versions to access legacy XenApp servers extremely easy.

New versions of Receiver are automatically added as they are released. The Turbo.net Citrix Sandbox works with all desktop and server versions of Windows. Turbo applications can be deployed to individual desktops and teams.

Visit the Citrix Sandbox now at https://turbo.net/citrix

Deploying Turbo Browser URL Redirection via Group Policy

The Turbo URL Redirector lets you automatically launch a specific containerized browser when a user accesses a specific web site. (Details of the Turbo URL Redirector were discussed in the article Automatic URL Redirection to Turbo Browsers.)

In this article, we explain how to deploy this great feature to users through Local Group Policy (GPO).

Before You Start

The Turbo URL Redirector is a native browser extension that assists in web navigation by processing clicked hyperlinks and URLs entered in the navigation bar. The extension can be configured to open specified domains using a browser available on Turbo.net or a local TurboServer.

The Turbo URL Redirector for Internet Explorer is implemented in the Turbo.net Browser Helper Object and supports IE versions 8, 9, 10 and 11. The Turbo.net Chrome Extension provides the same experience for users of Chrome 42 and above.

A step-by-step walkthrough of the Turbo URL Redirector for Internet Explorer was described in this article. If you are not sure how to configure URL redirections using the Turbo.net website, we encourage you to read the previous post before moving to the next section.

Enable Redirection

The Turbo URL Redirector is disabled by default, because its installation requires elevated permissions to copy IE Browser Helper binaries to %ProgramFiles(x86)%.

To enable the Turbo.net URL Redirector, execute the following command:

> turbo config --enable-redirector
Hub server: https://turbo.net/
Browser redirection is enabled

Enable the Turbo Browser Helper Object for All IE Users

Microsoft Internet Explorer can be configured for all users through Local Group Policy. This section explains how to specify the GPO to silently load and enable the Turbo.net Browser Helper Object. Depending on the policy settings the user may be allowed to disable the add-on afterwards.

First open the Local Group Policy Editor:

> gpedit.msc

Select the Add-on Management node under Computer Configuration/Administrative Templates/Windows Components/Internet Explorer/Security Features in the Local Computer Policy panel.


Double click Add-on List in the detailed view.

Select Enabled and click the Show button in the Options panel.

Add a new entry with Value name {DEC8F2AC-A81F-4BC9-A973-41EE4C4AF116} and Value 1. The Value name corresponds to the class identifier (CLSID) of the Browser Helper Object. The Value is a number indicating whether Internet Explorer should deny or allow the add-on to be loaded. Setting Value to 1 means that an add-on should be allowed. Enter a 2 to allow the add-on to be loaded and permit the user to manage the add-on through Add-on Manager. We recommend using 1 for most administration scenarios.


Click OK to save options and close the dialog.

Press the Apply button to update the policy settings and OK to close the dialog.

Launch the native IE to verify settings.

If the Turbo Sandbox Manager is not running you may see an Internet Explorer Security alert explaining the process will be opened outside of Protected mode. (Turbo Sandbox Manager is the service responsible for integration of Turbo applications with the Turbo.net website.) You can ignore this warning by checking Do not show me the warning for this program again and then clicking Allow.

Go to Tools (Alt + X) and open Manage Add-ons (M).


Turbo.net Browser Helper should be included in the list of currently loaded add-ons and be enabled. Note that actions to change the status of the Turbo.net Browser Helper are disabled.

Enable the Turbo.net Extension for All Chrome Users

Google Chrome configuration for all Windows domain users can also be defined using Local Group Policy. This section provides step-by-step instructions on adding the Turbo.net Extension to force-install extensions in Chrome. The extension will be installed silently, without user interaction and cannot be uninstalled by the user. All permissions requested by the extension will be granted implicitly, without user interaction.

As of this writing the Turbo.net Extension requires permissions to read and change all data on the visited websites and communicate with cooperating native applications. The extension supports Chrome 42 and above.

First, Download the IP archive with policy templates from the Chrome website.

(For more information about the policy templates and other supported configuration settings refer to the documentation for Chrome administrators.)

Unpack the archive to and install templates on the local machine by copying them to %SystemRoot%\PolicyDefinitions directory.

Copy .\policy_templates\windows\admx\chrome.admx to %SystemRoot%\PolicyDefinitions.

Copy .\policy_templates\windows\admx\locale\chrome.adml to the %SystemRoot%\PolicyDefinitions\locale directory, where the locale alias corresponds to the locale name (en-US for United States) of the Windows display language used on the host machine.

Run the Local Group Policy Editor:

> gpedit.msc

Select Extensions node under Computer Configuration/Administrative Templates/Google/Google Chrome in the Local Computer Policy panel.


Double click on the Configure the list of force-installed apps and extensions in the detailed view.

Select Enabled and click the Show button in the Options panel.

Add the following entry to the list of Extension/app ids and update URLs to be silently installed.


The first component is the Id of the Turbo.net Extension. The URL points to the standard Chrome Web Store update service.


Click OK to save options and close the dialog.

Press the Apply button to update the policy settings and OK to close the dialog.

To verify that local policy settings are applied correctly launch Google Chrome and go to chrome://extensions URL.


The Turbo.net Extension should be listed on the page with the Enabled checkbox set, but not available for user interaction and a badge informing that the extension was installed by enterprise policy.

The Local Group Policies presented in this article apply equally well to browsers launched with merge or write-copy isolation using Turbo:

> turbo try google/chrome --isolate=merge
> turbo try microsoft/ie --isolate=write-copy

For a list of all browsers available in Turbo.net, see the Browser Sandbox Channel. Customized web applications for browsing popular web sites such as Facebook, Twitter and WebEx are available in the TurboBrowsers repository. Remember that all Turbo browsers can be customized with specific plugins, IP and site blocking, and many other customizations.

Please share any comments or suggestions on this article with us at @turbohq!