Deploying Trikker on multiple devices

Trikker is a normal Windows Installer (MSI) package, so you can deploy it like any other Windows software.

Any tool that can run an MSI silently already works: Microsoft Intune, System Center Configuration Manager (SCCM/ConfigMgr), Group Policy, PDQ Deploy, NinjaOne, and others. This guide walks IT administrators through packaging the installer, running a silent install, and setting up license activation without user interaction.

Before you start

Windows devices under your management: enrolled in Intune, joined to a domain with Group Policy, or managed by another deployment tool.
The Trikker offline installer, so the install needs no extra downloads.
A Trikker license: a regular license (one code per device), an educational license (one code for an unlimited number of devices), or a license with the remote or terminal server (RDS) option.
Outbound HTTPS access to the Trikker license server on every managed device. Don't block that traffic in your firewall or proxy.

1Get the installer

Download the offline installer at trikker.be/offline-version-windows. Use the offline version, not the smaller web version, for an unattended rollout: it needs no extra downloads during setup.

The download is a zip file with a setup.exe bootstrapper and the actual installer, Trikker_V.msi.

Most deployment tools need no packaging step at all: point them at Trikker_V.msi and run it with the silent command below. Do you use Microsoft Intune? It has one extra, recommended option, see "Packaging for Microsoft Intune" further down.

2Run a silent install

The MSI carries two public properties for an unattended install. Property names are case-sensitive, so keep them in capitals:

Property	Effect
`NOTHANKYOU=1`	Skips the closing thank-you webpage. That page opens through a custom action, so /qn alone doesn't suppress it.
`TARGETDIR`	The install folder.

msiexec /i Trikker_V.msi /qn NOTHANKYOU=1 TARGETDIR="C:\Program Files\Bluebits\Trikker"

For a detection rule in your deployment tool, use the MSI product code or the file version of the installed Trikker.exe.

3How license activation works

A Trikker license activates per device. On first activation, Trikker binds the license code to that device and confirms it online at every start afterwards; a short offline period stays covered by the last confirmed activation. That means you can't copy one ready-made license file to every device in the fleet.

Two license types work differently: an educational license activates with the same code on an unlimited number of devices, and a regular license activates once per device, each with its own code, from the Extra tab in Trikker.

A license with the remote or terminal server (RDS) option works differently again: the same code can log in from several sessions on the remote machine, but only for the number of devices registered with us in advance for that license. Running out of room resets the same way as a regular license: remove a device from the license in the license portal. This is specific to an RDS license; it doesn't apply to a regular or educational one.

4Provision the license without user interaction

Put the license code in a plain text file that contains only the code, name it exactly Trikker.V1.License.triklic (no other name), and place it in the license folder with your deployment script: %APPDATA%\Bluebits\Trikker\. Trikker picks up that file automatically at the next startup and activates it online.

This file works without any deployment tool as well: hand a single .triklic file straight to one user (by e-mail, a shared drive, or a USB stick), and it activates the moment Trikker finds it in the license folder or opens it as the first argument.

Note. A device can already hold an older activation. Trikker checks a saved lease first, so a new .triklic file doesn't take effect right away. Let your script delete any *.triklease files in the same folder before it drops the new .triklic file, and Trikker activates the new license at the next start.

5Launch with a file argument

Trikker reads only the first command-line argument, and it's always a file path. There are no separate switches.

Bluebits.Trikker.exe "C:\path\drawing.trik"
Bluebits.Trikker.exe "C:\path\Trikker.V1.License.triklic"

A .triklease file (bound to one device) also works as the first argument. It has no file association of its own, so pass it explicitly. Use it for targeted provisioning of a single machine, not for the whole fleet.

6Packaging for Microsoft Intune

Package Trikker_V.msi, not setup.exe, as a Win32 app with the Microsoft Win32 Content Prep Tool (IntuneWinAppUtil). Assign the app in system context, with a detection rule on the installed version or the MSI product code.

Use this as the install command in the Win32 app wizard, the same silent command as in step 2:

msiexec /i Trikker_V.msi /qn NOTHANKYOU=1 TARGETDIR="C:\Program Files\Bluebits\Trikker"

And this as the uninstall command:

msiexec /x Trikker_V.msi /qn

Add the .NET 10 Desktop Runtime as a separate Intune dependency: the MSI doesn't install it on its own.

7Verify the rollout

Installation: check the installed version, or the MSI product code, in your deployment tool's device status.
Activation: start Trikker on a sample device and check the license status on the Extra tab.
Network: keep the HTTPS connection to the license server open. A blocked connection stops the lease from renewing once the offline period runs out.

Need help?

Something not matching your setup? Get in touch through our helpdesk or at info@trikker.be, and let us know how many devices you're rolling out, which license type you use (regular, RDS, or educational), and which deployment tool you use.