Configuration guide: Jamf client continuity

The configuration options on this page are only accessible to administrators.

Refer to the Usage guide: Jamf client continuity to use library content as a standard user.

Prerequisites

This library pack contains content from the following required expansion products:

Some of these products offer default access to their respective content and can still be used without expansion products.

To learn more about default thresholds for expansion products, visit the extended documentation.

Included content and dependencies

This library pack contains the following content and dependencies:

Content type
Name
Description
Dependencies

Jamf client continuity

Orchestrate the troubleshooting of Jamf client.

none

Get Jamf agent health

Collects key Jamf client status information.

Used directly in the workflow

Invoke Jamf reconnect

Reconnects the Jamf agent to the JSS server.

Used directly in the workflow

Configuring Jamf client continuity pack

Adapt these suggested configuration steps to edit and customize content according to your organizational needs.

Follow these steps to install and configure content:

Step 1 - Configure remote actions

  1. From the main menu, navigate to the Remote Actions > Manage remote action page.

  2. Review and edit your remote actions.

Nexthink recommends the following configurations for these remote actions:

Name
Trigger schedule
Parameters to edit

Get Jamf agent health

Trigger: Workflow

N/A

Invoke Jamf reconnect

Trigger: Workflow

N/A

Step 2 - Configure ITSM API connector credentials

The configuration of connector credentials is essential for enabling API calls.

  1. From the main menu, navigate to the Administration > Connector credentials page.

  2. Choose the HTTPS option from the Protocol drop-down.

  3. Paste the root https:// of the ITSM into the URL address field.

  4. Choose the Basic option from the Authorization drop-down.

  5. Enter a Username and Password to connect to the third-party tool.

  6. Save the credential.

After configuring the connector credential for the ITSM API:

  1. From the specific workflow, fill in each Service/API thinklet dropdown field for Credentials.

    • When the workflow is installed or copied from the Library, this field will be blank as it is a local setup of each environment and is not included in the Library.


RELATED TOPICS

Last updated

Was this helpful?