Marcos
-
Posts
36,189 -
Joined
-
Last visited
-
Days Won
1,440
Posts posted by Marcos
-
-
I recall that technical support has a batch file that removes older versions of agents and has all GUID included. Please raise a support ticket.
-
We kindly ask you to reproduce the issue while capturing the network communication with Wireshark and advanced network traffic scanning enabled at the same time in the advanced setup -> Tools -> Diagnostics:
After reproducing the issue, please disabled advanced logging and only then collect logs with ESET Log Collector.
-
We kindly ask you to reproduce the issue while capturing the network communication with Wireshark and advanced network traffic scanning enabled at the same time in the advanced setup -> Tools -> Diagnostics:
After reproducing the issue, please disabled advanced logging and only then collect logs with ESET Log Collector.
-
Please follow the instructions at https://help.eset.com/ecs_mac/7/en-US/allow_full_disk_access.html:
MacOS Monterey (12) and older
1.Open System Preferences.
2.Go to Privacy tab and select Full Disk Access from the menu on the left.
3.Click the lock icon at the bottom left to allow changes in the settings window.
4.Use your Touch ID or click Use Password, type your User Name and Password, then click Unlock.
5.Select ESET Cyber Security from the list.
6.A restart ESET Cyber Security notification will display. Click Later.
7.Select ESET Real-time File System Protection from the list.
If the Real-time File System Protection option is not available, you must allow system extensions for your ESET product.
8.Click Start Again in the alert dialog window to restart ESET Cyber Security and reflect the changes, or restart your computer. For more detailed information, visit our Knowledgebase article.
MacOS Catalina is not supported by ESET CyberSecurity v7. As for v6, limited support ended on February 15 and the product is now EOL: https://support-eol.eset.com/en/policy_home/product_tables.html
-
It is not necessary to send a "Check for product update" task. The endpoints will check for module and product updates automatically in 1 hour interval by default and download them, if available and allowed by the auto-update policy.
The "Check for product update" task is useful when an admin wants to force upgrade to the very latest version shortly after the release when throttling is active and upgrade is not offered to everyone instantly.
-
What about sending a "Check for product update" task? It should upgrade Endpoint the the highest version allowed by the auto-update policy:
-
2 hours ago, ShaneDT said:
So going back through all of this, my only option to update from 10.0 versions to 10.1.2063 is to use Software Install.
Why? The requirements for "Stop update at" feature are as follows, ie. for Endpoint for Windows it's => v9.0:
-
There is a handful of default EEI reports that you can edit or create your own:
-
This probably happens because another Bing application was installed in the past (e.g. Bing Wallpaper). Do you remember allowing installation of such application? Isn't there a way to avoid downloading the above file? When is the detection triggered?
-
Here's what drives cybercriminals to relentlessly target the personal information of other people – and why you need to guard your data like your life depends on it
-
It's a kind of an anti-cheat application. We're going to remove the detection for now but it may be detected later as a potentially unsafe application which is optional detection.
-
While you may occasionally receive an EPNS error, it should not occur always. Moreover, we are working on an ultimate solution so that the errors never occur. Since the error always occurs for you, I assume there will be a communication problem with the EPNS servers, hence I'd recommend raising a support ticket if the issue is not resolved automatically this week.
-
You can use the following vulnerability information in PROTECT reports:
-
I confirm, it appears to be a false positive. The detection has been removed. In the mean time, you can create a detection exclusion to prevent the files from being detected.
-
You wrote that the original server certificate was about to expire. If it has already expired in the mean time, restoring it won't help. Wouldn't it be easier just to re-deploy the management agent on those machines using current certificates?
-
If there were problems downloading updates and they were not caused by a firewall blocking the communication, it it very likely that also all other software would have problems with update. Anyways, you wrote that the issue was resolved by replacing the modem so there are no issues to investigate any more.
-
9 hours ago, RobertEDS said:
This is the most common result on 99.99% of scan with cleaning in eset protect cloud. I have hundreds of end points in protect cloud and we do monthly scans with cleaning on them. Almost always results in detections retained. Constantly I see folks here saying it is due to scan without cleaning but this is not true. Would be nice to see this issue actually addressed by eset. It is annoying. The things detected are real problems and should be cleaned especially when the task is scan with cleaning.
Please raise a support ticket. A detected file can be retained also in case when it's a driver that is always loaded at system startup.
-
The update servers are located in EU and US. The closest should be selected automatically.
-
Make sure to creat the mirror with the same version of Endpoint as those that update from it. Or use the mirror tool to create the mirror for different versions of Endpoint.
-
Odporucil by som presunut vlastne pravidla, s ktorymi mate problem, nad defaultne pravidla. Podla konfiguracie pravidla pre svchost maju prioritu 63 a 64. Okrem toho namiesto aplikacie svchost.exe pouzite servis "Windows update":
Ak by problem pretrvaval, postupujte, prosim, nasledovne:
- odinstalujte ESET
- nainstalujte ESET Internet Security v17.1.9 bez importovania predchadzajucich nastaveni
- vytvorte prisludne fw pravidla podla odporucani vyssie
- zapnite pokrocile logovanie pod Help and support -> Technical support
- zreplikujte problem
- vypnite logovanie
- poslite logy z nastroja ESET Log Collector
- kontaktujte technicku podporu s popisom problemu a dodajte im ELC logy -
2 hours ago, ShaneDT said:
If I create a Common Features policy with Stop Updates At set to 10.1.2063 for ESET Endpoint for Windows, assign this to all groups with Windows computers, then run the "Check for product update" tasks on these computers, they should all upgrade to 10.1.2063 only, there is no risk of this triggering an update to v11. Correct?
That's correct.
-
12 minutes ago, ShaneDT said:
I've never even looked at Common Features policy before. You guys make this stuff so incredibly complicated....
It's one of very few settings common for all products, hence it's available as a separate "product".
-
6 minutes ago, byxil said:
No it doesn't work like that either, I've given up and to get the ping I need for my automations, I have to keep network traffic disabled.
Please provide logs collected with ESET Log Collector as per the instructions in my post above.
-
2 minutes ago, ShaneDT said:
Why did all my posts get deleted?
I moved the discussion to https://forum.eset.com/topic/40559-controlling-product-auto-updates/#comment-182410 since this topic is not intended for discussions.
Unistall Agent with command line
in ESET PROTECT On-prem (Remote Management)
Posted
Yes, if you raise a support ticket, further communication with technical support is typically via email.