-
Patch installs failed due to malformed email format in Reboot Action policy
Problem When installing patches to certain agents, Patch status is not automatically updated (but it may show as "installed" after running a new patch scan). Agent procedure log shows the following error during patch install process: - 4:51:07 pm 7-Sep-15 $inst$ptc0$ebd-080.root.ebd *System* Script Summary: Failed loading…
-
Patch Reboot Action causes machine to reboot after scheduled time.
PROBLEM: Machine reboots after patches are installed if patches and reboot action are scheduled at the same time regardless of the time it takes for patches to install. CAUSE: When patches are set to install at the same time as when the reboot action is set to reboot, the patches will install and take x amount of time.…
-
Windows 10 fresh OS Install or Upgrade - Cannot complete patch scans
PROBLEM Windows 10, whether upgraded from a prior OS or using a fresh OS install, cannot complete patch scan when server is at R9.1 and the agent is at R9.1. The patch scan will report as completed but the patch data may not report correctly. CAUSE This is a known issue that is being investigated. SOLUTION The problem is…
-
Patch scans results do not update to the UI. Error: hr=8007000E
Problem: When scanning a machine OS type: Windows 7 32-bit for the most part, the scan reports no information back or does not update with correct data. Also, once the machine scan is done the WindowsUpdate.log ( C:\Windows) will have entries as below: COMAPI WARNING: ISusInternal::GetUpdateMetadata2 failed, hr=8007000E…
-
How do I transfer over patch policies to another Kaseya Server?
Answer We set up a new Kaseya Server for a customer and wanted to know how I can transfer over our patch policies from one Kaseya Server to another ? Resolution You can transfer over a policy by using the import/export feature on Kaseya. Go to System--> Import Center and you can export your patch policy. On the new Kaseya…
-
Question marks appear in the patch Details section for a patch
Question: Why are we unable to see the name/description for patch in Patch Management module, instead question marks appear in the patch Details for a patch. Example: Answer: When patches like this are encountered, these patches are specific to one machine. If machine X detects a patch in a language that is not supported…
-
Patch Status error: Credential might not have admin rights. Patch file failed to install.
Issue: Patch Management > Patch status page shows error below when performing patch test Cause: The agent does not have the correct credentials to perform the operation. Resolution: Open Start menu =>services => Agent service => right click => properties => "Log on" tab => Make sure it is set as "Local System Account" as…
-
Patch Scan error "FAILED in processing THEN step 7, Get Variable, with error File Open Failed"
Problem * Patch Status shows no patch data (only dashes) even after patch scan In order to determine whether this article may be applicable to the conditions you are experiencing, view the Agent > Agent Logs > Agent Procedure Log for the specific endpoint. Note: ensure you are reviewing the Agent Procedure log, not the…
-
Why can't I see the latest Microsoft Surface Pro firmware update on Kaseya ?
Question When I run Windows Update on the machine I see the latest MS Surface Pro firmware update, but when I run a patch scan on the endpoint, I don't see the firmware update on the Patch Management Module. Answer If the firmware update is not available on the Microsoft Update Catalog, then the patch will not be available…
-
Processing Patch Scan Results Failed
PROBLEM When you look at the Agent Procedure log via Agent module> agent logs option you notice the entry below. Note this would cause patch status page to NOT update correctly as the data has not populated yet. 3:01:15 pm 11-Feb-15 WUA Patch Scan 2 System Processing patch scan results for <machine_id> failed. CAUSE At…