Jump to content

Trooper311

Members
  • Posts

    40
  • Joined

Posts posted by Trooper311

  1. Hi everyone,

    So I upgraded two endpoints today from version 6.6.2086.1 to 7.0.2073.1.

    Both are showing errors on both the console and the endpoint that Web Control is non-functional.  (See attached pic).

    Also if you go to the update portion no update has been run, (see attached pic). 

    It states that the Product is not activated when indeed it is.  I even sent an activation task to the endpoints to no avail.

    Thoughts on this one folks?

    Thank you in advance.

    P.S. Both machines are Windows 7 x64 Enterprise Edition and are fully patched.

    error.PNG

    error1.PNG

  2. 2 minutes ago, MartinK said:

    Unfortunately this is issue we are currently investigating and working on remediation. What actually happens that ERA Agent successfully upgrades to ESMC Agent, but for some reason, remnants of original application are not properly removed from registries (msiexec database). It has no impact on functionality, but it is confusing, especially in case ESMC reports it as outdated software is present on client machine.

    We will most probably provide at least script that cleans those registry entries, until proper fix is available.

    Thanks Martin I appreciate it.  Please keep me posted.  For now, I am going to halt the rollout until some of these kinks are sorted out.

    Cheers!

  3. 5 minutes ago, Marcos said:

    Thanks. Since the issue with Web Control is most likely related to Endpoint and to avoid discussing different issues in this topic, please create a new topic in the Endpoint forum and provide a screen shot or two with the errors that you are getting. I've checked the logs you've supplied and there was no mention of an error neither in ESET's event log nor the system log.

    Thanks Marcos.  I will do that.

    Cheers!

  4. 5 minutes ago, MartinK said:

    I would recommend to check standard client task view, where you will see basic statistics of planed/finished and failed installations (see relevant documentation article). In case failure will be reported, it is possible to drill down for more details.

    Regarding old version uninstallation: ERA Agent v6 will be upgraded to ESMC Agent v7 without uninstallation as it is actually considered as application upgrade. All settings will be applied after upgrade and identity of device in console will be the same.

     

    Hi Martin,

    Thanks very much I will look at the documentation.  However this is what I am seeing after sending the upgrade task to an endpoint.  That is why I was asking about the uninstall of the old version.

     

     

     

    Capture.PNG

  5. 48 minutes ago, Marcos said:

    It can be either an issue registering a WFP callout (e.g. due to issues with BFE or registry permissions), or you disabled protocol filtering which is now indicated by a change of the protection status. Please provide me with logs collected with ESET Log Collector from such machine so that I can check the configuration.

    Will get you the logs ASAP.

     

    Just finished upgrading my server to ESMC.  So far, so good.

    Where do I find the ESMC component upgrade task for clients?

  6. Hi everyone,

    I have a few guinea pigs at my job who I installed the upgrade to.  A few Windows 10 Users and a few Windows 7 users.

    Windows 7 users currently have installed:  ESS -  7.0.2073.1 and ESET Remote Administrator Agent 6.5.522.0 

    Both of these users have alerts on my ERA 6.5 Console of Web Control is not Functional. (Tried sending an update from the ERA console but no chance is made.)  Also see errors on both endpoints.

    Windows 10 User have ESS -  7.0.2073 and  ESET Management Agent 7.0.553.0 installed. (Only one user (me has this).  I only have the updated Agent since I saw it appear today in my ERA 6.5 console.

    Off the bat after reboots I have an error message on the endpoint that the firewall is not enabled, which is true because I do not use the ESET firewall here at work. Console not showing any errors.  I did manually turn it on (at the endpoint) and back off and the error seems to have gone away.  Do not want to have this issue for all my users so gonna go slow with this rollout.

    Also, even though I have ESET Management Agent 7.0.553.0 installed the ERA 6.5 console is still stating that I am out of date and have ESET Remote Administrator Agent 6.5.522.0.  So it is not reporting correctly.

    In addition, in my policy I have the license information hidden.  However on Windows 7 endpoints it is hidden, but on Windows 10 it is not.  I am running Windows 10x64 Enterprise v1709 with all the latest patches.

    Are there any fixes for this yet?  Or do I need to upgrade to version 7 on my server?

    Please advise.

    Thanks!

×
×
  • Create New...