BenjaminMH
-
Posts
18 -
Joined
-
Last visited
Posts posted by BenjaminMH
-
-
This is helpful, thank you.
I assume you're referring to Policy Settings>User Interface>Application Statuses>General and disabling showing of "A computer restart is required?"
-
In Windows 10, after an upgrade to Endpoint AV 6.6 has been completed, users receive a toast notification with a red X that states "Your system is exposed to risk" that stays on the screen for ~5 seconds. Clicking the notification brings up the ESET GUI with a message that the product has been upgraded and a restart is required.
Is there any way to make this notification less intrusive? In previous versions, it would be a yellow warning pop up that says "ESET requires your attention" which is generally less alarming. It's harder to do silent upgrades in the background when it triggers an alarming message.
Thanks for any thoughts.
-
Is the seat always supposed to deactivate during an upgrade? Or should it preserve the seat?
The batch of computers I sent an upgrade task to that do not have a license seem to have kept their seats.
-
4 hours ago, MichalJ said:
In general, the ELA knows, that it is the same machine. However, during the upgrade process, the previous seat instance was not correctly deactivated (means, that there might be an issue on our side, as during standard de-installation, the application should send "deactivation" response to ESET licensing servers. In your case, it looks like it was taken as a new entry, however with the same HWF. You can send me a PM, with the details, like full seat name, PLID of your license, and approximate time of this upgrade so we could further investigate, and confirm, that is the problem. Thank you.
I went through and cleaned out the duplicates from ELA. I can upgrade a few more with my original method to get you some examples and report back.
-
1 minute ago, MartinK said:
It should not behave like this, but maybe license has changed since you installed previous version? @MichalJmay be able to confirm what is expected behavior.
The license has been updated with a new expiration date, but the key itself is the same. As long as the software stays activated during the upgrade, this should work just fine.
-
1 minute ago, MartinK said:
When you created mentioned ERA task (I guess it is software installation task), have you specified license? Selecting license will instruct ERA to activate product once it is installed (or upgraded in this case) - maybe that is reason for this behaviour.
Yes, there is a license as part of the software installation task. I double checked previous install tasks, and they also have a license specified, so I'm not sure why I'm just running into this issue.
Your answer makes sense, though. I've been using the same task to install the client on new machines as the one to upgrade, so I'm sure that's where the issue lies. Thanks for the quick answer!
-
I've been upgrading clients on Endpoint Antivirus from 6.4 to 6.5 through an ERA task, and I've noticed that in most cases, a new licence seat is created when the upgrade takes place.
I'm having to go into ELA and delete out duplicates, as it does not seem to preserve/automatically relinquish the upgraded seat.
See attached example. Both entries are the same machine. The bottom one is the original licence, and was activated back in 2016. On 6/12, we upgraded to ESET, and it created a new seat for it.
I've never had this issue before when upgrading - anything I need to check?
-
It looks like this issue is being caused by a component of the LogMeIn software we have on computers.
wa_3rd_party_host_32.exe which is a component of OESIS that polls client AV software for status information appears to be hanging and has the ESET eScan directory open.I have an open support ticket with LogMeIn -
5 hours ago, Marcos said:
Please generate a Process monitor log during installation and also collect logs with ELC as per the instructions linked in my signature.
When done, compress the pml log, upload it together with ELC logs to a safe location and pm me download links.
Working on it. It seems like if you reboot the machine after the the failure, and then try to reinstall, it works. Trying to replicate the issue on another machine that I have access to.
-
When trying to update from ESET Antivirus 6.4 to 6.5 through ERA, I am seeing the following error on some (but not all) installs.
At this point, it has stripped the previous version of ESET, but fails to complete the installation of the new version, leaving the machine unprotected.
SoftwareInstallation: Installation failed with: (0x643), Fatal error during installation (0x643), The installer has insufficient privileges to access this directory: C:\ProgramData\ESET\ESET Endpoint Antivirus\Logs\eScan. The installation cannot continue
-
Endpoint Antivirus 6.5.2094.0 on Windows 10 Pro
When unlocking my computer after being on the lock screen for an extended time, in addition to ERA indicating that the machine is in presentation mode, a very brief "ESET Requires Your Attention" notification will appear on the bottom right.
Clicking it yields nothing, and the message is not displayed for more than a second or two, but it is nonetheless a little distracting.
-
2 hours ago, BenjaminMH said:
Endpoint Antivirus 6.4.2014.0
Word file on a network share.
When trying to export or save it as a PDF, ~1/4 times you'll get a message that says "This file is in use by another application or user" and the save fails. Occasionally, it will happen multiple times back to back, other times it's sporadic.
When pausing ESET on the client, I'm unable to reproduce the issue. I've tried the exact same process 32 times with ESET disabled, and I have not seen this error.
I separately tried disabling document protection in AV, but I still experienced the issue.
Any ideas, thoughts, suggestions?
It looks like disabling "scan on file creation" on the local machine may resolve the issue, although that isn't exactly something I'd want to disable...
-
Endpoint Antivirus 6.4.2014.0
Word file on a network share.
When trying to export or save it as a PDF, ~1/4 times you'll get a message that says "This file is in use by another application or user" and the save fails. Occasionally, it will happen multiple times back to back, other times it's sporadic.
When pausing ESET on the client, I'm unable to reproduce the issue. I've tried the exact same process 32 times with ESET disabled, and I have not seen this error.
I separately tried disabling document protection in AV, but I still experienced the issue.
Any ideas, thoughts, suggestions?
-
Using ESET Endpoint Antivirus 6.4.2014.0
We occasionally run into issues where a scheduled scan is significantly impacting system performance. What is the best way to cancel an active scan?
I only see the cancel option when the scan has been initiated from the client itself, not from a scheduled scan.
Thank you
-
Gotcha. Thanks for the quick and detailed answer.
-
I recently have cleaned out 20-30 old computers from ERA, but noticed that the count of units used has not decreased on the License Management page.
The number of licenses it says are used greatly exceeds the number of machines I have connected to ERA. Currently on v6.3 across the board, and the licenses in question are for Endpoint AV for Windows.
I have not had a problem with this in the past. I've also tried synchronizing the license count several times, but nothing changes.
Any suggestions/known issues?
-
I've noticed that when certain sites are blocked by the HTTP filter, ERA will flag it as a critical threat, and under action error, lists "Unable to clean."
The "object type" says file, but the "object URI" lists a web address instead of a file path. So, what is it trying to clean?
This event often occurs along with an actual file that has successfully been cleaned/deleted.
What is the appropriate way to deal with these events? I believe in v5, it used to say something along the lines of "connection terminated" and it would only show as an informational alert.
Thanks for your help!
ESET ERA 6.2
Endpoint Antivirus 6.2
6.6.2068 vanishes from the repositoy during upgrade
in ESET PROTECT On-prem (Remote Management)
Posted
I'm with you on this. Same thing happened to us.
Spend time testing, begin rolling out, only to have the package disappear. Process starts over from scratch, and now we have machines on inconsistent versions.