Skip to main content

Manual agent installer should not rely on the filename

Feature Request

When using the manual installer (exe), if you change the file name, the License Key field does not populate.

It would be great if you could download a unique exe per client/location, which has the license key imbedded into the exe itself and just runs the installer without requiring any further user input.

1 comment

Log in to comment and vote

Comments1

  • Mikel from Gorelo

    Team

    Hey mate,

    The reason we have a single universal installer (exe) and just encode the license key in the filename comes down to a few things:

    • Security & trust: Shipping one signed binary means it’s always the same code. If we started distributing hundreds of unique exes, every hash would be different, and that raises red flags for AV/EDR tools. One consistent exe is much less likely to get flagged or quarantined.

    • Simplicity in updates: We only have to build, test, and sign one installer.

    • Audit & compliance: Easier to track what’s running in the field when there’s only one executable. It also keeps SOC2/AV whitelisting cleaner (same hash, same signature everywhere).

    The majority of agent installs will be automated or tech initiated via the PowerShell script so the filename issue will never arise. Not saying this won’t change in the future — just wanted to explain why we chose this approach.

    Cheers,
    Mikel.