Turbo Client

Turbo Client

Turbo Client Installation

The latest Turbo Client may be downloaded from https://turbo.net/download.

Installing Turbo Client for a Single User

To install the Turbo Client using default settings, double-click on the installer. This will configure the client for the current user and place the client components in the %LOCALAPPDATA%\Turbo user directory. Shortcuts will be added to the Start Menu in the Turbo.net folder for quick access to the TurboLauncher and TurboShell. In addition, shortcuts will be added to the Startup folder to automatically start the Turbo Client.

The Turbo.net Extension is required when using the client with the Chrome browser. It may be found in the Chrome Web Store at [https://chrome.google.com/webstore/detail/turbonet-extension/ldibmiofagdkgiphkcokpooepankmacl] (https://chrome.google.com/webstore/detail/turbonet-extension/ldibmiofagdkgiphkcokpooepankmacl).

Installing Turbo Client for All Users

The Turbo Client can be installed for all users on the machine with the --all-users flag, which will place the client components in the %PROGRAMFILES(x86)%\turbo directory and register the shortcuts for all users on the system.

Note that if users on the machine already have the Turbo Client installed in their user directories, then their single user installs will be overriden by the all user install. Additional updates to the Turbo Client will occur for the all users installation even if the --all-users flag is omitted.

For all user installs in environments using the Chrome browser, the Turbo.net Extension may be enabled via group policy. See the [Enable the Turbo.net Extension for All Chrome Users] (https://blog.turbo.net/deploying-turbo-browser-url-redirection-via-group-policy/) section on the Turbo.net Blog.

Turbo Client Unattended Installation

Pass the --silent flag to the client installer to suppress the UI popups that may block unattended installs.

Turbo Client Installer Flags

Running the Turbo Client installer with these command line flags can change the install behavior.

Flag

Behavior

--app-server

Installs client and provisions the server to be used as an Application Server in an onpremise streaming pool.

--all-users

Installs the Turbo Client to %PROGRAMFILES(x86)%\turbo so that it is accessible for all users on the machine. This is required for running certain Turbo command for all users (such as `subscribe` or `installi`)

--hide-gui

Disables the Turbo Launcher from being visible.

--no-auto-start

Stops the Turbo Launcher from starting when logging into your machine.

--no-auto-update

Disables the check to see if new versions of the client are available.

--no-redirector

Doesn't install the Turbo Redirector Internet Explorer plugin when installing for all users.

--no-shell-ext

Disables the Turbo Launcher from being visible.

--server

Sets the default server for Client component login. This is used in environments with Turbo Server.

--shutdown-period

Specifies the number of minutes that the Turbo Sandbox Manager is idle before shutting down.

--silent

Turbo Client installs without any UI popups.

Uninstalling the Turbo Client

Uninstalling Turbo Client via Control Panel

You can uninstall the Turbo Client or the TurboLauncher specifically from the Windows Uninstall or change a program screen (previously called Add/Remove Programs).

Uninstalling Turbo Client via the Command Line

To uninstall the Turbo.net Sandbox Manager, you may pass the /uninstall flag to the Turbo-Sandbox.exe in the %LOCALAPPDATA%\turbo[client-version] directory for single user installs or %PROGRAMFILES(x86)%\turbo[client-version] for all user installs.

# Uninstall for single user
C:\> "%LOCALAPPDATA%\Turbo\[client-version]\Turbo-Sandbox.exe" /uninstall /silent

# Uninstall for all users
C:\> "C:\Program Files (x86)\Turbo\[client-version]\Turbo-Sandbox.exe" /uninstall /silent

For unattended or scripted uninstalls, pass the /silent flag in addition.

Note that if the client is installed for all users, you would have to run from an elevated command prompt or the command will fail with insufficient privileges.

Turbo-Sandbox.exe Uninstall Flags

Pass the following flags to the Turbo-Sandbox.exe to uninstall specific components or the whole Turbo Client.

Parameter

Behavior

/uninstall

Uninstalls the Turbo Client. Close all web browsers before uninstalling.

/silent

Used with /uninstall to perform a silent uninstall.

/delete-user-data

Used with /uninstall and /silent to remove user container data during uninstall.

/uninstall-launcher

Uninstalls the TurboLauncher but leaves the rest of the client.

/uninstall-redirector

Uninstalls the TurboRedirector but leaves the rest of the client.

### Turbo Client Security

There are several ways to control how containers can be run on your machine.

Trusted Sources

Trusted sources control which hub locations are allowed to have containers be started from web locations. By default, only https://turbo.net is trusted. A new hub can be added to the list with turbo config --add-trusted-source=[hub-authority].

Any untrusted hub will result in a warning dialog that will ask the user if the container execution is desired. The user will have the option to trust future containers from the location.

A hub location can also be blocked which will prevent users from executing containers from those locations. A hub source can be blocked with turbo config --block-trusted-source=[hub-authority].

The trusted sources can be set for all users on the machine with the --all-users flag. These will either set the defaults or the overrides depending on how the shared settings are configured.

# view current trusted sources
> turbo config
Hub server: https://turbo.net/
Turbo Drive is enabled (mounted as a T: drive)
Trusted Hub Sources:
  turbo.net
  
# add a trusted hub
> turbo config --add-trusted-source=my-hub.com
Hub server: https://turbo.net/
Turbo Drive is enabled (mounted as a T: drive)
Trusted Hub Sources:
  turbo.net
  my-hub.com
  
# block a hub
> turbo config --block-trusted-source=dangerous-hub.net
Hub server: https://turbo.net/
Turbo Drive is enabled (mounted as a T: drive)
Trusted Hub Sources:
  turbo.net
  my-hub.com
Blocked Hub Sources:
  dangerous-hub.net

Local Resource Requests

Containers which are executed remotely may require access to local resources (such as local network). If the container requires access but is not allowed globally then a security dialog will be shown to request permission.

To allow access to the local network automatically, use turbo config --enable=LocalNetworkAccess.

Talk to us.