Migrate ERA 5 plugin to Direct Endpoint Management
To migrate from the ESET Remote Administrator (ERA) 5 plugin for ConnectWise to the ESET Direct Endpoint Management plugin for ConnectWise Automate:
Prepare server for uninstalling ESET File Security 4.5
1.In Control Center, install the ESET Direct Endpoint Management plugin for ConnectWise Automate.
2.In ESET Remote Administrator (ERA) 5, create a policy.
a.Click Policy Editor > Add New Policy.
b.In the Policy name field, type a policy name.
c.In the Parent policy list, select BaseUp.
d.In the Policy configuration section, select Create empty policy configuration.
e.Click OK.
3.Double-click the policy from step 2.
4.Expand Windows Server v4.5, locate the Enable Self-defense file, disable Self-defense and then click Console.
|
For Self-Defense to be fully disabled, reboot each server after the server obtains the policy to disable self-defense. |
5.At this time, we recommend you schedule a maintenance window.
6.Select all applicable servers ready for migration, right-click and select Set Policy.
7.Select the appropriate server migration policy and then click Set Policy. The Requested Policy Name column will update to reflect your changes. Policy changes and changes to Self-defense will reflect the next time servers check into the system.
8.Reboot the Server machine to disable self-defense before uninstalling.
Create an uninstall task using ESET Remote Administrator (ERA) 5 plugin for ConnectWise
9.In ESET Remote Administrator (ERA) 5 plugin for ConnectWise, uninstall ESET File Security.
a.Click Deployment > New Task.
b.In the Task Name field, type a task name, select Remove ESET Software and then click Continue.
c.If you have an Advanced Settings password on your severs, type it in the Endpoint Password field and then click Continue.
d.Select the applicable LabTech Group to Target and OS to Target Filter and then click Continue.
e.Click Save Task.
f.After uninstall is complete, reboot servers.
|
The ESET Remote Administrator (ERA) 5 plugin for ConnectWise is no longer needed. |
|
Step 10. is optional. You can use one deployment package for servers and desktops. One deployment package can cover multiple OS versions and automatically deploy the supported product. |
Create a Deployment package in ESET Direct Endpoint Management plugin for ConnectWise Automate (Clean install)
10. In ESET Direct Endpoint Management plugin for ConnectWise Automate, create an installation deployment package for ESET File Security.
a.Click Deployment Packages > Create & Edit and then click Create Package.
b.In the Package Name field, type a descriptive name. In the Product, Language and License drop-down menus, select the appropriate values.
c.Expand Advanced Options. In the V5 Upgrade Handling drop-down menu, select Do Nothing (Default).
d.In the V6 eRMM drop-down menu, select Warn Only (Default).
e.An Access Setup Password is required for every deployment package. Click Set.
|
Set a password. There is no default password to be used if you type no password. |
f.In the Password and Confirm Password fields, type a secure password and click OK.
g.Click Save.
How can I deploy the ESET Management Agent using the deployment package?
Create a Deployment package in ESET Direct Endpoint Management plugin for ConnectWise Automate (Upgrade from an earlier version/resolve missing eRMM settings)
11. In ESET Direct Endpoint Management plugin for ConnectWise Automate, create an installation deployment package for your ESET endpoint product.
a.Click Deployment Packages > Create & Edit and then click Create Package.
b.In the Package Name field, type a descriptive name. In the Product, Language and License drop-down menus, select the appropriate values.
c.Expand Advanced Options. In the V5 Upgrade Handling drop-down menu, select In-Place Upgrade.
d.In the V6 eRMM drop-down menu, select Uninstall, Reinstall.
e.An Access Setup Password is required for every deployment package. Click Set.
|
Set a password. There is no default password to be used if you type no password. |
f.In the Password and Confirm Password fields, type a secure password and click OK.
g.Click Save.
How can I deploy the ESET Management Agent using the deployment package?
Create a Deployment task in ESET Direct Endpoint Management plugin for ConnectWise Automate (Servers)
12. Use ESET Direct Endpoint Management plugin for ConnectWise Automate to reinstall ESET File Security version 7.
|
Do not install ESET File Security version 7 over ESET File Security version 4.5 for any reason. |
a.Click Overview > Computers, select the computer(s) that require a ESET File Security installation then click Deploy ESET.
b.In the drop-down, select the installation deployment package you created in step 10 and then click OK.
Create a Deployment task in ESET Direct Endpoint Management plugin for ConnectWise Automate (workstations)
13. Use ESET Direct Endpoint Management plugin for ConnectWise Automate to setup an automatic deployment for your ESET endpoint products.
c.Click Deployment Packages > Create & Edit.
d.Select the endpoint product deployment package you created in step 11 and then click Setup Automatic Deployment.
e.Expand the Groups and Clients & Locations trees, select the applicable groups, clients and/or locations and then click Save. Automatic deployment is successfully setup. Deployment will automatically begin when a device joins the target client, group, or location.
f.After uninstall is complete, reboot workstations.
|
If you upgrade from a previous version to version 7 of ESET endpoint products, a post-installation reboot is necessary. |
14. Due to the significant change in software architecture to facilitate a non-ERA setup, the options below are the only options currently available for handling policy migration.
•ESET File Security: During the process above, you installed a clean version of ESET File Security. No policy migration options are available. Create a policy.
•ESET endpoint products: Update all workstations to the appropriate ESET endpoint product version 7 software. After the update is complete, export all existing policies (locally or from Automate) and then import the policies into the plugin.
Migration is complete.