Jump to content

IT Professional

Members
  • Posts

    5
  • Joined

  • Last visited

About IT Professional

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Canada
  1. I got this link from ESET tech support. hxxp://support.eset.com/zap/kb3701/ By doing a "repair" for the ESET Remote Administrator Agent you can change the ERA IP address Also this link will help in case you want to create a new Policy for ERA Agent to connect to the new ERA Server hxxp://help.eset.com/era_admin/63/en-US/index.html?admin_pol_planed_for_migration.htm
  2. It makes sense. Thank you for your replies. Maybe ESET will add this feature back in the next release so we don't have to redeploy the agent because of an IP change.
  3. I'll change the current policy and add a second IP address to the server list so I don't have to worry about "roaming" laptops. I still have to connect the existing laptops to our network so I can update the agent policy. Thank you
  4. This sucks. What if for some reasons I have to change the ERA server IP and I have 200 clients already deployed? Why do I have to reinstall the agents instead of changing the IP address like in the previous versions? The IP address has to be somewhere in a configuration file or maybe in the Windows registry.
  5. The following link shows the setting for the old version of the ESET Endpoint security hxxp://support.eset.com/zap/kb2716/ Any idea where is this setting in the new version of the client workstation? I have a laptop that has an internal IP address and now has to connect to a "external IP" using a proxy server in DMZ. I can't bring the laptop back (or connect it to the VPN) to deploy a new policy. Can I edit the policy on the ERA server and add another IP address to the server list so I don't run in this problem again? Thank you
×
×
  • Create New...