Branded agent and installers
Get agent packages in a customer's brand from Devices > Installers, and see what the agent shows on their devices: Apps and features, the tray, the consent prompt and the session indicator.
The agent on a customer's devices wears that customer's brand profile: its name, publisher, icon, colour and support details. The people using those computers see your product, not Tenvara.
How branding reaches the agent
Every Tenvara program is code-signed (Authenticode on Windows, Developer ID and notarisation on macOS). Changing a signed file would break its signature, so a brand never changes the signed files. It is applied beside them:
- At install time, by a Windows Installer transform (an MST file) made for the customer's brand, so the installer and Apps and features show your name from the start.
- At run time, by the agent itself, from the brand your server sends it on every connection.
When you change a profile or move a customer to another profile, connected agents pick up the new brand within moments: the tray, the prompt and the indicator change without a reinstall or a restart. An agent that is offline keeps the brand it last had and starts with it, then checks for changes when it reconnects.
Getting packages for a customer
- Open Devices > Installers.
- Under Packages for a customer, choose the customer.
- Tenvara shows the agent name, whether it is a Customer brand or the Default brand, the brand colour and the company it is published by.
- Use Get an install command for the one-line command with an enrolment token, or download the packages for a deployment tool.
Windows
| Download | What it is |
|---|---|
| Bundle (ZIP) | The signed MSI, the brand transform and install.cmd, ready to run with an enrolment token |
| Signed MSI | The standard signed package, unchanged |
| Brand transform (MST) | The customer's brand, applied on top of the MSI at install time |
For Intune, Group Policy or a script, install the MSI with the transform. The page shows the exact msiexec command to copy: the MSI, TRANSFORMS= with the MST, a quiet install, your server's address and a placeholder for the enrolment token.
In Intune, use it as a Win32 or line-of-business app's install command. In Group Policy, add the MST on the package's Modifications tab. The one-line PowerShell command from an enrolment token downloads the MSI and the customer's transform and installs both.
macOS and Linux
The page gives the signed package or archive and the customer's Brand file. The one-line installer puts the brand file in place before installing, so the agent starts in the right brand. On macOS, an MDM can place the brand file in the location shown on the page before it installs the pkg.
Note: A transform is made for each release and each version of the brand, so after you change a profile or upload a new release, download the packages again for new installs. Agents already installed update their brand on their own.
What changes on a Windows device
| Place | Changes with the brand |
|---|---|
| Apps and features | The name, publisher, icon, support link, phone number and contact |
| The Windows service | Its display name and description |
| The installer | Its windows and messages, including the product name |
| The tray | The name, menu, tooltip, About, dialogs, notifications and the chat window's title |
| The tray icon | The profile's square mark, when it has one |
| Remote control consent prompt | The title and question, for example "Clearwater Hub remote support" and "Sam Carter from Clearwater IT would like to connect" |
| "Being viewed" indicator | The text and colour shown during a remote session |
The agent rewrites the Apps and features entry and the service name each time it starts and whenever the brand changes, so they stay right after an upgrade.
What stays the same
Some details are inside the signed files and do not change with a brand:
- The file details of the programs themselves (Explorer's Details tab, the process descriptions in Task Manager) still name the Tenvara Agent.
- The MSI and pkg files, their signatures and file names.
- Install folders, the service's short name, registry keys and log paths. These are identifiers rather than names people read, and changing them would break upgrades.
Agent name and support details
The agent's name comes from Agent name on the brand profile (empty means your product name followed by "Agent"). The publisher is the profile's Company name, and the support link, email and phone come from the Customer portal, emails and chat card. See Brand profiles.
Related: Installing the agent, Remote control, Agent updates and release channels.
Was this page helpful?
Thanks for the feedback.