Windows System Tasks

WSUS Discovery Source Tasks

The systems tasks that are related to WSUS Discovery Source can be triggered by disabling, then reenabling the WSUS discovery source.

WSUS Get Updates

A manual run of WSUS get updates can be forced by appending the following to the JetPatch URL:

/vmanage-server/rest/experimental/patch-governance/jobs/fetch-wsus/run?fullScan=true

This query will delete the last time that JetPatch pulled the full patches list from WSUS and in the next time the "WSUS Get Updates" script will run - it will pull all of the updates in the Activities tab.

Note: In JetPatch 4.2.6, there is a known issue where it will say "An unknown error has occurred" this is a cosmetic only issue, which will be fixed in 4.2.6 UR4, and actually enhance the experience by automatically redirecting to the Activities tab.

Linux System tasks

Collect Endpoint Updates

JetPatch collects the updates on a Linux endpoint by running the "Collect Endpoint Updates" system task.

1) Remove and re-add the endpoint from the inventory - This is possible if the endpoint did not discover via a Discovery Source.

1. Delete the "/var/cache/JetPatch/scan_result.txt" file on the endpoint itself to get the latest updates states from the endpoint.
2. Go to platform configuration
   
3. Go to Servers > Server Actions > Remove from inventory.
   1. Note1: Removal from inventory doesn't uninstall the connector from the endpoint, but it will remove all DB entries (tags, smart groups, assigned MWs, etc).
   2. Note2: Because connector is installed, the entry should re-appear in a minute.  If not, re-add to inventory
4. Collect endpoint updates should now run in then next few minutes

2) Database Query - If the endpoint is part of a Discovery Source, the trigger should come from deleting some entries in the DB.

1. Connect to the JetPatch Database
2. Stop tomcat (service tomcat stop)
3. Before deleting the entries, let's make sure the deletion will happen for the needed endpoint. Run the following command (Replace the <ENDPOINT_NAME> with the actual name of the endpoint). The result
   should have 1 or 2 entries:

   select * from bulk_run_task where endpoint_id in (select id from endpoint_server where name like '%<ENDPOINT_NAME>%');

4. Delete the entries by running the command (Replace the <ENDPOINT_NAME> with the actual name of the endpoint):

   delete from bulk_run_task where endpoint_id in (select id from endpoint_server where name like '%<ENDPOINT_NAME>%');

5. JetPatch will trigger the Linux system task on the chosen endpoint almost immediately. This can be seen in the Endpoints -> Activities table (note - mark "System" tasks to show them in the table)

Note1: In order to trigger system tasks for all endpoints within a group, use the following example

delete from bulk_run_task brt where brt.endpoint_id in (select pc.endpoint_server_id from pg_computer pc inner join pg_computer_group pgc on pgc.id = pc.group_id where pgc.name in ('SUSE', 'RH'))

delete from bulk_run_task where type = 'EP_UPDATE_SCAN';