Skip to main content

Connector and Devices

The SmartTech connector is the service installed at the client that runs the diagnostic reads and the approved fixes. Devices without a connector (servers, network gear) are reached by jump from a designated machine.

SmartTech's Devices section holds:

PageContent
DevicesFleet figures: devices online, never seen, connectors behind the expected version, active tokens
InventoryClient workstations, servers and network gear
TokensEnrollment tokens, their use and their revocation
ProfilesDevice profiles for generic SSH equipment
DownloadsPublished connectors and install instructions

Enrollment Token​

A connector only enrolls with a token for the target client. To create one, pick the client, then generate a token:

FieldDescription
LabelToken name
KindSingle machine, or Deployment (several machines)
Number of usesHow many machines the token can enroll
Expires in (days)Token validity

Important: the token is shown only once. Copy it before closing the window.

Revoke a leaked token from the Tokens page: it can no longer enroll a machine, and machines already enrolled are not affected.

Installing the Windows Connector​

Download the installer from Devices → Downloads. The page shows the published version and the exact commands to copy.

Interactive Install​

Started by double-click, the installer asks for the token in a window. It rejects anything not starting with stk_.

Silent Install from an RMM​

Under the SYSTEM account, the token may be passed as a parameter:

<installer>.exe /S /TOKEN=<token>

Security: never from an administrator session. A process command line is readable through WMI, including by a standard user of the host.

The command runs the installer under the name shown: deploy it under this name, without renaming it.

Install by an Administrator​

The token goes through a file readable only by SYSTEM and administrators. The installer reads it, then deletes it.

<installer>.exe /S /TOKENFILE=C:\path\token.txt

/TOKEN= and /TOKENFILE= together are rejected.

Domain Controller​

Installing on a domain controller is supported since version 2.10.1. The connector reads the Application and System logs there, not the Security log.

Installing the Linux Connector (Preview)​

The Linux connector is a headless service for a server or jump host: SSH jump to network devices and system reads. It has no consent prompt, no user-data reads and no tamper protection. It requires Node 22 or later.

tar -xzf <archive>.tar.gz
sudo ./install.sh --env <environment> --token-file <file>

The token is never passed as an argument: it is read from a file, deleted after enrollment. The --token option prints a warning, because it exposes the token to other local accounts.

Service logs:

journalctl -u smarttech-connector -f

Devices Without a Connector​

A device without a connector is reached by jump from a machine of the same client designated as a jump host (device page, jump host option).

Click Add a device and choose:

TypeProtocolExamples
WindowsWinRM (PowerShell)Windows servers
LinuxSSH (bash)Linux servers
Generic SSHSSH, profile commandsRouter, firewall, NAS, hypervisor

The device can be picked from SmartDoc (the linked client's devices) or entered by hand: name, address, port, jump host and SmartDoc credential (the password stays in SmartDoc and is never shown in SmartTech).

When it is added, a first contact establishes the SSH host key, without which the first command would fail.

Device Profiles​

A profile lists the read commands allowed on generic SSH equipment, character for character. Starter templates are copied from Devices → Profiles; organization profiles are edited in place.

The profile tells the agent what to read on this kind of device. It grants nothing more: every command goes through the command rules. If commands come back as "Invalid input", the profile does not match the equipment's system: pick another one.

From the device page, a fetch runs the profile's identity commands and extracts model, version, name, serial number and uptime.

Removing a Connector​

From the device page:

ActionEffect
UninstallA signed order asks the connector to uninstall itself (online machines only)
Uninstall codeA code valid for 24 h lets you uninstall by hand; it is shown only once. Without that code, the uninstaller refuses
RevokeThe connector is disconnected and can no longer reconnect; it stays installed on the machine
RetireThe device is retired for good: connector revoked, record frozen, history kept