Install the Abloomify Device Agent on Windows

July 20, 2026

Walter Write

7 min read

Abloomify device agent installed on Windows and reporting into the Abloomify console

Quick Setup

This guide is the starting point for installing the Abloomify device agent on Windows. It covers what you download, how to install it on a single machine (by hand or silently), and how to confirm it worked. When you are ready to push it to a fleet, jump to the per-tool deployment guide for Intune, Group Policy, SCCM, or Rippling.
The short version is:
  1. Download the AbloomifySetup.exe from the Device Agents page in the Abloomify console.
  2. Install it: double-click on a single machine, or run it silently with AbloomifySetup.exe /quiet /norestart.
  3. Verify the device shows up in your Abloomify console.

Windows only

This guide covers Windows devices only. If you manage Macs, the macOS agent is a separate package with its own MDM flow (see the Intune macOS guide). For the full picture of how the agent works and what it does and does not collect, see the Abloomify device agent overview.

Contents

What Abloomify collects (and what it does not)

Before you push anything to your fleet, it helps to be clear about what the agent does, so you can answer questions from your team with confidence.
The Abloomify device agent collects high-level app and technology-usage metrics: which applications are active, for how long, and when sessions are active. That is the signal that powers Abloomify's analytics.
It does not do the invasive things people associate with traditional monitoring software:
  • No keylogging. There is no keystroke capture and no input monitoring. The agent reads only an aggregate keystroke count per active app (a measure of how busy an app was), never which keys you press or what you type.
  • No screenshots or screen recording. The agent does not capture screen content, and there is no screen-capture code in it.
  • No microphone or camera. The agent never requests or uses audio or video capture.
Same posture as the macOS agent, one platform over. For the deeper breakdown, see the Abloomify device agent overview.

Before you begin

You will need:
  • Windows 10 or Windows 11 (64-bit) on the target machines.
  • Local administrator rights on the machine, or a device-management tool (Intune, Group Policy, SCCM, Rippling) that installs in the SYSTEM context. The agent installs per-machine, so it needs elevation.
  • An Abloomify paid subscription and admin access to the Abloomify console.
  • The installer, downloaded from the Device Agents page in the console (covered next).
Note: The installer is self-contained. You do not need to stage any prerequisites separately.
Note: During install, Windows shows the publisher as Abloomify Inc. You can confirm this under the file's Properties > Digital Signatures before you deploy.

Choose your installer: with Chrome extension or agent only

On the Device Agents page, the Windows download offers two variants. Pick one per machine.
VariantWhat it installsChoose when
With Chrome extensionThe device agent and a force-installed Abloomify Chrome extension for browser-level signalYou want browser activity captured alongside desktop app usage
Agent onlyThe device agent by itself, no browser extensionYou do not want the Chrome extension, or you deploy the extension separately through your browser-management policy
Both variants install the exact same agent. The only difference is whether the Chrome extension is force-installed alongside it. If you already push the Abloomify Chrome extension through your browser policy, choose agent only to avoid managing it twice.
Note: The download is specific to your company. Grab the installer from your own Abloomify console so it carries your company's identity, rather than reusing a file from somewhere else.

Install manually on one machine

Use this for a single machine, a pilot, or a quick test.
  1. Download your chosen variant of AbloomifySetup.exe from the Device Agents page.
  2. Double-click the installer. Windows shows Abloomify Inc. as the verified publisher in the User Account Control prompt. Approve it.
  3. Accept the license when the installer displays it, then click Install.
  4. Wait for the installer to finish. It installs the agent, registers the Windows service, and starts it automatically. No reboot is required.
That is the whole manual flow. Skip to Verify the install to confirm it took.

Silent install

Use this for scripted or unattended installs (a login script, a remote-execution tool, or an RMM). Run from an elevated command prompt or in the SYSTEM context:
AbloomifySetup.exe /quiet /norestart
  • /quiet runs with no UI.
  • /norestart prevents the installer from rebooting the machine.
To uninstall silently, run the same bundle with the uninstall flag:
AbloomifySetup.exe /uninstall /quiet /norestart
Important: The silent install must run elevated (as administrator or SYSTEM). Run from a standard user context, and the per-machine install will fail. Intune, SCCM, Group Policy startup scripts, and most RMM tools already run in the SYSTEM context, so this is handled for you there.

Deploy across your fleet

The install command is the same (AbloomifySetup.exe /quiet /norestart) no matter which tool pushes it. What differs is how you package and assign it in each console. Pick your tool:
Each guide uses the same installer you picked above. Choose the variant (with Chrome extension or agent only) once, then wrap or upload that one file in your tool of choice.

Verify the install

You can confirm a successful install without touching the machine.
In Add/Remove Programs: Open Settings > Apps > Installed apps (or Programs and Features). Abloomify Device Agent by Abloomify should be listed.
In the Abloomify console: Within a short window of installing, the device begins reporting in your Abloomify console. That is the confirmation that the agent is installed and running.

FAQ

Which installer do I pick, with Chrome extension or agent only?

Both install the same device agent. With Chrome extension also force-installs the Abloomify Chrome extension for browser-level signal. Agent only installs the agent by itself. If you already deploy the Chrome extension through your own browser policy, pick agent only so you are not managing it in two places.

Does the agent take screenshots or log keystrokes?

No. The agent does not capture screen content, does not record the screen, and does not log keystrokes. It reads an aggregate keystroke count per active app (a busyness signal), never the keys themselves, and it never uses the microphone or camera. See the device agent overview for the full breakdown.

Does the installer need administrator rights?

Yes. The agent installs per-machine, so the installer must run elevated, as a local administrator or in the SYSTEM context. Intune, SCCM, Group Policy, and most remote-management tools already run installs as SYSTEM, so a manual double-click just needs a local admin to approve the UAC prompt.

How do I deploy this to my whole fleet?

Use your existing device-management tool. The install command is identical everywhere; only the packaging and assignment differ. See the Intune, Group Policy, SCCM, or Rippling guide.

Can I deploy the macOS agent this way?

No. This flow is Windows-only. The macOS agent is a separate package with its own MDM deployment (configuration profile plus a pkg). See the Intune macOS guide if you also manage Macs.

Need help?

If a device does not begin reporting in your Abloomify console after install, contact Abloomify at support@abloomify.com with the Windows version, and we will help you sort it out. For background on how the agent works across platforms, start with the Abloomify device agent overview.
Share this article
← Back to Blog
Walter Write
Walter Write
Staff Writer

Tech industry analyst and content strategist specializing in AI, productivity management, and workplace innovation. Passionate about helping organizations leverage technology for better team performance.