Overview
You can run tasks directly from the Management table (Endpoints → Management).
- Select an endpoint and click ACTION.
- Choose Run Task and execute your tasks.
- The progress of the run task can be monitored from the Activities table.
Hover a Task
To see task details, hover over the task name - a pop-up window will open with the following information:
You will be able to see the following data:
| Field | Description |
| Task Name | The name of the task. |
| Task Description | A description of the task. |
| Operating Systems | The OS(es) the task is compatible with. |
| Parameters | The parameters configured for the task. |
| Task Source | Displayed by hovering the icons in the top right corner: Command Line or Script (also shows the script name). |
Run Task at a Specific Time
When choosing the task to run, you can delay execution to a specific time by selecting the Timezone and Date & Time.
Run as an Unmanaged Task
Unmanaged tasks can be executed without Connector monitoring. This execution will not obstruct the endpoint from running additional tasks in its regular run (System / User / User Schedule).
When a task is run as an Unmanaged Task:
- The task runs without a timeout, disregarding the configured timeout in the Configuration Tab.
- The task runs without Connector monitoring.
- The task can be set to run at a specific time.
- Running a task as Unmanaged will not prevent the endpoint from executing additional tasks in its regular run (System / User / User Schedule).
|
Note: Configuration changes are required for this feature to work: Step 1: Connect to the JetPatch Core server via SSH and edit the properties file: Versions before 5.0: /usr/share/tomcat/default/conf/intigua.properties Version 5.0 and later: /usr/share/intigua/services/data/intigua-main/conf/intigua.properties Step 2: Add the following line: automation.task.unmanaged.enabled=true Step 3: Save the file and restart the service: Versions before 5.0: systemctl restart tomcat Version 5.0 and later: docker restart intigua-main |
To run the task, follow the same steps as Run Task and make sure the option Run as Unmanaged Task is selected.
Run Endpoint Readiness Task
- Navigate to Endpoints → Management.
- Select the task Endpoint Readiness for Windows Endpoint or its equivalent for Linux.
- Execute the task to check endpoint readiness.
Viewing Activities in JetPatch
- Navigate to Endpoints → Activities from the left-hand menu.
- The Activities page lists all activities categorized as: Patch, Pre Patch, Post Patch, User, User Scheduled, and System.
- Use filters to narrow results by Smart Group and Task Name.
- Download the full output as CSV if needed.
Interpreting Endpoint Readiness Results
Windows Endpoint Readiness Test Output
The output verifies the following:
| Check | Requirement |
| PowerShell Execution Policy | Must be set to Unrestricted or RemoteSigned. |
| WSUS URL | Must match the endpoint's intranet Microsoft update service location. |
| PowerShell Version | Must be 3.0 or higher. |
| Update Service Requirements | "Has update service location" and "WSUS automatic updates" must both be true. |
| Tip: Download the script from Tasks & Scripts → Scripts → Check endpoint readiness for a single Windows computer. |
Linux Endpoint Readiness Test Output
The output verifies the following:
| Check | Requirement |
| Repo ID | Relevant repos must align with the required configuration. |
| Repo Status | Must be enabled for the relevant repositories. |
| Package Count | The number of packages in the repo must be greater than zero. |
| Update Info | Has Update Info must be true. |
Comments
0 comments
Please sign in to leave a comment.