Deploy the Abloomify Device Agent via SCCM / Configuration Manager (Windows Guide)

July 21, 2026

Walter Write

5 min read

Abloomify Windows device agent packaged as a Microsoft Configuration Manager application and deployed to a device collection across an enterprise fleet

Overview

This guide walks you through deploying the Abloomify device agent to Windows machines with Microsoft Configuration Manager (SCCM / ConfigMgr). You create an application with a script-installer deployment type, point it at AbloomifySetup.exe, set silent install and uninstall commands, add a detection method, and deploy it to a device collection.
The short version is:
  1. Copy the AbloomifySetup.exe to a content source folder.
  2. Create an application with a script installer deployment type: silent install, silent uninstall, and a file detection method.
  3. Distribute the content and deploy to a device collection, then verify.

Windows only

This guide covers Windows devices managed in Configuration Manager. For the general Windows install (manual and silent) and other deployment 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:
  • Microsoft Configuration Manager (SCCM) with target devices under management (the ConfigMgr client installed).
  • Access to the Configuration Manager console with rights to create and deploy applications.
  • A content source share the site server can read.
  • Windows 10 or Windows 11 (64-bit) on the target machines.
  • An Abloomify paid subscription and the AbloomifySetup.exe from the Device Agents page.

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 package that single file. See the Windows install hub for the full comparison.

Step 1: Stage the installer content

  1. Create a source folder on your content share, for example \\server\Sources\Apps\AbloomifyDeviceAgent\.
  2. Copy your chosen AbloomifySetup.exe into that folder. This is the content location the application will reference.

Step 2: Create the application

  1. In the Configuration Manager console, go to Software Library > Application Management > Applications, then Create Application.
  2. Choose Manually specify the application information (the installer is an .exe, so there is no MSI to auto-detect).
  3. Fill in the application name, for example Abloomify Device Agent, and publisher Abloomify.
  4. Add a deployment type of Script Installer (manually specify), and set the content location to the folder from Step 1.
  5. Set the commands:
    • Installation program:
      AbloomifySetup.exe /quiet /norestart
    • Uninstall program:
      AbloomifySetup.exe /uninstall /quiet /norestart
  6. On the deployment type's User Experience settings:
    • Installation behavior: Install for system.
    • Logon requirement: Whether or not a user is logged on.
    • Visibility: run Hidden (silent).
Important: Install for system runs the agent install per-machine in the SYSTEM context, which is what the per-machine installer requires.

Step 3: Set the detection method

On the deployment type's Detection Method, add a clause using File System:
  • Type: File
  • Path: C:\Program Files\Abloomify\Abloomify Device Agent
  • File or folder name: AbloomifyDeviceAgent.exe
  • Condition: The file system setting must exist on the target system to indicate presence of this application.
That marks the app as installed once the agent binary is present, so ConfigMgr does not reinstall it on compliant devices.

Step 4: Distribute content and deploy

  1. Distribute Content for the application to your distribution points.
  2. Deploy the application to a device collection with the target machines. Set the Purpose to Required for an unattended rollout.
  3. Save the deployment. Clients install the agent silently at their next policy evaluation and maintenance window.
Note: Deployment is not instant. Clients pick up the deployment on their policy cycle, so plan for machines to complete over a window.

Step 5: Verify the deployment

In Configuration Manager: Open Monitoring > Deployments and check the deployment status. Target devices should move to Success.
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 in Add/Remove Programs on the device.

FAQ

Application or Package/Program?

Either works, but the Application model is recommended because its detection method prevents reinstalls and reports install state cleanly. Use the silent install and uninstall commands shown above in a Script Installer deployment type.

What install behavior should I use?

Install for system, with logon requirement Whether or not a user is logged on. The agent installs per-machine in the SYSTEM context.

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, 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 deployment status under Monitoring > Deployments, 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 package?

Whichever you need: with Chrome extension or agent only. Both install the same agent; the only difference is the force-installed Chrome extension.

Need help?

If a deployment shows errors, contact Abloomify at support@abloomify.com with the deployment status and the AppEnforce.log from an affected client. 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.