Policy not apply for Windows server

[chuong 0]

Hi all,
I'm using ESET Security Management Center 7, I created a Policy "for windows server" with many custom "perfomance exclusions" , "processes exclusions" , "file extensions excluded" (for scan) , "scheduler" , "password protect settings".
This policy is assigned to/applied on a Windows server 2008 R2 SP1.
I use ESMC to install ESET Management Agent then ESET File Security 7.3 for above Windows server successfully, but settings from policy are not applied/showed when I view in advanced setup.
How can I troubleshoot it ?

[Marcos 5,092]

First of all I'd recommend upgrading to ESET PROTECT and installing ESET Server Security v8. Is there a reason why you are not on the latest supported version?  ESMC is already in limited support phase.

[chuong 0]

Hi Marcos,
I cannot upgrade to ESET PROTECT right now.
First, I deploy agent to windows server using ESMC , then download and install ESET Server Security v8 (because ESMC doesn't have ESET Server Security v8 package , of course) , but the policy is not applied.
So I uninstall ESET Server Security v8 and deploy ESET File Security 7.3 by ESMC, hopefully, policy would be applied from ESMC, but it wasn't.
Policy for workstations works fine.
If can not troubleshoot, I have to configure ESET in 1 example server then export settings and import to other servers.

[chuong 0]

I attach a policy image

[MichalJ 434]

Is the agent communicating? Isn´t there any policy configuring the same settings with "force flag" set on a static group / all? that might prevent the product from getting the policy.

Also, please make sure, that both agent / File Security is capable to update its functionality modules, so the "configuration support module is on the latest version".