Zero-Touch Client Deployment

The Turbo Update Service MSI installs the Turbo Client, configures it, and logs it in from properties you pass to msiexec. Your deployment tool runs one install and nothing further is required: no configuration script and no sentinel file to detect one.

msiexec /i TurboUpdateService.msi /qn ^
  HUB_URL="https://hub.company.com" ^
  CLIENT_API_KEY="<key>" ^
  CLIENT_CONFIG="--domain=https://hub.company.com --image-path=allusers --enable=AutoRegister" ^
  CLIENT_PULL="xvm,base" ^
  CLIENT_SUBSCRIBE="--all --pull"

Property	Description
HUB_URL	Base URL of your Turbo Hub, used to check for Turbo Client updates
CLIENT_API_KEY	API key the device logs in with. Create one with ts api-key or from the Administration site
CLIENT_CONFIG	Any arguments accepted by turbo config, applied for all users in the order given
CLIENT_PULL	Optional. Arguments for one turbo pull, typically the images to pre-stage (for example xvm,base)
CLIENT_SUBSCRIBE	Optional. Arguments for one turbo subscribe, typically --all --pull to subscribe the device to its workspaces
UPDATE_CHECK_PERIOD_MINUTES	Optional. How often the device checks for Turbo Client updates

HUB_URL and --domain are separate settings and both are needed: the first tells the update service where to fetch client updates from, the second tells the client which Hub to use.

Each CLIENT_CONFIG argument is applied on its own, so write settings in the --flag=value form. A value separated by a space is read as a second setting and will not take effect.

Once the MSI completes, the device installs the Turbo Client if it is not already present, applies each CLIENT_CONFIG argument for all users, logs in with CLIENT_API_KEY, and then runs the CLIENT_PULL and CLIENT_SUBSCRIBE commands, in that order. Everything runs in the background within a minute of the client being installed, and retries on its own if the Hub is unreachable at the time. Subscriptions are kept up to date from then on; the pull list is re-applied whenever you redeploy it with different values.

Rotating or correcting the key

Deploy the MSI again with the new values. The device notices the change and re-enrolls within a minute, without a reboot or a service restart. This is also how you recover from a key that was mistyped or has since been revoked.

Client Updates

The update service keeps the Turbo Client current from your Hub. Installing a client update closes running Turbo applications and the Turbo Launcher, deploys the new version, and restarts the client in each signed-in session. Interactive installs ask for confirmation first, and the Turbo Launcher warns users that installing closes their Turbo applications, both before they choose Install now and ahead of a mandatory update deadline. An update applied automatically at a deadline closes applications without further prompting, so set deadlines with your users' working hours in mind. No script needs to stop or restart Turbo processes around an upgrade.

If a process cannot be closed, the installer still completes and returns exit code 3010, the standard soft-reboot request, which deployment tools handle with their usual reboot behavior.

Deployment Tool Guides

• System Center (SCCM)
• Intune