TheSkymanDC

Marcos - I get the above window saying "I want to purchase a new license"

And here's a pic of the activation problem

And here's a new twist. Was able to deactivate via ELA. I am unable to reactivate. The install task from yesterday says it's still running and the activate task from ERA will not run. When I try to activate manually I click on "Activate this product" - it just gives me a window that says "I want to purchase a new license".

Nope. Not on this one. I think the Activation task is confused on the server. It's stuck on running. I've just successfully tested the ELA deactivate - reboot - ERA activate on a different workstation. That one worked fine. eset needs to quickly give use a better solution.

1. Deactivate via ELA. 2. Activation task from ERA never finishes. I am able to manually activate from the workstation. That's going to be painful.

Add me to the list of folks that have this problem. A couple of dozen computers show this error after upgrade via ERA. Client task activation made no change. An easy fix would be greatly appreciated.

Thanks all for the info!

Cool! Thanks!

What about more minor updates - like 2052 to 2064?

Is there a schedule or frequency for endpoint or agent version updates? (Not referring to A/V definitions) Knowing this will help us plan for update installation. Thanks!

We have several computers that show in the Remote Administrator Console as having not connected in a long time. When you check the computers they show that they have indeed connected and everything is up to date. Additionally the ELA console show them as connected today. Any idea how I can reconcile the endpoints with RA console correctly? Thanks!