Skip to main content
Add machines puts Quint on computers. It asks which computers you are adding, makes the files your tool needs, gives that tool’s steps as a checklist, and waits for your first computer to connect. Nothing is installed until your management tool pushes the files. You need the Admin or Owner role, signed in to the dashboard; a partner’s delegated session or an API-token session makes nothing. Open it with Add machines on Settings › Machines & licensing, or from Data Sources (the Deploy sensors panel, or an empty host list). Settings › Fleet and Settings › API tokens link to it too.

​
The five steps

The top of the wizard shows where you are: Choose computers, Name it, Download files, Upload and First computer. Click a finished step to go back to it. Just one computer has no Upload step.
1

Choose computers

Three questions, each a row of cards with an icon or the tool’s logo: the Operating system, how you install software on those computers, then which tool. Choose a path lists every combination. On Windows, Microsoft Intune is picked for you. Changing an earlier answer clears the later ones. Click Continue; the top of the wizard then shows your choice, for example “Mac · Jamf Pro”.
2

Name it

Name the group of computers, for example “Engineering Macs”; the name appears on your packages list. It is the only field. You are not asked how many computers: Quint sets the package’s limit. Click Continue.
3

Download files

A checklist of files. Each row says what the file is for and carries a label: Ready, Downloaded, Made with your files (it comes when you make them) or Ask Quint support. On a Mac, the approvals profile and the installer can be downloaded straight away; they hold no secret. Read Before you make your files, then click Make my files. The line beside Ready says the limit, for example ““Engineering Macs” can add up to 500 computers.” Download each file, or click Download all files, then Continue.
The files can be downloaded once. If you lose them, make a new package; the old one keeps working until you stop it. They carry the package’s join code, which adds computers to your organisation, so keep them inside your management tool.
4

Upload

Your tool’s steps as a numbered checklist, in order: the place in your tool, what to do there, and the files it uses. Tick each off as you go; the ticks are only for you. On a Mac, Profiles first, then the installer comes first. Click Next: check for my first computer.
5

First computer

“Waiting for your first computer…” until a computer joins after you made the files, usually a few minutes after your tool installs Quint. Then five checks: Joined your organisation, Sending heartbeats, Endpoint Security extension active, Network extension active and AI traffic is visible to Quint. Each reads Done, Not working or Not reported yet; on Windows and Linux the two extension checks read Not needed on Windows or Not needed on Linux. Click Open this computer for its page.

​
Choose a path

Each tool’s card is labelled Early access, or Partly tested for Mosyle: the approvals profile and the installer have been pushed through Mosyle with no click on the Mac. If any step needed a click on the computer, tell Quint support.

​
What you download

Every package also has a README.txt with the same steps. The installers come from Quint’s public download site: Mac and Windows. An installer row that says Ask Quint support means we send it to you.

​
One computer

Just one computer makes no package. After the name, “Install on this computer” offers the installer on a Mac or Windows. Click Get a one-time install code: it adds one computer, stops working after 24 hours, and is shown once. Below it is one command to copy:
  • Mac: paste it into Terminal on the Mac.
  • Linux: paste it into a terminal, as a user who can run sudo.
  • Windows: rename the installer you downloaded to quint.msi, open PowerShell as administrator in the folder that holds it, and paste the command there.
Paste the code when the command asks for your Quint token, never into the command itself. Click I’ve run it and the wizard waits for the computer. A Mac set up this way has no approvals profile, so the person at the Mac allows the extensions; see Install on a Mac.

​
After the rollout

Machines & licensing lists every package and how many computers joined. When a group is done, or if its files may have leaked, stop the package there: no new computers can join, and joined computers keep running.
Do not revoke a package’s token under Settings › API tokens to end a rollout. Revoking it disconnects every computer it enrolled. Stop the package in Machines & licensing instead.

​
If this fails

​
Next