File Security 6.5 Upgrade LiveGrid enable wont work

[bauavssft 0]

We started to deploy 6.5 and on Windows 2012 Server R2 we see LiveGrid disabled, but in policy it enabled and FORCED we also now see that phishing disabled warning. We cant enable LiveGrid, how to solve that problem?

version 6.4 works fine with no issue

 

[Marcos 5,070]

Please clarify what problem you have with querying ESET cloud servers with hashes of files and urls.

Apologize, I misread your initial post.

[bauavssft 0]

all grid parameters enabled, you mean that client machine doesn't have access to grid servers ?

[Marcos 5,070]

If you enable LiveGrid manually, does it stay enabled? Also could you confirm that you installed ESET File Security or ESET Mail Security 6.5 on the server?

[bauavssft 0]

we gave 1 server full internet access but still have Notice about Disabled LiveGrid

this happens only on 6.5 version

[bauavssft 0]

we installed  ESET File Security 6.5, option is disabled in Options because we use Eset_Policy on all servers

[MichalJ 434]

Can you send us screenshots of the error message, setup pane (live-grid switch) and the advanced setup with live grid settings. It could help us to better understand the issue.

[bauavssft 0]

Yes. This version was upgraded correctly from 6.4 to 6.5 and in 6.4 LiveGrid worked.

[bauavssft 0]

option enable just do nothing, clicked but without result, no error message

[Marcos 5,070]

The padlock next to the LivveGrid setting means that it's enforced by a policy. Please check client details in the ERA console and check the policies that are applied. Make sure the setting is enabled.

[bauavssft 0]

enabled, re-added host for policy apply. 

[Marcos 5,070]

According to your screen shot, you've picked a wrong product. Instead of "ESET File Security for Window Server (v6+)", you've picked "ESET Endpoint for Windows" which is why it's not applied on EFSW.

[bauavssft 0]

2 hours ago, Marcos said:

According to your screen shot, you've picked a wrong product. Instead of "ESET File Security for Window Server (v6+)", you've picked "ESET Endpoint for Windows" which is why it's not applied on EFSW.

thanks that was main problem, my mistake.