We have just released Kaseya VSA Patch 220.127.116.11:
————— 18.104.22.168 - 12 December 2017—————
Virtual System Administrator™
————— 22.214.171.124 - 7 December 2017—————
There were a few issues mentioned in the .32 thread community.kaseya.com/.../23682.aspx
One issue was with regards to reapplying schema after applying the .32 patch. Has that issue been resolved in this patch?
Another issue mentioned was something about Webroot, but that issue sounded more like a problem on Webroot's end. Can anyone confirm if that issue still exists? Moreso, if I'm on an older patch am I affected by that issue, or is it specific to .32 (and possibly .34)?
Hope you are doing well, from reviewing the reapply schema errors mentioned in the referenced thread, one seems like it was not related to the patch and the other related to WebRoot.
WebRoot, as others mentioned, may present a schema issue, but this may be due to some condition of the WebRoot version but I cannot confirm, as I have it installed in my system and did not have any issues with WebRoot - from what I can tell there were only 2 reports of it to our support team (If you do face an issue with reapply schema, please do raise a support ticket).
If you are on an older patch, they should all roll up and it should not present you with the reapply schema issue identified in VSA Patch 126.96.36.199.
Let me know if I can provide any further clarifications on this as I know it has been rather confusing.
We did run into an error during the Reapply Schema from the (post)installer launch from the Webroot patch. After the error I was able to run the reapply from the Kaseya console successfully. This behavior was not seen in the lab test but did occur in production (188.8.131.52) last night. I am not sure that it is worth the time to enter a ticket as it is working now.