Brand the Automox agent tray titlebar on Windows endpoints with a custom organization label up to 20 characters
This Automox Worklet™ writes a custom titlebar label onto the Automox agent tray window on Windows endpoints. The Worklet calls amagent.exe with the notifications set_titlebar_title --text "<value>" argument, which updates the tray UI in place without restarting the agent service. After the label is applied, the Worklet records the configured value in a CSV state file so the next evaluation can confirm the endpoint is still on the branded baseline.
The state file lives at ${ProgramFiles(x86)}\Automox\tray_branding_text_state.csv. It stores a row with Key=titlebarTitle and Value=<your label>, and it is shared across the tray-branding Worklet family so multiple branding values (titlebar, header text, footer text) can coexist in one file. Evaluation parses the CSV with Import-Csv and looks for the titlebarTitle key; if the row is missing, empty, or holds a different value than the configured $TitlebarTitle, the endpoint is flagged non-compliant and remediation runs.
Both phases gate on Automox Agent version 2.5.0 or higher. The agent version is read from the Windows registry under HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* by filtering DisplayName equals Automox Agent. Evaluation exits 0 (compliant) when the version is too old, so older agents are quietly skipped instead of being marked failing. Remediation exits 2 on a version miss to surface the agent-upgrade dependency in Automox activity logs.
End users notice unfamiliar system tray icons, and the default Automox tray reads as a generic third-party tool. That confusion turns into help desk tickets asking whether the application belongs to the organization, whether it is safe to close, and why it is allowed to run. Putting your company name in the titlebar replaces that ambiguity with a recognizable label, which reduces the false-positive ticket volume and reassures users that endpoint management is sanctioned by their employer. The 20-character limit keeps the label readable in the tray notification window across Windows display scaling settings.
Tray branding is also one of the easier surfaces to lose. Image refreshes start the agent with the default label, an agent reinstall after a hardware failure wipes tray_branding_text_state.csv, and a migration between Automox organizations resets the file as part of the re-enrollment. A single unbranded endpoint is enough to trigger a wave of end user tickets asking whether the tray icon is legitimate. The Worklet reads tray_branding_text_state.csv on every evaluation, compares the recorded label against $TitlebarTitle, and runs amagent notifications set_titlebar_title when they diverge, so the configured label is restored after image refreshes, agent reinstalls, and cross-organization migrations without an admin revisiting each workstation.
Evaluation phase: The Worklet reads the Automox Agent version from HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* and exits with a skip message if the version is below 2.5.0. It then calls Test-Path on ${ProgramFiles(x86)}\Automox\tray_branding_text_state.csv. If the state file does not exist, the endpoint exits with code 2 (non-compliant). If the file exists, Import-Csv loads its rows, Where-Object filters for the titlebarTitle key, and the recorded Value is compared against the configured $TitlebarTitle. Any mismatch or missing entry triggers remediation.
Remediation phase: The remediation script validates $TitlebarTitle is not empty and is 20 characters or fewer, then resolves amagent.exe under ${ProgramFiles(x86)}\Automox first and falls back to $ProgramFiles\Automox if the 32-bit path is absent. It invokes amagent.exe with the arguments notifications, set_titlebar_title, --text, and the configured $TitlebarTitle, then checks $LASTEXITCODE. On exit code 0 it writes (or updates) the titlebarTitle row in tray_branding_text_state.csv via Export-Csv -NoTypeInformation -Force, preserving sibling rows for other tray-branding Worklets. Any failure path exits 2 with the amagent stderr forwarded to Automox activity logs.
Windows 10, Windows 11, or Windows Server 2016 or later with PowerShell 5.1 available
Automox Agent version 2.5.0 or higher; older agents are skipped at evaluation
amagent.exe present under ${ProgramFiles(x86)}\Automox\ or $ProgramFiles\Automox\ (the default install paths)
Set $TitlebarTitle to the same value in both evaluation.ps1 and remediation.ps1; mismatched values will cause the policy to remediate on every run
Keep $TitlebarTitle at 20 characters or fewer; longer strings are rejected by remediation with exit code 2
Worklet is FixNow compatible, so the branding can be pushed on demand from Automox console without waiting for the next scheduled policy run
After a successful run, the Automox tray window on the endpoint displays your configured label in place of the default titlebar text. The change is visible immediately without an endpoint restart or agent service restart, because amagent applies the update to the running tray UI override. A new row appears in ${ProgramFiles(x86)}\Automox\tray_branding_text_state.csv with Key=titlebarTitle and Value matching the configured $TitlebarTitle, and any pre-existing rows for sibling branding Worklets (header, footer, icon) are preserved untouched.
Subsequent Automox policy runs report the endpoint as compliant without applying remediation again, because the evaluation phase finds the state file already aligned with $TitlebarTitle. To verify on the endpoint, open the Automox tray icon in the system taskbar and confirm the titlebar reads your configured value; for audit evidence, capture the contents of tray_branding_text_state.csv and pair them with the Automox policy run identifier. If an admin updates $TitlebarTitle in the Worklet, the next evaluation parses the new value, sees the stored CSV row out of date, and the remediation phase runs amagent notifications set_titlebar_title to roll the new label out in a single policy cycle.


Loading...
Consider Worklets your easy button
A Worklet is an automation script, written in Bash or PowerShell, designed for seamless execution on endpoints – at scale – within the Automox platform. Worklets deploy named-CVE mitigations within hours of disclosure, perform configuration, remediation, and install or remove applications and settings across Windows, macOS, and Linux.

AUTOMOX + WORKLETS™
Uncover new possibilities with simple, powerful automation.
By submitting this form you agree to our Master Services Agreement and Privacy Policy
By submitting this form you agree to our Master Services Agreement and Privacy Policy.
Already have an account? Log in