This document and guide will assist you in configuring the Endpoint Manager Integration with Naverisk. This integration allows you to install endpoint managers on managed devices. This is currently for the ESET AV Suite only and further integrations are in development.
IMPORTANT (Please read and note)
In its current version (2023 R1.2), an ESET license will always be purchased when every ESET installation is triggered from the Naverisk application. (OS template or device-specific template).
1.0 Prerequisites
ESET endpoint manager is currently (as of Naverisk 2023 R3) only available to devices running Windows 10, Windows 11, and Windows Server 2022 operating systems.
2.0 How to setup endpoint manager integration
Please follow the below steps to set up the integration and initial connection.
Navigate to Settings > Endpoint Security
Click on an endpoint manager's dedicated tab to start the authenticating process
In the setup section, enter your MSP administrator URL, account management username, and account management password in the corresponding fields
Click the integration-enabled checkbox.
Click the SAVE button
Once connected, the integration sync will start. This will then pull all available plans which will populate in the Plans section and ESET clients will be displayed in the Client section.
Use the client mapping section to link corresponding clients. A Naverisk client which exactly matches an ESET client will be automatically mapped and given the auto-mapped status.
You can also Click the Edit button to manually match the client.
Please Note: Clients already mapped in the ESET integration of another client will be disabled as clients can only be mapped once.
3.0 How to allocate endpoint managers
3.1 OS template
Operating System Templates are configured for the monitoring aspects of your Devices, such as CPU, RAM and Disk performance, Agent Availability, Device Security, Services, Processes, Ports, and Events. To see more on OS templates please refer to this KB Article http://kb.naverisk.com/en/articles/2814259-os-alert-templates
To activate the within the OS template please follow the below steps,
Go to the Settings page
Click on the OS Template icon
Select a client already matched in the Endpoint manager integration
Click the New Template button or open an existing OS template
Go to the Security Center section of the OS template document
Select your preferred endpoint manager
Select the plan you want to associate with this OS template
Tick the Antivirus, Disabled, and Outdated checkboxes
Click the SAVE button
Once completed the above follow the next few steps to activate.
Go to the Device grid
Select a client already matched in the Endpoint manager integration
Select a device (Windows OS only)
Go to the Monitoring tab of that device
Click on the OS template field
Select an OS Template
Click the SAVE SETTINGS button
3.2 Device-Specific Template
Go to the Device grid
Select a client already matched in the Endpoint manager integration
Select a device (Windows OS only)
Go to the Monitoring tab of that device
Click on the OS template field
Select the Device Specific Template option
Go to the Security Section
Select your preferred endpoint manager
Select the plan you want to associate with this OS template
Tick the Antivirus, Disabled, and Outdated checkboxes
Click the SAVE SETTINGS button to start installing and monitoring the selected endpoint manager
4.0 Endpoint Manager installation
Once an endpoint manager has been assigned to a device, the following will happen:
The online device will get the change immediately
An offline device will get the change when they reconnect
Please note: The following scenario will occur when a Windows desktop or a Windows Server device is already running a different AV Product.
When online and already running Windows Defender, the ESET installer will run and replace the running antivirus software,
When online and already running a 3rd party endpoint manager, the ESET installer will not run and the running antivirus software will need to be removed first,
Please note: The ESET installer will attempt to install up to 5 times before returning an error message. Three times at 10 minutes interval and then, twice more, 24 hours apart.