Jump to content

ESET server migration


Devender
 Share

Recommended Posts

Hello everyone. 

A new user here..moving the ESET server from an old 2003 server to a new 2012 server. ESET endpoint version 5.3.39.0. Followed article https://support.eset.com/kb2683/ . It looks like while pointing the agents from Server A (old) to Server B(new) , we actually pointed them to Server C ( Which doesnt have any ESET Remote admin server ) . We realized our mistake , changed the setting and can only few agents pointing to Server B ( which I did manually ) . What is the best way to push the config now as they are not pointing to server A or Server B.

Thanks

Devender

 

Link to comment
Share on other sites

  • Administrators

I would recommend to use this opportunity to move to ERA6 since ERA v5 is due to reach its end of life by December 2018. Moreover, v5 Endpoint products do not provide as good protection as Endpoint v6 and may be affected by issues that were addressed in newer versions.

If you don't need to keep the existing db, simply deploy an ERA v6 virtual appliance, generate an agent live installer and install it on a group of clients via group policy. The clients will start reporting to the new ERA then. Both old Endpoint v5 and new Endpoint v6 can be managed with ERA v6.

If you want to keep the existing db, follow the instructions at https://support.eset.com/kb3607/.

How many endpoints do you manage with ERA?

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...