We have just released patch 220.127.116.11:
Critical Issues For Customers To Patch Immediately
Virtual System Administrator™
Once 'Use LAN Updater' is checked, click the 'Refresh Lan Updater' button to enable this same feature immediately on newly added or reconfigured machines. As a precaution, the 'Refresh Lan Updater' function runs once a day. (PT-377/ATTWO-1601)
There was a problem : transaction aborted
An existing asset "..." with IP "..." and address "..." have been updated at device ID ....
Non-Critical Issues For Customers To Patch When Convenient
A lot of good fixes on this one.
@oromero, there are good fixes but AVG still doesn't work after the patch update...
I understand that Avg fixes are scheduled for the next patch.
When I joined my current company they were a hybrid AVG/Kaspersky shop. I am not familiar with your situation however, there are other options with potential which integrate well with Kaseya. The new Kaspersky module is suitable to levels as well.
Ran into really high CPU usage for the KaseyaEdgeServices.exe tonight post .27 install. It has been 20 minutes and it has been pegging the 6proc/40gig server ver since the restart. Anybody else run into something similar?
Well Tim, our VSA server is a bit more creative and has two options to run out of resources.
I've seen the KaseyaEdgeServices.exe eating up every ounce of memory it could, slowing the VSA to a crawl, doing a restart of the corresponding service should fix this. The last time it was the end of the day and I resorted to rebooting the server. Last time I saw this was around 6, 7 weeks ago.
We see the Kaseya.SecurityCenter.AV.Service.exe process doing the same but then much more efficiently ;-) The service for all things AntiVirus has a strike rate of once every week, maybe 2 weeks in a good month. We've had support contribute this to the old Kaspersky Classic installations. Since we're very close to having migrated some 4500 clients to the new AntiVirus module, this issue should go away soon.
For both issues we've not been able to pinpoint why they happen, unfortunately. We do run a lighter setup, 4 proc / 14 gig - usually running at 5 - 10% CPU and 10 gig memory.