Skip to main content
At the end of this page every Linux computer your playbook, manifest or recipe reaches has Quint installed and is joined to your organisation. You need a configuration tool that can copy a file as root and run a command as root, outbound HTTPS from each computer, and the Admin or Owner role in the Quint dashboard.
Linux is early access. If a step behaves differently on your distribution, tell Quint support.

What the package holds

The install script uses Quint’s own installer. Signed .deb and .rpm packages are also published; Linux distributions lists where each installs.
1

Make the package

In Quint, open Add machines. Choose Linux, then A configuration tool, then Ansible, Puppet or Chef, and name the package for the group. Click Make my files and download both files. They can be downloaded once. See Add machines.
2

Place the enrollment file

In your playbook, manifest or recipe, copy enrollment.conf to /etc/quint/enrollment.conf on each computer: owner root, mode 0600, no ACL. install.sh and Quint refuse the file if anyone but root can read it. Keep the file in your tool’s secret store, not in a shared repository.
3

Run the install script

In the same run, once the file is in place, copy install.sh to the computer and run it as root:
4

Leave the file in place

Leave /etc/quint/enrollment.conf where it is. The join code is used once per computer, to join; the computer then holds its own credential.
5

Verify each machine

The wizard’s First computer step shows the first computer’s checks; the two extension checks read Not needed on Linux. Then open Data Sources: each computer appears under Telemetry by host. Verify a machine explains each state.

One Linux computer

For one computer without a configuration tool, choose Linux, then Just one computer, in Add machines. Paste the command the wizard shows into a terminal on the computer, as a user who can run sudo; paste the one-time install code when the command asks for your Quint token. See One computer.

After the rollout

A package admits new computers for one year from the day it is made, up to its limit. When the group is done, stop the package in Machines & licensing: computers that already joined keep running. To reach new computers after that, make a new package and replace enrollment.conf in your tool with its file.

If this fails

Next