Integration Tools

Integration Tools

Turbo has tools to enhance the deployment process and integrate containerized applications with existing deployment tools. For example, Browser Redirector enables administrators to automatically direct users to a supported browser based on a URL that is entered. This solves compatibility issues for organizations that have legacy web applications that rely on non-standard browser configurations.

Another integration tool, SpoonReg, provides a way to register the virtual applications to the Windows shell and create file associations and desktop shortcuts.

Browser Redirector

Browser redirection is a service that automatically opens the page or resource a user is trying to visit in an alternate browser. It uses a browser plugin to check URLs against a list of administrator defined rules that specify which websites or web applications are incompatible with the user's current browser. If the URL matches a rule, the web page will launch in the specified virtual browser instead of their installed browser.

Browser redirection prevents errors when accessing legacy web resources on newer systems, creating a more seamless and efficient web experience for the end user.


Browser Redirector is included in the Turbo client, but requires a command line switch on install to be enabled. Unlike the standard install, the Browser Redirector requires administrator rights during install.

From and elevated command prompt, run the following command:

turbo-client.exe /redirect /allusers

Silent installation is available using the silent command line flag. Also, for environments where the console should be hidden, there is a hidegui command line flag available.

turbo-client.exe /redirect /allusers /hidegui /silent

Note that the deploying using the SYSTEM account is not supported.

Setting up Redirection Rules

After completing the client install, administrators define a set of rules that will determine which websites should redirect to a specific browser.

These rules are defined in the registry so that they may be deployed efficiently via group policy.

Registry-based rules are located under HKLM\Software\Wow6432Node\Code Systems\Turbo in a key called Redirector. The Redirector key will contain a list of keys. Each key represents a rule, and the name of the key is the URL pattern match for the rule. Under each rule key, there will be a value of TurboCommand or Command which will define what happens when the URL matches the pattern.

For example, if you wanted to route all users to Firefox version 35 when they went to Google, the key name would be and the TurboCommand value would be new firefox:35.

There is an optional value AutoReturn that can be used if the user should be redirected to a host browser if they navigate to a URL that does not match the rule pattern.

This screenshot shows a fully set up rule key for a TurboCommand rule.

This screenshot shows a fully set up rule key for a Command rule.

Additional Information

Applications on a Network Share

When a virtual browser is located on a network location or anywhere not on the user's hard drive, the user may be prompted with a security warning before the browser is launched. The user must then manually select "Run" the application before the browser launches.

The warning can be suppressed by setting the environment variable SEE_MASK_NOZONECHECKS to 1.


SpoonReg is a tool that provides a command-line interface for deploying containers and managing the virtual desktop environment. Users and administrators can use SpoonReg to register containers for a single user or, in the case of administrators, a group of users or devices. SpoonReg can be used to deploy and manage containers and layers built using Turbo Studio.

After containerizing an application with Turbo Studio, you can make the Start Menu icons, shortcuts, and file associations available on a user's desktop. SpoonReg enables you to register Turbo containers in the shell, creating associations that generally are created during a standard installation process. Unlike an installation, registration and un-registration are performed instantaneously.

SpoonReg also enables you to create, reset, and remove application sandboxes: virtual environment "bubbles" where containerized applications reside. Sandbox management provides control over application linking and intercommunication.

Turbo Server users and administrators can use SpoonReg to register applications to the desktop. For specialized deployment scenarios, contact your Turbo representative to learn how to obtain your own version of the SpoonReg.exe utility.

Command-Line Syntax

The following table lists the different naming conventions used with SpoonReg:

Parameter Description
AppSpec Path (relative or fully-qualified) to a virtual executable or layer built with Turbo Studio
SandboxSpec Name or path of a virtual sandbox

Registering a container

To register an application, use the following command:

SpoonReg.exe AppSpec

This command creates all Start Menu items, Desktop shortcuts and file associations used with the container executable. By default, registration creates a local cached copy of the container executable and uses the local profile as the sandbox location.

Note: The sandbox location specified during the container build is ignored when registering applications using the SpoonReg tool.

Advanced Registration Options

Command-line parameters control caching behavior and sandbox where the container should be registered:

SpoonReg.exe [Options] AppSpec[@SandboxSpec]
Parameter Behavior
/nocache The container executable will not be copied to a client machine. All shortcuts and file associations point to the full path as given by AppSpec.
/id {00000000-0000-0000-0000-000000000000} Specify the internal guid used to uniquely identify the application. There are no published uses for this value today.
SandboxSpec Name and path to an existing sandbox. If this parameter is specified and a sandbox with that name exists, the application will register into that sandbox.

Updating Registration Settings

Application registration settings can be changed by re-executing the registration command with the desired options:

SpoonReg.exe [Option] AppSpec[@SandboxSpec]
Parameter Behavior
/nocache The container executable will not be copied to a client machine. All shortcuts and file associations point to the full path as given by AppSpec.
/cache Enable caching of the specified application (reverses the /nocache setting)

Un-registering a Container

Un-registering a container reverses the registration process, removing the container, Start Menu icons, shortcuts, and file associations.

To un-register a container, use the following command:

SpoonReg.exe /unregister AppSpec[@SandboxSpec]

You can also un-register all applications with the single command:

SpoonReg.exe /unregisterall

Questions? Projects? Talk to us.