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

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 Turbo Server.

The Turbo URL Redirector for Internet Explorer is implemented in the Turbo.net Browser Helper Object (Turbo-IEBrowserHelper.dll or Turbo-IEBrowserHelper-x64.dll depending on the processor architecture of the host machine) and supports IE versions 8, 9, 10 and 11. The Turbo.net Extension provides the same experience for users of Chrome 42 and above. To try the Turbo URL Redirector feature for yourself, follow this step-by-step guide.

Enabling Turbo URL 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 URL Redirector, execute the following command:

> turbo config --enable-redirector
Hub server: https://turbo.net/
Browser redirection is enabled
Enabling Turbo URL Redirection in Internet Explorer

Launch Internet Explorer.

You may see an Internet Explorer Security alert explaining that the Turbo Sandbox Manager will be opened outside of Protected mode. (Turbo Sandbox Manager is the service responsible for integration of Turbo applications with the Turbo.net website.) 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 Manage add-ons (M).

The Turbo.net Browser Helper will be displayed in the list of currently loaded add-ons. Change the status of the add-on to Enabled if required and close the dialog.

Enabling Turbo URL Redirection in Chrome

Install and enable the Turbo.net Extension.

For information how to enable the extension for all users see Deploying Turbo URL Redirection via Group Policy.

Defining Redirection Rules in Turbo.net

Sign in to the Turbo.net website and go to the Home tab.

Filter the Web category using the list on the right.

Select the Facebook app and press Install.

Go back to the Home tab and click Customize to display the Settings dialog.

Look at the URL Redirections section.

The Facebook application defines a default redirection for the facebook.com domain.

(Administrators can define custom browsers and redirection URLs from the Settings menu for other web sites.)

Close the Settings dialog.

Go to www.facebook.com using navigation bar in the native browser or press the hyperlink.

The Turbo URL Redirector will display a notification explaining that the domain will be opened in a separate window and the Facebook app will open in a few moments.

Defining Redirection Rules in the Windows Registry

Redirection rules can also be set in the Windows registry in cases where Turbo.net subscriptions are not used.

Rules are added to the "HKLM\Software\Code Systems\Turbo\Redirector" hive ("HKLM\Software\Wow6432node\Code Systems\Turbo\Redirector" for 64-bit operating systems).

Create a key under the Redirector hive, setting the name of the new key to the url pattern to match. In the example above, the pattern is "yahoo.com" which matches any url that contains "yahoo.com".

Within the new rule key, registry values are used to describe the command to execute if a url is encountered which matches the pattern. There are two ways to describe the redirection response, with Command or TurboCommand string values. A Command value is set to the full path to the command to execute. In the example above, the command is set to "c:\turbo\ie8-win10.exe". A TurboCommand value is set to the command to execute via turbo.exe. An example value would be "run ie8" which would execute "turbo.exe run ie8". For either of these command types, the url which matched the pattern is appeneded to the end of the command to be passed as a parameter.

Deploying Turbo URL Redirection via Group Policy

This section explains how to enable the Turbo URL Redirector for all users of Internet Explorer and Chrome.

Before following the step-by-step guide for each browser ensure that the Turbo URL Redirector is enabled.

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

If the browser redirection feature is disabled, see enabling Turbo URL Redirection.

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.

ldibmiofagdkgiphkcokpooepankmacl;https://clients2.google.com/service/update2/crx

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

SpoonReg

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.