Deploy the Abloomify Device Agent via Group Policy (Windows Guide)

July 21, 2026

Walter Write

5 min read

Abloomify Windows device agent deployed across an Active Directory domain with Group Policy, using a startup script that runs the installer as SYSTEM

Overview

This guide walks you through deploying the Abloomify device agent to Windows machines with Group Policy in an on-prem Active Directory domain. You deploy it with a computer startup script that runs the silent install as SYSTEM (the section below explains why this, rather than GPO Software Installation).
The short version is:
  1. Stage the AbloomifySetup.exe on a network share that domain computers can read.
  2. Create a GPO with a computer startup script that silently installs the agent, with a guard so it does not reinstall on every boot.
  3. Link the GPO to the target OU and verify.

Windows only

This guide covers Windows domain-joined devices. 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:
  • An Active Directory domain with the target machines domain-joined.
  • Access to Group Policy Management on a domain controller or an admin workstation with RSAT.
  • A network share readable by the computer accounts that will install the agent (grant Domain Computers 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 stage that single file. See the Windows install hub for the full comparison.

Why a startup script, not Software Installation

Group Policy's built-in Software Installation feature only deploys .msi packages. The Abloomify installer is an .exe, so you deploy it with a computer startup script instead. Startup scripts run at boot in the SYSTEM context, which is already elevated, so the per-machine install works without any extra credentials. A short guard in the script keeps it from reinstalling every time the machine boots.

Step 1: Stage the installer on a share

  1. Copy your chosen AbloomifySetup.exe to a network share, for example \\server\software\Abloomify\.
  2. On that share, grant Domain Computers the Read permission (both share and NTFS), so machine accounts can reach the installer at boot.

Step 2: Create the GPO and add the startup script

  1. In Group Policy Management, create a new GPO, for example Abloomify Device Agent - Install.
  2. Edit it and go to Computer Configuration > Policies > Windows Settings > Scripts (Startup/Shutdown) > Startup.
  3. On the PowerShell Scripts tab, click Add and point to a script (store it in the GPO's own scripts folder or on the same share). Use a guarded silent install like this:
    $agentExe = "C:\Program Files\Abloomify\Abloomify Device Agent\AbloomifyDeviceAgent.exe"
if (-not (Test-Path $agentExe)) {
    Start-Process "\\server\software\Abloomify\AbloomifySetup.exe" `
      -ArgumentList "/quiet","/norestart" `
      -Wait
}
    The Test-Path guard means the install runs once. On later boots, the agent is already present, so the script does nothing.
  4. Click OK to save the script.
Important: Startup scripts run as SYSTEM, which is why this installs per-machine without a prompt. Do not use a logon script for this. Logon scripts run as the signed-in user and will not have rights to install per-machine.
  1. Link the GPO to the OU that contains your target computers.
  2. On a test machine, run gpupdate /force and then reboot (startup scripts run at boot).
  3. The agent installs silently on that first boot after the policy applies.

Step 4: Verify the deployment

On a target machine, confirm the install took:
The app is installed. Open Settings > Apps > Installed apps (or Programs and Features). Abloomify Device Agent should be listed.
The device is reporting. Within a short window, the device begins reporting in your Abloomify console, which confirms the agent is installed and running.
If a machine did not install: Run gpresult /r to confirm the GPO is applied to the computer.

FAQ

Why a startup script and not a logon script?

Startup scripts run as SYSTEM at boot, which is elevated, so the per-machine install works. Logon scripts run as the signed-in user and lack the rights to install per-machine.

Will it reinstall on every reboot?

No. The Test-Path guard checks for the installed agent binary and only runs the installer when it is missing, so it installs once and then no-ops on later boots.

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?

Open Settings > Apps > Installed apps and confirm Abloomify Device Agent is listed, then confirm the device begins reporting in your Abloomify console. If a machine did not install, run gpresult /r to confirm the GPO applied.

Need help?

If a machine did not install, contact Abloomify at support@abloomify.com with the gpresult /r output from the affected machine. 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.