.svg?fit=max&auto=format&n=9mgYzkCsWGfCgDGh&q=85&s=4fd670d691aa6a1a77dbfa0ed4830fb1){kind=logo}
- Starts with no window at all at install, at every login, and after updates.
- Sits in the system tray, signs the user in silently (via Silent Authentication), and captures as normal.
- Opens its window only when the user chooses to, by clicking the tray icon.
Requirements
The per-user installer does not support the
/STARTHIDDEN flag. If your fleet currently runs the per-user agent, see Migrating from a per-user install below.Deployment
Install command
/S: silent install (no installer UI)./STARTHIDDEN: enables silent startup for the machine./DISABLEAUTOUPDATE: recommended for silent fleets, see the note below.
Why disable auto-update? A per-machine install lives in
Program Files, so the agent’s built-in auto-updater needs elevation to apply an update. On standard-user machines this surfaces a UAC prompt, which defeats the purpose of a silent deployment. Disable auto-update and roll out new agent versions through your MDM instead, the same way you deployed initially./STARTHIDDEN flag writes a machine-wide policy that the agent reads at every launch, so silent startup survives reboots, autostart, and agent updates:
Starting the agent after install
A silent install does not launch the agent. Trigger it from your deployment tool, or let it start at the next user login (autostart is registered on first run):Migrating from a per-user install
The per-machine installer does not remove an existing per-user installation, so deploying it directly would leave two copies on the machine. Uninstall the per-user agent first:Behavior Reference
There are no pop-ups or notifications of any kind. The window appears only from an action the user takes.
If silent sign-in fails
The agent stays hidden and does not capture. The tray menu shows “Sign in required”; clicking the tray icon opens the window where the user can sign in via the browser flow. Because such machines are silent and idle, they will not appear in your Fluency dashboards. If a deployed user is missing, check that machine’s tray first.Verification
On a test machine after deployment:- Confirm the policy was written (an empty result means the installer wasn’t elevated or predates 0.15.5):
- Launch the agent. No window should appear; the Fluency tray icon should be present.
- Click the tray icon. The window opens; close it and it returns to the tray.
- Reboot. The agent starts again with no window.
Reverting
To return a machine to standard (visible) startup without reinstalling:Intune Notes
The packaging steps are the same as the per-user flow (see IT - Deploying Fluency Agent), with these differences for the per-machine silent package:FAQ
Does silent startup change what the agent captures? No. Authentication, capture, and settings behave exactly the same; only window visibility changes. Does this work on macOS? No. Silent startup is currently Windows-only, via the per-machine installer. Contact us if you need this on macOS. Can users still use the agent normally? Yes. The tray icon works exactly as always; clicking it opens the full agent window with status and settings. We already deployed per-machine without the flag. Do we need to reinstall? No, the flag only writes the registry value. You can push it directly via Group Policy or an Intune remediation script:reg add "HKLM\Software\Fluency\Agent" /v StartHidden /t REG_DWORD /d 1 /f. It takes effect at the next agent launch.
What do users see during rollout? Nothing. The only visible change is a new icon in the system tray.
Support & Contacts
Oliver Farnill (COO) oliver@usefluency.com We will get back to you as soon as possible.Next up: with the agent deployed, workspace admins configure the organization, starting with Setting up Teams.