Anyone braved the new update that came out yesterday yet? Just curious to know if anyone has done so and had any "new" issues?
Not yet, though I see they finally have a fix in for our weird "negative message queue length" bug in the system status page. There's enough stuff in this one to warrant doing the upgrade, especially the Live Connect fixes. (We didn't do .14, wasn't anything in there we needed badly enough to risk getting a new bug.)
Yes it has a fix in for me that gets screen recording working again.. I need it but I need to see if we have problems before I load it up.
I was thinking about doing it tonight. Looks like a nice round of bug fixes...
FYI - adding in the warranty dates for reports is nice, BUT other than being able to list the warranty dates you can not do a report that allows you to show ONLY the expired and/or missing warranty dates ... Or at least that we've been able to figure out yet ...
Please see the link below for more information on the Patch Release notes - for those that may need it.
Agent Update to 18.104.22.168
Live Connect & Remote Control
Database & Schema
Audit Module, Policy Management Module
Info Center Module
Classic Monitoring Module
Service Desk Module
Security Vulnerability, VSA Core
Database & Schema, Installers, KServer, VSA Core
Cloud Backup Module
@Craig Hart; which one?
Is this Kaseya’s way of saying Patch Management doesn’t officially support patching Win 10 devices anymore? Or this applicable to the latest build 1803 only?
• On Windows 10 Machines, Microsoft will force updates, so the "automatic update" setting is no longer relevant. VSA will now display "automatic updates not supported" (i.e. auto-update cannot be set on or off) for Windows 10 machines on applicable MS Win 10 builds. (VSA-255)
We know it doesn’t work consistently for all Win10 devices but we were hoping they would fix it instead of stop supporting it.
I don't know if anyone else had this issue but the machine filters would work a couple of times and then would stop updating the page since about version 9.4. This update seems to have resolved this. I do not need to refresh the whole page.
I thought it worth commenting on.
• On Windows 10 Machines, Microsoft will force updates, so the "automatic update" setting is no longer relevant. VSA will now display "automatic updates not supported" (i.e. auto update cannot be set on or off) for Windows 10 machines on applicable MS Win 10 builds. (VSA-255)
Applied 22.214.171.124 (and, um, .14 as well) and now one of my frequent-running PowerShell-based procedures is broken. I don't know if .14 or .15 did the deed but I'm borked until Support can figure out what went awry. (Given that .14 is the one which specifically mentions "the wrong command" for PowerShell in procedures, that's my guess. But.)
We've applied it now as well. No major *new* issues, but I do have to agree with Craig's findings that it definitely hasn't fixed *all* of the keyboard bugs with liveconnect. I've had several instances still where while I've got remote control sessions up using live connect my shift key stops working completely *locally*. Until I close out all live connection sessions.
It definitely fixed the recording issues we were seeing, and did fix *some* of the keyboard bugs I'd seen.
We have been on it Since Friday. No issues here.
Patched last night - same findings as Craig Hart and Jonathan