This guide will detail how to deploy a custom profile, how to deploy the Auvik SaaS Management package, and how to run the appropriate configuration script.
Deploying the Custom Profile
Login to Jamf Pro and navigate to Computers > Configuration Profiles.
Click Upload to create a new Configuration Profile.
Open the Auvik SaaS Management platform and navigate to Org Preferences > Integrations > Custom Scripts. Download the Custom Profile from within the Custom Scripts menu for your operating system as highlighted in the screenshot below.
Once you’ve saved the .mobileconfig file locally, return to the Jamf platform. Select the Application & Custom Settings payload and then click the Upload button. Click Add option and upload the .mobileconfig file downloaded from the SaaS Management platform.
Using the Scope menu, apply the uploaded custom profile to the desired devices. It's always recommended to test the deployment with a small group of devices first. Be sure to hit Save to start the deployment.
You can easily see the updated status of the custom profile deployment on the Configuration Profile menu.
Note: It is recommended to wait until the device checks in with Jamf, and validate that the custom profile is present on the device before following the rest of this guide. This ensures that the profile is properly pushed to the device prior to the package and configuration script being run. If the profile does not exist on the device, the deployment may not be silent, and users may receive permission prompts.
Uploading the Auvik SaaS Management package to Jamf Pro
First, download the Auvik SaaS Agent Package by navigating to Org Preferences > Integrations > Custom Script and select the button to download the .pkg file. Save the file to your local device, as this .pkg will be uploaded to Jamf.
Log in to Jamf Pro and In the top-right corner of the page, click Settings, then Computer Management.
In the Computer Management section, click Packages then select New.
Use the General pane to configure basic settings for the package, including the display name (Auvik SaaS Management) and then select a category according to your typical configuration for IT related tools (typically Utilities or similar).
Note: If you do not add the package to a category, Jamf Admin will automatically display the package in the Unknown category.
Click Upload Package and upload the package. No manifest file is needed.
Click the Options tab and configure the priority setting as a value 1-10. This is highly dependent on your configuration, but conventionally, lower priorities indicate that this particular package will be installed first during the enrollment process.
If you’d like to only install on certain operating systems or similar, you can use the Limitations tab to configure the package to only deploy on a certain OS. When finished, hit Save to save the new package.
To add this package to a policy, navigate to the Computers Tab and click Policies.
From this screen, you can configure a new policy that deploys the Auvik SaaS Management package. Select Policies > Packages on a new policy, or an existing policy that you’d like to modify.
Select a Distribution point (depending on your configuration - this is typically Cloud Distribution Point) and select the package uploaded in the prior step. Set the Action to Install so that the package is installed on any devices enrolled in the policy.
Setting up the ASM Configuration Script
Once the package has been added to the policy, we then need to add a configuration script so that the deploy package knows which tenant of ASM it needs to check in to.
Navigate to the Scripts menu on the left hand side of the policy menu. Click Configure and then New.
Give the script a recognizable Name, Description, and Category similar to the screenshot below.
Open the Auvik SaaS Management platform. The configuration script is available both as a .sh file or for you to copy/paste into Jamf Pro. To do this for a specific client tenant, navigate to Org Preferences > Integrations > Custom Script within the Auvik SaaS Management Platform, and then select the desired client tenant in the dropdown. For deployments via Jamf or similar, be sure to use the script listed under the Installing Auvik SaaS Management on Mac Using MDM option.
Copy/Paste or upload the downloaded .sh file into the Scripts tab within Jamf Pro. As a final step, navigate to the Options tab and be sure to set the Priority setting to After. This will ensure the configuration script runs only after the .pkg file is deployed.
When done, hit Save.
Deploying the Newly Created Policy
As a final step, we need to configure this newly created policy, to push the package and run the configuration script. There are several ways to accomplish this, but it is often easiest to set the device to run regularly on the device’s next Recurring check-in with Jamf, or upon a brand-new device enrollment in Jamf.
To do this, navigate to the General tab within the policy menu.
You’ll see two checkbox options: Enrollment Complete and Recurring Check-In. Enable both of these options. Doing so will allow the device to enroll on its next check-in into Jamf, or for brand-new devices, run after the initial enrollment process is complete. When completed, hit Save.
There are various ways to deploy the newly created SaaS Management policy within Jamf. One of the most common options is to configure the appropriate devices within the policy itself. To do this, re-open your policy and navigate to the Scope tab. From this menu, you can apply the policy on the next device check-in across specific users, specific computers, or specific groups of devices depending on how your Jamf environment is configured.
Jamf Pro Helpful Links
Deploying Custom Configuration Profiles with Jamf Pro:
Managing Policies with Jamf Pro:
https://learn.jamf.com/bundle/jamf-pro-documentation-current/page/Policies.html
Deploying Packages with Jamf Pro
https://docs.jamf.com/10.25.0/jamf-pro/administrator-guide/Package_Management.html
Running Scripts with Jamf Pro:
https://docs.jamf.com/10.27.0/jamf-pro/administrator-guide/Scripts.html