Articles in this section

Run Task (including specific at a time, unmanaged, and readiness tasks)

You can run tasks directly from the Management table (Endpoints > Management)

To do so, select an endpoint and click on "SELECT ACTION", then choose "Run Task" and execute your tasks.

Progress of run task can be monitored from the activities table

Hover a task

To see task details you can hover over the task name and a pop-up window will open: 

You will be able to see the following data:

  • Task Name
  • Task Description
  • Operating Systems
  • Parameters 
  • Task Source - by hovering the icons in the top right corner 
    • Command Line mceclip2.png
    • Script - provides you also the script name mceclip1.png
  • Executing a Reboot Procedure 

Run Task at a Specific Time

When choosing the task to run, you can delay the task to run on a specific time by choosing 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 the User chooses to execute a task as an Unmanaged Task:

  • The task will run as an Unmanaged Task.
  • The task will run without a timeout, disregarding the configured timeout on Task Settings (located on the 'Configuration' Tab).
  • The task will run without Connector monitoring.
  • It will be possible to set the task 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: It is required to make configuration changes for this feature to work:

  1. Connect to the JetPatch Core server through SSH and edit the file /usr/share/tomcat/default/conf/intigua.properties
  2. Add the line
automation.task.unmanaged.enabled=true   

     3. Save the file and restart the tomcat.

To run the task please follow the same steps from "Run Task". Make sure the option "Run as Unmanaged Task" is selected. 

 

Run Endpoint Readiness Task

  1. Navigate to the Endpoints > Management Tab:

    • Open the JetPatch console and go to the Endpoints > Management tab.

  2. Select the Task:

    • Choose the task "Endpoint readiness for Windows endpoint" or its equivalent for Linux.

  3. Execute the Task:

    • Start the task to check endpoint readiness.
    • For further details on running tasks, refer to Running a Task documentation.

Viewing Activities in JetPatch

  1. Navigate to the Activities Page:

    • In JetPatch, go to Endpoints > Activities from the left-hand menu.
    • This page lists all activities categorized as Patch, Pre Patch, Post Patch, User, User Scheduled, and System.

  2. Filter by Smart Group and Task Name:

    • Use filters on the Activities page to narrow the results by Smart Group and Task Name.
    • This provides focused tracking and management for specific tasks or endpoint groups.

Interpreting Endpoint Readiness Test Results

Windows Endpoint Readiness Test Output:

The output verifies the following:

  • Powershell Execution Policy:
    • Must be set to Unrestricted or RemoteSigned.
  • WSUS URL:
    • Matches 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.

For more information, download the script from Tasks & Scripts > Scripts > Check endpoint readiness for single Windows computer.

Linux Endpoint Readiness Test Output:

The output verifies the following:

  • 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.

Use this information to ensure endpoint readiness before patch management processes.

Related articles

Comments

0 comments

Please sign in to leave a comment.