Install on Windows

Deploy a Quint install package to Windows computers as an Intune Win32 app: the installer, the install script and the two files it reads.

At the end of this page every Windows computer in your Intune group has Quint installed and is joined to your organisation. You need an Intune role that can add Win32 apps, the Microsoft Win32 Content Prep Tool (IntuneWinAppUtil.exe), and the Admin or Owner role in the Quint dashboard.

Windows is early access. These steps follow Intune’s Win32 app flow; if a step differs in your tenant, tell Quint support.

​

Before you start

• 64-bit (x64) Windows computers, enrolled in Intune.
• The Windows installer, quint-windows-x64.msi. It is the same for every organisation, and signed by Quint Security. The wizard links it, or download it from Quint’s public download site. Check its signature with Get-AuthenticodeSignature before you package it.

​

What the package holds

File	What it is for
install.ps1	The install script. Runs quint.msi with the two files below, then deletes the join code file, whatever the installer returned.
quint-token.txt	The package’s join code. Read once by the installer, then deleted. Keep it out of shared folders.
quint-license.txt	Your organisation’s license. Not a secret.

1. Make the package

   In Quint, open Add machines. Choose Windows, then A device management tool (MDM); Microsoft Intune is picked for you. Name the package for the group and click Make my files. Download every file, and the Windows installer from its row. The package’s files can be downloaded once. See Add machines.

2. Put the files in one folder

   Rename the Windows installer to exactly quint.msi: install.ps1 looks for that name and stops if it is missing. Put quint.msi, install.ps1, quint-token.txt and quint-license.txt in one folder.

3. Package the folder

   Run the Microsoft Win32 Content Prep Tool on that folder with install.ps1 as the setup file. It makes install.intunewin. The file contains the join code: keep it inside Intune, and delete your local copy once it is uploaded.

4. Add the Win32 app

   In the Intune admin center, open Apps › Windows › Add and choose Windows app (Win32). Upload install.intunewin.

   • Install command: powershell -NoProfile -ExecutionPolicy Bypass -File .\install.ps1
   • Install behavior: System.
   • Device restart behavior: Determine behavior based on return codes.
   • Requirements: operating system architecture x64.
   • Detection rules: a registry rule, key exists, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\QuintProxy.

   Assign it to your group as Required.

5. Verify each machine

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

​

One Windows computer

For one computer without Intune, choose Windows, then Just one computer, in Add machines. Download the installer and rename it to quint.msi, open PowerShell as administrator in the folder that holds it, and paste the command the wizard shows; 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 build a new install.intunewin from it.

​

If this fails

What you see	What it means	What to do
The app reports a failed install	install.ps1 did not find quint.msi, quint-token.txt or quint-license.txt beside it	Rename the installer to quint.msi, put all four files in one folder, and package it again. If you no longer have the join code file, make a new package.
Intune reinstalls the app on every check	The detection rule does not match	Use the registry rule above, exactly.
The computer installs but never appears in Data Sources	The package is no longer Active, or the computer has no outbound HTTPS	Check the package in Machines & licensing, and the network.

​

Next

• Verify a machine
• Machines & licensing