-
Software Management 2.0. Migration of 3rd-Party Software Profiles.
With the 9.5.9 version, VSA introduces the new version of the Software Management module — 2.0. This version brings important advantages: * Frequent module updates thanks to native in-house technology without any 3rd party dependencies. * Reliable Windows patching including BIOS and driver patching using native Microsoft…
-
Software Management 2.0 vs 1.0
With the 9.5.9 version, VSA introduces the new version of the Software Management module — 2.0. This version brings important advantages: * Frequent module updates thanks to native in-house technology without any 3rd-party dependencies. * Reliable Windows patching including BIOS and driver patching using native Microsoft…
-
Software Management 2.0. Full migration guide.
With the 9.5.9 version, VSA introduces the new version of the Software Management module — 2.0. This version brings important advantages: * Frequent module updates thanks to native in-house technology without any 3rd party dependencies. * Reliable Windows patching including BIOS and driver patching using native Microsoft…
-
Microsoft confirms issues with January 2022 Cumulative Update
Microsoft have acknowledged issues with the January 2022 Cumulative Update. These issues affect L2TP over IPSec VPN connections, Hyper-V Machine reboot loops, and ReFS drives not being recognised. The VSA can be used to deny this patch and avoid these issues. Please see this KB article which explains how to deny this…
-
How To Deny a Patch in Software Management?
How do I deny a patch in Software Management? It is good practice to test OS or application patches before rolling these out to your managed machines. This testing should cover various platforms - OSes, hardware, software, etc. This testing will limit the chance of patch causing widespread During this testing, you may find…
-
Software Management 2.0 - Security Update Severity Rating System
Kaseya Software Management 2.0 uses the Windows Update API to detect and install OS Patches on Microsoft devices. Microsoft break these updates in to 4 categories, however, in Software Management, we currently break these in to two categories - Critical and Recommended. There are 4 Microsoft ratings - Critical, Important,…
-
Troubleshooting and log collection for New SM (Kaseya Update 2.0)
Summary Follow these steps to troubleshoot and collect the logs for the new SM module Process Clear all settings in the SM interface * Clear all pending actions * Clear all errors * Remove the Scan and Analysis profile * Remove the Deployment profile * Remove the 3rd Party profile * Remove 3rd party support Clear the logs…
-
Software Management Troubleshooting Guide
Below is a list of SM messages with their meaning, cause and troubleshooting steps to resolve. NB. The Activity.log can be found in C:\ProgramData\Kaseya\Log\Endpoint\Instance_XXXX\Tasks\ActivityLog Messages Could not assign profile to agentGuid because it is currently using Patch Management. Cause: On the Software…
-
Software Management 2.0 - 3rd-Party Software Applications List
Application Name Product Version OS Arch .NET Core Desktop Runtime 3.1 (32-bit) for Windows3.1.32.31915Windows32 bit.NET Core Desktop Runtime 3.1 (64-bit) for Windows3.1.32.31915Windows64 bit.NET Core SDK 3.1 (32-bit) for Windows3.1.426.16244Windows32 bit.NET Core SDK 3.1 (64-bit) for Windows3.1.426.16244Windows64 bit.NET…
-
"Failed to Install after two attempts" OR Machine picking up zero or no vulnerabilities
PROBLEM When using Software Management, my vulnerabilities are failing to be installed and the patches are failing with Failed to install after two attempts. OR When using Software Management, my machine is not picking up any vulnerabilities, my machine returns 0 vulnerabilities. CAUSE Microsoft periodically updates the…