Invarosoft Deployment Guide

 Everything you need to roll out the ITSupportPanel agent: how to get the installer, how activation and user authentication work, what each error response code means, and how to uninstall the agent.

We deliver the agent installer through a CDN, so you get it quickly and you're always deploying the latest version.

These links always deliver the latest installer:

Use this URL format to download an MSI already named with a client's activation code, so it activates automatically when installed (see MSI file name under Activation during installation).

Activation is the first step after installing the agent. It links the agent to your Invarosoft partner record and to the right client in your partner account.

Each activation code is a 10-character alphabetic value, unique to one client across our entire partner base. Once a code is created and assigned to a client, it never changes.

You can activate the agent as part of the MSI installation in two ways, so you have flexibility when writing your deployment scripts.

Pass the activation code to msiexec.exe with the ACTIVATION parameter:

Include the activation code in the MSI file name. The installer reads it from there:

Run this command against our service executable:

Or with the full path:

Run this command against our service executable:

Or with the full path:

Once the agent is activated, the next step is making sure it's signed in as the right user. Authentication gives each user a personalized experience.

Every agent feature that doesn't need a user works right away, which helps your end users start engaging with Invarosoft. If a user tries a feature that does need identification, they're prompted to register or log in at that moment.

We offer six methods to get your users logged in, each explained below:

Automatically authenticates users when agents run on a network managed by Microsoft Active Directory. It requires setting up the AD Harvester on the network's domain controller.

Once set up, users are logged in automatically, based on the relationship between their Windows user account and their PSA user or contact record. You'll find more AD Harvester resources in the Invarosoft Portal.

Works like Manual Registration (method 3), with one key difference. When the user logs their first ticket, they're asked for their first name, last name and email. If manual registration would have succeeded, the ticket is accepted and a confirmation email is sent to that address asking the user to confirm their identity.

Once the user confirms, two things happen:

1. The ticket held in our system is released to the PSA.
2. An Agent User Assign is run, logging the user into their agent.

Checks the user against the list of users Invarosoft has for that client. The registration email contains what the user needs to enter in the agent's login screen.

We don't recommend this method because it requires more work from your client's users.

In the Invarosoft Portal, use the Assign button under the Users column on the agent screen. The selected user is queued for the agent to pick up.

If more than one instance of the app is running on that endpoint, it works on a first-in, first-served basis. That's why we recommend this method only for agents with a single user profile.

Use the Manage button under the Users column on the agent screen. It opens a list of the users seen on that agent; a user appears there after the agent runs for the first time under their profile.

This method isn't affected by multi-user environments, because the assignment targets a specific user context rather than the whole agent.

Set it on the agent's Edit screen. It forces login as the selected user on every instance of the agent running on that endpoint.

Set it on the client's Edit screen. It forces login as the selected user on every agent activated for that client.

When activation, registration or login fails, the agent shows a response code that explains exactly what went wrong. In most cases you can use it to fix the issue without contacting our support team.

Removes ITSupportPanel but keeps its configuration data. Use it if you plan to reinstall and want to keep the existing configuration.

Or with the full path:

Removes ITSupportPanel and wipes its configuration (activation, etc.) at the same time.

Or with the full path: