What does the agent do?
In a nutshell, the SuperOps agent installed on your client's device establishes a deeper connection between the admin and the endpoints in their network. It gives technicians more control over their endpoints and helps them keep devices running smoothly and remotely. What the agent does is communicate with the admin console and send vital information about the asset that keeps technicians informed about the status of the assets, who can then perform actions to course-correct and remotely fix the issues.
Now that we know what the agent does, let's take a look at how you can download the agent to install on your client's assets.
How to download the SuperOps agent
To install agents for a specific client, you'll need to select the client and the site for which the agent is to be deployed, and SuperOps will auto-generate agents that are unique for that specific site and client.
📝 Note:
If you've just started using SuperOps, you'll need to create a client and a site to generate the agents. The agents won't be visible for any existing demo data in the system.
To create a client:
Click the ‘Create’ button on the pane to the left. Under ‘Create’, select the ‘Client’ option.
Inside the create new client page, enter all the information you have about the clients in the corresponding fields.
📝 Note: Do not use the same email address with which you have logged in as a technician. Enter the email ID of the client in question. Just a quick heads up, since it's easy to get confused between the two fields, especially if you're adding a client for the first time.
Once done, click ‘Save’ to finalize the information and add the client.
Now that the client has been added to SuperOps, you can download the agent to install on the client's devices. You can download the agent for the client through two sources:
Under the specific site for each client: Click the Modules icon on the pane to the left, and open the client module. Inside the client module, open the particular client, and switch to the site section on the right. Here, under each site, you'll find the agents available for the site for both Windows and Mac devices.
From the asset management page: Click the ‘Modules’ icon on the pane to the left, and open the ‘Asset’ module under asset management.
Inside the Asset module, you'll find a download agent button at the top right of the screen. Click the button, and then choose the client and site. Once you do, the agents for both Windows and Mac devices for the site will be generated.
Once you have downloaded the corresponding agents for the devices, you are all set to deploy them by installing them in your assets and start monitoring them.
These are the types of agents currently available in SuperOps:
An MSI installer for x64 CPU architecture for Windows devices.
An MSI installer for x86 CPU architecture for Windows devices.
A package (.pkg) installer for Mac devices.
Agent requirements
Here are the OS versions that the agent supports:
Windows: Windows 8.1 and newer, Windows 2012 R2 and newer
.Net: 4.7.2 and newer
macOS: 10.15 and above
Prerequisites for downloading the agent in your asset:
For Windows devices,
PowerShell and WMI must be enabled on your device, and the SuperOps agent must be granted the required permissions to access them.
Administrator privileges must be granted for the agent to enable MSI files.
For Mac devices,
Full disk access and screen recording permissions must be enabled for the SuperOps agent.
To do that, Navigate to System Preferences > Security and Privacy > Full Disk Access, and select superops and updmgr.
Setting up full disk access
Go to Settings on your Mac device.
Click "Privacy and Security" > "Full Disk Access."
Enable SuperOps and Splashtop Streamer as shown below.
Enabling Splashtop for RMM:
Navigate to Settings > Privacy and Security > Accessibility.
Enable the Splashtop streamer as shown below.
Enabling screen recording permissions:
Go to Settings > Privacy and Security > Screen Recording.
Enable SuperOps and Splashtop Streamer as shown below.
Ensure that any antivirus software or firewalls on the asset don’t block the SuperOps agent. You can do so by whitelisting the following URLs used by the agent to download script module files and auto-updates:
wss://ws.superops.ai/*
SuperOps should have the permissions needed to execute a script from the default folders.
📝 Note: Do not rename the .msi and .pkg agent files, as the system will not be able to recognize the installed agent on the client's device if the name is changed.
💡 SuperTip: The copy option copies the URL of the agent to the clipboard, which can be used in scripts to deploy agents.
Click here if you'd like to see how to deploy the SuperOps agent silently using scripts.