Deploy clients with Jamf

Jamf instructions to deploy clients

You can use Jamf to perform a large-scale, production deployment of the Adaptiva client for macOS. The general shape of this process follows:

1. At the command line, install the package.

2. In Jamf, add a configuration script.

3. In Jamf, configure a policy.

4. At the command line, run the configuration script.

More detail for each of these steps is provided below.

Install the Package File

The Adaptiva client for Mac is a package file (.pkg) found in the installer zip. You will need to know the version number, so you may want to extract files from the zip before you begin.

1. At the command line, type the following: sudo installer -tgt / -pkg ./adaptiva-client-<version>-macOS.pkg

2. Open Jamf.

You can find more information on Adaptiva client installation and macOS in the Client Installation on Linux or macOS documentation.

Link the Package File to Jamf

When you get to the script stage of this process, Jamf will need to know how to find the package file. You can set those parameters in a New Package dialog.

1. In Jamf, go to Settings > Computer Management > Packages.

2. Click New Package.

3. Check to make sure you have selected the General tab.

4. In the Filename box, browse to the adaptiva-client-<version>-macOS.pkg file or drag the file into the box.

5. In the Display name box, type Adaptiva.

6. In the Category dropdown, select Utilities.

   

   New package screen

Add a Script to the New Package

For each device, a post-install script runs to configure the Adaptiva client with information like your server name and GUID. You can store the script in Jamf and link it to the package.

1. In Jamf, go to Settings > Computer Management > Scripts.

2. Click New Script.

3. Check to make sure you have selected the General tab.

4. In the Display name box, type Adaptiva.

5. In the Category dropdown, select Utilities.

6. Select the Script tab.

7. Customize and save the following script: sudo /opt/adaptiva/adaptivaclient/bin/adaptivactl setup --server <server address> --server-guid <server GUID> --no-connection-checks

   

   New Script screen

Set a Policy for the Package

Configure the Policy

You'll want to configure a new policy that connects the Adaptiva script to policy options, such as triggers and execution frequency. By setting options at the policy level, you gain flexibility and easier management across different environments.

1. In Jamf, go to Computers > Policies.

2. Click New Policy.

3. Check to make sure you have selected the Options tab and General settings.

4. In the Display Name box, give the policy a meaningful name, such as PRA install - Checkin with Limited Scope.

5. In the Trigger section, select Recurring Check-in.

6. In the Execution Frequency dropdown, select Once per computer.

7. Set any other optional parameters.

8. When asked for details, add the Adaptiva package.

   

   New Policy screen

Set a Scope for the Initial Deployment

For the initial deployment, you should limit the scope for a test run.

1. On the New Policy screen, check to make sure you have selected the Scope tab.

2. In the Target Computers dropdown, select Specific Computers.

3. In the Target Users dropdown, select Specific Users.

   

   Scope tab

Run the Configuration Script

Prerequisites

Before you run the configuration script, be sure to have the following pieces in place:

• Jamf policy

• Recurring check-in trigger

• Once-per-computer execution frequency

• Adaptiva package installed

Run the Script

1. At the Command Line, launch the policy by typing the following: sudo jamf policy

2. You may have to provide your credentials.

3. Jamf will check for policies triggered by recurring check-in for your user name.

4. You should see the text Executing Policy Adaptiva and a series of automated status reports.

5. A validator runs inside the script to make sure the connections are set up correctly.

Validate the Deployment

In the Adaptiva Admin Portal, you can see whether Jamf and Adaptiva have communicated successfully with the devices in the Scope you set for this deployment.

1. In the Adaptiva Admin Portal, got to Platform Features, and then navigate to Asset Devices.

2. Confirm that the Adaptiva client is present.

3. You can also confirm any updates to the OS, client version, or product compliance.

You can find more information about the various validation checks available in Adaptiva in the Client Validator documentation.