Erlend

unassigned the default policy File Security for Windows Server - HTTP Proxy Usage now. i will report back how it goes after a few days.

it's set in the default policy: File Security for Windows Server - HTTP Proxy Usage

hm, yes i see that now it's configure to connect via the ESET management server.

Hi again @Marcos, we see both activation errors and live grid communication errors at random how can we figure out what the issues is?

ok, thank you!

Hi what's the hostnames for ESET LiveGrid and ESET License servers?

ok, yes that's the internal ESET server.

logs. efsw_logs.zip

what do i need to include in ESET Log Collector?, don't won't to upload any unnecessary information here.

the servers are connected directly not via proxy the issues seems to be intermittent, sometimes it's ok if i check for updates 5 times one of them can be ok are there any logs i can check on the client, to see what source is used for updates?

Hi any know issues with updates at the moment?

@Marcos same issue, i have sendt the license details in a private message.

one more thing, do you have a internal system to make local support in different countries aware of these kind of issues? i contacted ESET support in Norway, and they needed to check and get back to me.

the version is: 1236

no, both ESET shell and GUI is non-responsive (not able to start them), but i can access the file system remotely on the affected servers. is the module a separate dll file?, that i can check the version on?