Hello we’re running Avast 7.0.1455 and we’ve recently just had a custom time clock program developed for us. Well unfortunately every time we execute this time clock software Avast either autosandboxes the executable, or makes the user wait before executing the program.
I’ve gone into Filesystem Exclusions, and added the program directory, added autosandbox exclusions, even disabled autosanbox components at the server and redeployed.
In each instance Avast refuses to honor the exclusions, and when going back in to check the Exclusions that were input before are now missing.
Even when the client is redeployed without the sandbox component it’s still sandboxing.
How can one chisel, etch, or otherwise set in STONE the exclusions for Avast, it doesn’t seem to want to honor any custom settings whatsoever.
We are currently using the Small Office Administration Console, it reports version 1.2.2.8.
It would be great if we could centrally deploy these exclusions, but at this point I don’t mind doing to each computer manually, the time clock software is on 4 out of 27 computers.
I’m assuming the clients are setup with the admin console address correctly, so they are checking in with the server and their status is showing up as connected in the SOA console.
I’d go into the network group, edit group settings, navigate to shields settings, autosandbox, and then either disable autosandbox or put the exclusions that you want in the autosandbox exclusions list there.
It WAS managed a time ago. I’ve installed the console, added domain credentials, and then pushed out the client to all the happy domain members. But now some of the computers lose their license, and don’t honor when I turn the AutoSandbox off globally from the console. How do I tell the clients to ALWAYS look at the server for their marching orders?
And that being said, if I can’t centrally deploy exclusions from the console, how do I get them to stick on an individual basis?
We had purchased an additional 5 licenses and I sent a support ticket to Avast and they “Glued” them together. I re-downloaded that file and
re-inserted it back into Avast.
From what I can tell the client keeps going back into trial mode.
Isn’t Avast Proper aware of this when they preform the merge action of the licenses together?