-
'Reboot Now' Button Remains and/or end user Reports Ongoing Patch Reboot Nag After Reboot
Problem * After rebooting an endpoint, the Reboot Now button persists on the Patch Status page. * After rebooting an endpoint, the end user continues to be prompted with the Patch Reboot nag. * Machine Update page may list some patches as Reboot Pending. * New patch installation cycles do not begin and the Configuration…
-
Patch Test Fails
Problem * Agent Procedure log reports, "FAILED in processing THEN step 3, Execute File, with error Invalid executable file, %WorkingDirectory%\kPmChk.exe" * Patch Management > Patch Status shows "Patch file failed to download" or "Patch file failed to execute" after running patch test. Resolution The Patch Test simulates…
-
How do I ensure I copy all Patch settings, including Patch Scan Schedules, Patch File Source and Patch Policies?
QUESTION I am attempting to copy certain patch settings in the Agent > Configure Agents > Copy Settings page, however when I do this, certain patch settings are not copied over. For example, the Scan Machine Settings are not copied over even though I select the "Patch Settings" radio button in the Copy Parameters pop-up…
-
Proxy and Kaseya Patch Management
QUESTION How do Proxies work with Kaseya Patch Management? Note: This article specifically addresses the use of a proxy, but also contains information relevant to firewall, web filter, and other network infrastructure configuration. ANSWER Many environments use a proxy to manage web traffic. It is important that the proxy,…
-
Windows Auto Update page displays “Automatic Update not initialized on machine” for some endpoints
KB#: KKB000806 QUESTION Windows Auto Update page displays “Automatic Update not initialized on machine” for some endpoints ANSWER Kaseya leverages Microsoft’s patch scan engine for patch scans and patch installations. In order configure the Windows Auto Update setting for an endpoint, the locally-installed program on the…
-
Why can’t I see a patch in my VSA that I know has been released by Microsoft?
KB#: KKB000676 QUESTIONWhy can’t I see a patch in my VSA that I know has been released by Microsoft? ANSWERMicrosoft releases a tremendous number of patches for their vast array of products. Not all environments requireevery patch that Microsoft releases. Rather than inundating your system with patches you don’t need,…
-
Initial Update status reported as "Started" but no patch install scripts are run.
KB#: KKB000692 · QUESTION A machine is scheduled for "Automatic Update" or "Initial Update" under Patch Mgmt. The Initial Update status reported as "Started" but no patch install scripts are run. Or the machine with Automatic Update scheduled does not have any patch updates scheduled at the expected time. · ANSWER There is…
-
How do I configure a LAN Share as the File Source?
QUESTION: How do I configure a LAN Share as the File Source? ANSWER: To configure a LAN Share as a File Source, please review the example steps below. Please note that the machine you designate as the file source:* MUST have access to anonymously browse to the following sites to download patches from the patching websites*…
-
Reboot Action Overview
The “correct” Reboot Action will vary based on your users and business requirements Reboot Immediately after Update: Machine is rebooted without warning Reboot every day at 12:00am after install: will reboot on the selected day and time without warning, but will only occur if a patch installation cycle has run Warn the…
-
Patch Scan Process Overview
KKB#: KKB000897 A patch must be release by Microsoft into the Update Catalog (catalog.update.microsoft.com) AND detected as needed via a patch scan by at least one endpoint in your environment to populate in the VSA. Review https://helpdesk.kaseya.com/entries/34399846 for more detail.