Documentation forSolarWinds Service Desk

Jamf configuration

On this page

Prerequisites for Discovery connection

Before creating a Discovery connection in SolarWinds Service Desk (SWSD):

  1. Review Best practices.
  2. Confirm you have a scanner up and running in your local environment, scanning data and collecting information from your local network.
  3. Identify user credentials that can be used to access your Jamf Pro instance.

Navigation

Setup > Discovery & Assets > Connections.

Create a Jamf connection

Be aware that SAML/SSO authentication cannot be used to authorize Jamf Pro API calls. SolarWinds recommends that you create a dedicated local Jamf Pro account for use with the API. SSO-only accounts cannot interact with the API.

  1. Navigate to Setup > Discovery & Assets > Connections.

  2. From the All Connections index page, click the Add icon and select Jamf from the dropdown.

  3. Use the information below to help in configuration.

    Field Description
    Cloud identification

    Jamf Pro organizational account URL.
    Authentication credentials

    Credentials for a user who has access to your Jamf Pro instance (read access is sufficient).

  4. Use the image below as an example as you configure your connection. By default, hardware information is fetched from Jamf. However, during the configuration process, you have two options to identify what information will be collected through Jamf:

    • Import installed software from devices (for example, computers). With this selection, hardware information is fetched from Jamf, and then software information is fetched from the hardware.

    • Import mobile devices and installed applications (for iOS mobile devices only). If you select this option, both mobile hardware and software information is fetched from Jamf. Mobile devices are added to the list of mobile assets. You can navigate to Assets > Mobile Devices to see the addition(s).

  5. Click Create on the top right of the screen to save the connection.

    After the Jamf secure connection is established, you can collect the following data:

    • Name (host name)
    • Mac address
    • IP address
    • Serial number
    • Asset ID
    • Department
    • Site
    • Other fields (for example, software)
The Owner field updates from the Jamf device User & location field in each scan if there is any change. However, if a Discovery Agent is installed, the Agent ignores the Jamf data.

In addition, the index page for the specific type of hardware includes an option to modify the page view to include the Scan Origin column. You can also filter the page to display only items matching a specific scan type. See List view.

Be aware that any incorrect information provided in the configuration setup (for example, an incorrect password) will prevent proper reporting in the Scanning report.

More information about Discovery connections

See Connections for information about:

  • Scanned ports and a list of the default ports scanned via Nmap
  • How to run an on-demand scan
  • How to pull a Last Scan Report
  • What data is pulled during Discovery through connections
  • Pulling fields from a mobile device via Intune
  • Obtaining management data from remote computers via WMI

Related topics