How do I trigger automatic system tasks?

WSUS 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.  How to:

1. Go to platform configuration
2. Go to Settings
3. It should already be on Discvoery Sources, so from here you can disable, then re-enable WSUS discovery source.
4. After you re-enable, click back into JetPatch main page
5. Go to Endpoints > Activities and wait for wsus get groups and wsus get summaries per computer to execute

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 deletes the timestamp of the last full patch list retrieval by JetPatch from WSUS. During the next execution of the 'WSUS Get Updates' script, JetPatch will first retrieve the oldest 5,000 patches (visible in the Activities tab), then continue retrieving patches in batches of 5,000 until reaching the most recent patch. This process usually completes within a couple of batches.

Collect Endpoint Updates (Windows without WSUS and Linux/Unix)

JetPatch collects updates on endpoints by running the "Collect Endpoint Updates" system task.

Option 1: Remove and re-add the endpoint from the inventory - This is possible if the endpoint is not discovered via a Discovery Source.

1. Linux/Unix Only: 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

Option 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';