Download and import plugin scripts

To deploy ESET Direct Endpoint Management plugin for N-able N-central, download and unpack the ESET-provided script bundle. When unpacked, import provided Automation Policies (tasks) and Custom Services (monitoring) script files into N-able N-central.

Download script bundle

1.Visit the ESET plugin download page and click the Download button. You will download a script bundle in a .zip file.

2.Unpack the .zip file.

3.Explore the unpacked package that contains folders with Automation Policies (tasks) and Custom Services (monitoring) scripts for Windows and Automation Policies (tasks) scripts for macOS.

Proceed and import these script files into N-able N-central.

Import Automation Policies (tasks)

1.Click Configuration > Scheduled Tasks > Script/Software Repository.

2.Click Add > Automation Policy > Browse to import .amp file:

Automation Policies for Windows	Description
ESET – Custom Property Refresh.amp	A specific Automation Policy to update the device level custom properties on a reccurring basis. To be scheduled during plugin setup.
ESET – Onboard Task.amp
ESET – Offboard Task.amp
ESET – Activate Task.amp
ESET – Deactivate Task.amp
ESET – Scan Task.amp
ESET – Update Task.amp
ESET – Configure Task.amp

Automation Policies for macOS	Description
eset_dem_plugin_ncentral_macOS.sh	General-use script that enables the administrator to call Emma commands. ermma commands.

3.Click OK to finish importing the file. Repeat the steps for each file.

4.When you import all your Automation Policies, they will be visible in the Configuration > Scheduled Tasks > Script/Software Repository.

Import using Automation manager

Alternatively, upload Automation Policies (tasks) script files using Automation Manager into the Script/Software Repository.

Import Custom Services (monitoring)

1.Click Administration > Service Management > Custom Services.

2.Click Import.

3.Click Browse to import .xml file:

Custom Services	Description
ESET – Activation Status Monitor.xml	Runs every 30 minutes. Indicates failed if the result does not contain "ESET Product Activated".
ESET – Installation Status Monitor.xml	Runs every 15 minutes. Indicates failed if the result contains "ESET Product Not Detected".
ESET – Protection Status Monitor.xml	Runs every 15 minutes. Indicates failed if the result does not contain "Ok".
ESET – Scan Log Status Monitor.xml	Runs every hour. Indicates failed if the result contains "New Scan Alerts". on whether a real-time scanner detects an infected item.
ESET – Threat Log Status Monitor.xml	Runs every 10 minutes. Indicates failed if the result contains "New Threat Alerts". The result depends on whether a real-time scanner detects a threat.

5.Click Import Custom Service to finish importing the file. Repeat the steps for each file.

6.When you import all Custom Services, they will be visible in the Administrator > Service Management > Custom Services.

˄˅