We have released patch 184.108.40.206 just now:
Critical Issues For Customers To Patch Immediately
Virtual System Administrator™
Enterprise Mobility Management
The no reboot on AVG2012 to 2013 is great. Unfortunately the windows firewall is still disabled as part of the upgrade.
I raised ticket #110113 on this a long time ago, got the run around with Kaseya blaming AVG and vice-versa, and eventually had the ticket closed on me with no resolution.
With the mandatory upgrade to AVG 2016 coming shortly, I would think it important that Kaseya fixes this bug.
Have a bunch of services that do not start after updating to this release, just opened a ticket with support...
EDIT: Kaseya support was very quick in response with the down system. A reinstall of the schema worked and was able to get us up and running.
We had similar issues. In our lab, we needed to do a manual schema update in order to get agents to update and all modules to show up. In our production environment we had a down situation...the schema update wouldn't complete. We worked with support and the final fix was a re-install of the patch/kserver. After that, the schema update ran successfully.
We came from patch .15 directly and had no noticeable problems in our installation. I did for good practice reapply the schema after patching and before I tested everything. Agents were updating properly, everything has been running okay for us. That said we do not utilize the KAV/KAM modules so those are not tested.
We also had the issue of 3, 4 services failing after the mandatory reboot on the last two patches.
Running Reapply Database Schema has fixed this for us as well. On the 220.127.116.11 patch we also had to start the Kaseya Directory Integration Service ourselves.
What remains is an issue with the Kaseya.SecurityCenter.AV.Service.exe process that takes up all resources on our VSA within a day of installing 18.104.22.168. That means Memory usage is at 99% and CPU is high, causing the Private Microsoft Message Queue for kes.service to rise over 10.000 halting all KAV related actions. Restarting the Kaseya Antivirus Service is a solution for this issue, at least for a few days. We've had this issue for the past few months on 9.3.