BradAtkins
-
Posts
12 -
Joined
-
Last visited
Posts posted by BradAtkins
-
-
Hi all,
We have ESET Endpoint Security on Windows 10. Managed by ESET Protect Cloud.
We have App Developers who need to use NodeJS and JavaScript. Can anyone tell me what I need to do to make sure they can work? I prefer to use policy applied to their group if possible.
This error pops up on the developer's screen:
This is what I see in the cloud manager:
I've tried adding a couple things to a policy that's applied to that computer group:
Added C:\SourceCode\* to a performance exclusion in Detection Engine area.
Added the C:\Sour....\esbuild.exe to Processes to be excluded from scanning in Real-time file system protection area.
The next time he tried to add another package, he got the error again.
Anybody know what I'm doing wrong?
-
5 hours ago, veehexx said:
Is this still an active issue, as we're seeing the problem and not got some of the updates (still in pre-release channel?) that have been mentioned.
It looks like Direct Cloud communication module 1123.2 is still in pre-release. Will that be moved to the regular update channel any time soon?
-
8 hours ago, Peter Randziak said:
Hello guys,
LiveGrid communication module 1123.1 is available on pre-release update channel.
If you do not use the proxy try to switch to pre-release updates, confirm that LiveGrid communication module bas been upgraded to version 1123.1 and let us know if it resolved your issue, even if you have License Interval Check set to limited.
Peter
That works for me.
Thanks!
-
-
1 hour ago, Marcos said:
Please carry on as follows:
- enable advanced Direct cloud logging under Tools -> Diagnostics in the advanced setup
- reboot the machine
- reproduce the issue
- disable logging
- collect logs with ESET Log Collector and upload the generated archive here.I ran the log collector, but the file size is 103MB. Just barely too big. Is there anything I can remove from the .zip and reduce the size?
-
I think there are 2 different categories of customer here.
- 1st category uses a proxy. (Some have proxy installed on Linux, and some have proxy installed on Windows Server.)
- 2nd category doesn't use a proxy. We have ESET Endpoint Security installed on Windows 10 endpoints.
You have to read between the lines in the posts above to tell which customer is in which category.
I'm in the 2nd category, we don't use a proxy, and yet we get the same error message. (Please go back to my original post to see my screenshots.) So, our problem is not caused by a proxy.
It seems to me, just based on experience, this seems like a problem with startup order. When the Windows 10 endpoint boots up, maybe ESET client attempts to contact the management system before the OS has all the networking services up and running. If this wild guess is correct, it could be solved by changing the startup order, or trying again later long after bootup is complete.
I solved the problem for myself by switching the License Interval Check from Limited to Automatic. So, if my wild guess is correct, the Limited setting only checks once early in Windows bootup. So, I switched the setting to Automatic, and the error went away with repeated connection attempts.
I'm well aware this is a wild- guess, I could be completely wrong about the reasons. But the end result - problem solved by switching to Automatic.
-
Sorry if this is redundant. But to confirm that the problem happens with us.
- We have Endpoint Security installed on Windows 10.
- Using ESET Protect Cloud.
- We have no proxy and all outbound connections are allowed on all ports.
Interestingly - ESET Protect Cloud shows "Everything is OK".
-
One of our endpoints doesn’t seem to be communicating fully with the Cloud manager.
We have ESET Management Agent and Endpoint Security installed on the endpoint. The endpoint shows up in ESET Protect Cloud. I ran the tasks to activate the licenses from the cloud, and that appears to have been successful after a 2nd attempt. (3AP-KFS-A7C ESET Endpoint Security for Windows and 3AP-KFS-A7C ESET Dynamic Threat Defense for Endpoint Security + Server Security)The GUI on the endpoint shows the license is valid, the modules are up to date, the initial scan ran, all statuses are green.
However, the Cloud manager’s Details page for the endpoint is missing some detail. The Products & Licenses section shows no products installed, but it does show the licenses applied. The Installed Applications tab is empty. And the hardware details are missing.
I tried uninstalling and re-installing. But the results are the same.
Any ideas on how I can get this fully functional? I’m concerned that it isn’t communicating properly with the cloud.
-
-
Hi Marcos, thanks for the reply.
I found the ESET Server Security for Microsoft Windows Server installer (efsw_nt64.msi).
We are managing with ESET Protect Cloud. And licensing with 3AP-KFS-A7C EPC.
Is there an installer for the Management Agent?
-
Hi, I get this error message:
Internal error
An internal error occurred. Please try again to start installation again.
I am attempting to install ESET Server Security for Microsoft Windows Server using an installer created in ESET Protect Cloud. This downloads the file epi_win_live_installer.exe. When I run it, (run as administrator) it shows the Install Components screen as expected. But after clicking the Continue button, it shows the error. See the attached screenshots.
I am installing on an Azure VM running Windows Server 2019 with roles AD DS, DNS, and File and Storage Services.
I've searched Google and ESET Forums, but haven't found any advice other than try to create a new installer package, download again, run it again. Is there anything else I can do to find the source of the problem?
Thanks
Need to allow our Application Developers to use NodeJS and JavaScript.
in Malware Finding and Cleaning
Posted
I guess I should add that since he got the error again, I clicked on the listing under "Submitted Files" and clicked on "Create Exclusion". Then changed the assignment to the group.
I won't know if this works until the next time he tries to add another package. I'd like to know before he gets another error. Does anybody know, is this what I should have done?