Configuration settings not persistent

[ntshane]

Hello, I have a strange problem with nod32 4.0.437 (and other versions)

When I push out a configuration change, specifically when I disable real-time scanning of network drives, the change will not persist after a reboot. It ends up being checked again after any reboot. In addition, if I push out a configuration to a PC, this setting never changes even though the task shows as successful. Help!

-shane

[RyanH]

If you are using Policy Manager in the ESET Remote Administrator, please make sure that these settings are in there as the machines may be reverting back to the setting in Policy Manager when reporting back to the ESET Remote Administrator Server.

[RyanW]

Are you just pushing out changes but leaving the setting defaulted in the policy editor?

I think the changes you 'push' are not persistent, but if you want them to be you need to have them in your default client policy in ERAC. I've got everything I want set in the default client policy and my changes are persistent across restarts.

There's also another policy that allows user setting to override policy, make sure that's disabled in your fault client policy too.