10-minute setup: from signup to your first investigation
Create your organization, protect your account, connect one device, and ask it your first question. Ten minutes is our target for one device, not a measured time.
Before you start
- Ten minutes is a target, not a measurement. We have not timed this on customer devices. Email delivery, device permissions, and your organization’s approval prompts can all add time.
- A work email you can open now, and an authenticator app on your phone, such as Microsoft Authenticator or Google Authenticator.
- One Windows PC or Mac you can administer. A Linux device also works, using a command instead of a link.
- Outbound network access from that device to Rapport. The Deployment page lists the requirements.
Screenshots show the Rapport interface with example data. Use your organization’s devices and values. Select an image to view it at full size.
Create your account and organization
On the Rapport website, choose Try Rapport. Enter Your name, Organization name, Work email, and a Password of at least eight characters, then choose Create account. If Rapport asks you to confirm your email, open the message and follow its link. Resend confirmation lets you ask for another after a minute.
What you should see: Rapport asks you to set up multi-factor authentication before you enter your organization.
Protect your account with an authenticator app
Sign in if asked. On the first verification screen, choose Set up authenticator, scan the QR code with your app, and enter the Six-digit authentication code. This step is required: installing a device needs an administrator who has completed it. Add a backup authenticator later, in Account security.
What you should see: The console opens on Overview for your organization.
Open Install agent and choose how to install
Open Admin → Agent Fleet and choose Install agent, or search for Install agent. The page offers three ways to install. For a first device, use the install link in the next step unless you already deploy software through device management, or the device runs Linux.
| Field or control | What to do |
|---|---|
| Send an install link | Recommended for one Windows PC or Mac. Open the link, download, and open the file. No commands, and no token to type. |
| Deploy with device management | A Windows MSI or macOS PKG package for Intune, Jamf, Configuration Manager, Group Policy, or an RMM tool. |
| Install with a command | For a technician at the machine, and the only way to install on Linux. |
Install with a link on a Windows PC or Mac
In Send an install link, keep Devices at 1 and choose Create install link. Copy the link, which is shown once, and open it on the device. Choose Download for Windows or Download for macOS, then open the downloaded file. On Windows, choose Yes when asked to allow changes. On a Mac, click through the installer and enter your password when asked.
What you should see: The installer finishes on its own, with no token to type.
Or install from a package or command
To use a package, go to Deploy with device management, choose Generate deployment token, and download the MSI or PKG for your device. On Windows, run the command below as an administrator with your own token. On a Mac, deploy the package together with a preference profile that holds the token. On Linux there is no package: generate an install token under Install with a command, then run the Linux command your console shows as root or with sudo, and enter the token when it asks. That command pins the published release and checks its signed SHA-256 hash before the installer script runs. The install guide has the full steps for each.
msiexec /i DexIQAgent-windows-x64.msi DEXIQ_TOKEN=<token> /qn /norestart /l*v "%WINDIR%\Temp\DexIQAgent-install.log"Confirm the device is reporting
Open Endpoints and search for the device’s hostname. A finished installer does not prove enrollment, so wait for a recent Last seen time before moving on.
What you should see: The device is listed in your organization with a recent heartbeat.
Check that the assistant can run
Open Admin → AI Assistant and read the API key status. Using the platform key or Tenant key configured means it can run. No key available means it cannot: paste your provider’s key and choose Save key. Then choose Test connection. New organizations start with Device assistant on, and with Shell tool and Auto-run read-only commands on. If your security team wants those off first, follow the guide to turning execution off.
What you should see: The test returns a reply and shows which key it used.
Ask your first question
In Endpoints, select the device. It opens on Agent workspace. Choose New conversation and describe a real symptom, for example Why is this device running slowly?. Follow the checks in Session activity. Read-only checks run on their own. Anything that changes the device waits for you to choose Approve & run or Decline.
What you should see: The conversation shows the checks that ran on the device and what they found.
If something doesn’t work
The confirmation email does not arrive.
Check spam, then use Resend confirmation after a minute. If you already registered with that address, sign in instead.
You see No organization yet.
You have an account but no organization. To join a teammate’s, open their invitation. To start your own, enter its name and choose Create organization.
Install agent says installers are unavailable.
The link and package options need a published signed release. Choose Retry if it is offered. Do not substitute a download from anywhere else.
The device does not appear in Endpoints.
Confirm the installer finished, the link or token belonged to this organization, and the device can reach Rapport. The install guide lists the local check for each operating system.
The assistant does not reply.
Check the API key status and Test connection, then check that the device has a recent heartbeat and that Device assistant is on in its agent policy.