> ## Documentation Index > Fetch the complete documentation index at: https://docs.quintai.dev/llms.txt > Use this file to discover all available pages before exploring further. # Add machines > Use the Add machines wizard to put Quint on your computers: choose the operating system, how you install software and your tool, name the group, download its files, and upload them in the right order. **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](https://docs.quintai.dev/settings/machines-and-licensing.md), 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](#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**. > [!WARNING] > > 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 | Your computers | Choose | Then read | | - | - | - | | Macs in Jamf Pro | **Mac** › **A device management tool (MDM)** › **Jamf Pro** | [Jamf Pro](https://docs.quintai.dev/install/mdm-jamf.md) | | Macs in Microsoft Intune | **Mac** › **A device management tool (MDM)** › **Microsoft Intune** | [Microsoft Intune](https://docs.quintai.dev/install/mdm-intune.md) | | Macs in Mosyle | **Mac** › **A device management tool (MDM)** › **Mosyle** | [Mosyle](https://docs.quintai.dev/install/mdm-mosyle.md) | | Macs in Iru (formerly Kandji) or another MDM | **Mac** › **A device management tool (MDM)** › **Iru (formerly Kandji)** or **Another MDM** | [Roll out with MDM](https://docs.quintai.dev/install/mdm.md) | | Windows PCs in Microsoft Intune | **Windows** › **A device management tool (MDM)** | [Windows](https://docs.quintai.dev/install/windows.md) | | Linux computers in Ansible, Puppet or Chef | **Linux** › **A configuration tool** › your tool | [Linux](https://docs.quintai.dev/install/linux.md) | | One computer, no management tool | Its operating system › **Just one computer** | [One computer](#one-computer) below | 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 | Computers | Files | What each is for | | - | - | - | | Macs | `quint-approvals.mobileconfig` | The **approvals profile**. Pre-approves Quint's system extensions, Full Disk Access and network filter. The same for every organisation; it holds no secret. | | | `quint-enrollment-….mobileconfig` | The **enrollment profile**. Connects each Mac to your organisation. Holds this package's join code and your license. | | | `com.quint.security.plist`, `enrollment.conf` | The same settings, for tools that take custom settings for the preference domain `com.quint.security` instead of a profile (use one or the other), and as a root-only file for pre-install scripts. Quint 1.1.29 reads only the profile or the settings file. | | | `quint-v1.1.29.pkg` | The Mac installer. Signed and notarized; the same for every organisation. | | Windows | `install.ps1`, `quint-token.txt`, `quint-license.txt`, and the installer `quint-windows-x64.msi` | The install script, the join code, your license, and the installer, signed by Quint Security. See [Windows](https://docs.quintai.dev/install/windows.md). | | Linux | `enrollment.conf`, `install.sh` | The enrollment file and the install script. See [Linux](https://docs.quintai.dev/install/linux.md). | Every package also has a `README.txt` with the same steps. The installers come from Quint's public download site: [Mac](https://quint-releases-public.s3.amazonaws.com/v1.1.29/quint-v1.1.29.pkg) and [Windows](https://quint-releases-public.s3.amazonaws.com/v1.1.29/quint-windows-x64.msi). 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](https://docs.quintai.dev/install/macos.md#if-the-mac-is-not-in-an-mdm). ## After the rollout [Machines & licensing](https://docs.quintai.dev/settings/machines-and-licensing.md) 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. > [!WARNING] > > 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 | What you see | What it means | What to do | | - | - | - | | "Only an admin of your organisation can add computers." | Your role is **Read** or **Policy Writer** | Ask an **Admin** or **Owner** to open **Add machines**. | | "Adding computers needs an admin signed in to Quint." | The session was opened with an API token | Sign in to the dashboard as an **Admin** or **Owner**. | | "This package can't be made yet: Quint is still being updated on our side." | Nothing was made | Try again later. If it keeps happening, contact Quint support. | | "Waiting for your first computer…" does not change | The computer has not joined yet | Check the order of the upload steps, then [Verify a machine](https://docs.quintai.dev/install/verify-and-troubleshoot.md). | | A check reads **Not working** | That part of Quint is not running on the computer | Open the computer's page, then see [Verify a machine](https://docs.quintai.dev/install/verify-and-troubleshoot.md). | ## Next * [Machines & licensing](https://docs.quintai.dev/settings/machines-and-licensing.md) * [Verify a machine](https://docs.quintai.dev/install/verify-and-troubleshoot.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.