Jeff.KeyesWhenever a scheduled scan is run from Kaseya, it is run under the process of KaseyaAVService...so it makes sense that it uses a lot of CPU and memory.
When the audit runs, it calls back into the Kaseya service as well. We do a bunch of cleanup after these things run.
In future versions (i.e. what we are working on now), we'll be far less chatty and just report on the final situation of these operations which will clean this up even further.
On that note, I'd recommend not using the office add-in (not the email scanner, just the office scanner)....it is intended for legacy office applications which are mostly gone now. We are planning on removing it from future releases.
Anything outside of this, please log a ticket so we can get the AVG support guys involved.