Deploy the Abloomify Device Agent via Microsoft Intune (Windows Guide)

July 21, 2026

Walter Write

5 min read

Abloomify Windows device agent deployed through Microsoft Intune as a Win32 app, flowing to a group of managed Windows devices

Overview

This guide walks you through deploying the Abloomify device agent to Windows machines using Microsoft Intune. Intune's line-of-business app type needs an .msi, and the Abloomify installer is an .exe, so you deploy it as a Win32 app: wrap AbloomifySetup.exe into a .intunewin package, set a silent install command, add a detection rule, and assign it to a device group.
The short version is:
  1. Wrap AbloomifySetup.exe with the Win32 Content Prep Tool into a .intunewin package.
  2. Create a Win32 app in Intune with a silent install command and a file detection rule.
  3. Assign it to your Windows device group and verify.

Windows only

This guide covers Windows devices. For Macs managed in Intune, deploy the macOS agent separately (see the Intune macOS guide). For the general Windows install (manual and silent) and links to other tools, see the Windows install hub.

Contents

What Abloomify collects (and what it does not)

The Abloomify device agent collects high-level app and technology-usage metrics: which applications are active, for how long, and when sessions are active. It does not log keystrokes (only an aggregate keystroke count per app, never the keys themselves), does not take screenshots or record the screen, and never uses the microphone or camera. For the full breakdown, see the Abloomify device agent overview.

Before you begin

You will need:
  • A Microsoft Intune subscription with Windows device management enabled.
  • Windows devices already enrolled in Intune. Intune documents enrollment thoroughly, so this guide does not re-cover it.
  • Windows 10 or Windows 11 (64-bit) on the target machines.
  • An Abloomify paid subscription and admin access to the Abloomify console.
  • The Microsoft Win32 Content Prep Tool (IntuneWinAppUtil.exe), a free download from Microsoft.
  • The AbloomifySetup.exe for your chosen variant, downloaded from the Device Agents page in the console.

Choose your installer variant

The Windows download offers two variants: with Chrome extension (also force-installs the Abloomify Chrome extension) and agent only (no browser extension). Pick one and wrap that single file. If you already push the Chrome extension through your browser policy, choose agent only. See the Windows install hub for the full comparison.

Step 1: Package the installer as .intunewin

Wrap the installer into a .intunewin package first.
  1. Put your chosen AbloomifySetup.exe in a source folder by itself, for example C:\AbloomifySource.
  2. Run the Win32 Content Prep Tool:
    IntuneWinAppUtil.exe -c C:\AbloomifySource -s AbloomifySetup.exe -o C:\AbloomifyOutput
  3. This produces AbloomifySetup.intunewin in the output folder. That is the file you upload to Intune.

Step 2: Create the Win32 app in Intune

In the Intune admin center, go to Apps > Windows > Add, choose Windows app (Win32), and upload the .intunewin file.
On the Program step, set:
  • Install command:
    AbloomifySetup.exe /quiet /norestart
  • Uninstall command:
    AbloomifySetup.exe /uninstall /quiet /norestart
  • Install behavior: System. The agent installs per-machine, so it must run in the device (SYSTEM) context, not the user context.
On the Requirements step, set Operating system architecture to 64-bit and a sensible Minimum operating system (for example, Windows 10 1809 or later).

Step 3: Set the detection rule

On the Detection rules step, choose Manually configure detection rules > Add, and use a File rule:
  • Rule type: File
  • Path: C:\Program Files\Abloomify\Abloomify Device Agent
  • File or folder: AbloomifyDeviceAgent.exe
  • Detection method: File or folder exists
That tells Intune the app is installed when the agent binary is present, so it does not reinstall on devices that already have it.

Step 4: Assign and roll out

On the Assignments step, add your target device group under Required, then save.
Important: Assign to a device group, not a user group. The agent installs per-machine in the SYSTEM context, so device-targeted assignment is the correct scope.
Devices install the agent silently as they check in with Intune.
Note: Deployment is not instant. Assigned devices pick up the app as they sync with Intune, which can take a while across a fleet. Plan for machines to complete over a window, not all at once.

Step 5: Verify the deployment

You can confirm success in Intune and in the Abloomify console.
In Intune: Open the Win32 app and check Device install status. Target devices should report Installed.
In the Abloomify console: Within a short window, the device begins reporting in your Abloomify console, which confirms the agent is installed and running. You will also see Abloomify Device Agent listed in Add/Remove Programs on the device.

FAQ

What install context should I use?

System. The agent installs per-machine, so it must run in the device (SYSTEM) context. Assign the app to a device group, not a user group.

Does the agent take screenshots or log keystrokes?

No. It does not capture screen content, record the screen, or 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.

How do I confirm it installed?

Check the app's Device install status in Intune, confirm Abloomify Device Agent appears in Add/Remove Programs on the device, and confirm the device begins reporting in your Abloomify console.

Which variant do I wrap?

Whichever you need: with Chrome extension or agent only. They install the same agent; the only difference is the force-installed Chrome extension. Wrap the single AbloomifySetup.exe for your chosen variant.

Need help?

If a device shows the app as failed, or does not begin reporting in your Abloomify console after install, contact Abloomify at support@abloomify.com with the Intune install status and the Windows version. For the general Windows install and other deployment tools, see the Windows install hub.
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.