Systems

Jamf Pro

Affected Customers

University of Illinois IT Pros leveraging Technology Services Endpoint Services Jamf Pro

General Information

For applications not available via the Apple App Store or the Jamf App Catalog, IT Pros can deploy software and other configurations using standard macOS .pkg installers uploaded to Jamf Pro. This method is commonly used for licensed, custom, or niche applications. Packages in Jamf Pro can be configured to install automatically or be made available for on-demand install by end users in the Jamf Pro Self Service+ application. Note: .dmg installers or applications must be repackaged as .pkg installers using tools such as Jamf Composer prior to being uploaded to Jamf Pro.

Only Endpoint Services staff can upload packages (.pkg) to Jamf Pro on behalf of IT Pros. Additionally, Endpoint Services maintains many widely used software packages in Jamf Pro for deployment by campus IT Pros. Package installers provided by EPS can be found in the Jamf Pro console at the Full Jamf Pro level at Computers → Policies, and have a "Global" prefix and category of either "Software" or "Software Licensed". Packages uploaded on behalf of IT Pros that contain custom or department-specific licensing or configurations typically have the IT Pro's department site prefix appended to the beginning. To request that a new departmental package be uploaded to Jamf Pro or to request that a new application be added and maintained by the Endpoint Services team, IT professionals should contact the Endpoint Services team.  

Actions

• On-demand Installs
• Automatic Installs

On-demand Installs

On-demand packages in Jamf Pro are made available for installation by end users in the Jamf Pro Self Service+ application and are only installed on a computer if installation is triggered by a user via the Install or Reinstall button.

Once a package has been uploaded to Jamf Pro by the Endpoint Services team:

• If the package was configured as a globally available on-demand application by the Endpoint Services team, no additional action is required by IT Pros and users can install the package or application via the Jamf Pro Self Service+ application.
• If the package was not configured as a globally available on-demand application, as is typical for packages that contain custom or department-specific licensing or configurations, IT Pros will need to create a site level policy with the desired automation trigger and uploaded .pkg:
  1. Login to the Jamf Pro console
  2. Ensure that you are in your department's site view using the dropdown in the top-right corner of the Jamf Pro console.
  3. Create a new Jamf Pro policy in the Jamf Pro console at Computers → Policies using the + New button.
  4. On the Options tab of the policy:
     • In the General node of the policy window:
       • Configure the Display Name, being sure to place your Jamf Pro site prefix at the beginning of the package policy.
       • Set the policy category to an appropriate category for the package's intended purpose.
       • Do not configure any triggers except for Custom Event triggers, which can be optionally configured
       • Set the Execution Frequency to Ongoing.
     • In the Packages node of the policy window:
       • Locate and add the package that was uploaded by the Endpoint Services team, configure it with an Install action.
     • Locate the Maintenance node of the policy window and click the Configure button.
       • Ensure that Update Inventory is checked.
  5. On the Scope tab of the policy, target the new policy at the desired deployment target, such as a computer group.
  6. As we want users to install the on-demand package themselves via the Self Service application, locate the Self Service tab of the policy and check the Make the policy available in Self Service checkbox.
     • Set the Self Service category an appropriate category for the package's intended purpose.
     • Update any other Self Service fields as desired.
  7. Save the policy.

Automatic Installs

Automatic Jamf Pro App Catalog applications install on computers following device enrollment without any action from users. They are configured at the site level by departmental IT professionals within the Jamf Pro console.

Once a package has been uploaded to Jamf Pro by the Endpoint Services team:

• If the package is already available as a globally available on-demand application by the Endpoint Services team, IT Pros can utilize their Jamf Pro custom triggers in their site level policies to trigger an automated install without the need to manually maintain packages within policies when they're updated by the Endpoint Services team.
  1. Login to the Jamf Pro console
  2. At the Full Jamf Pro view, locate the globally available on-demand application in the Jamf Pro console at Computers → Policies. Take note of the global policy's Custom Event trigger (e.g., InstallFirefoxESR)
  3. Switch to your department's site view using the dropdown in the top-right corner of the Jamf Pro console.
  4. Create a new Jamf Pro policy in the Jamf Pro console at Computers → Policies using the + New button.
  5. On the Options tab of the policy:
     • In the General node of the policy window:
       • Configure the Display Name, being sure to place your Jamf Pro site prefix at the beginning of the package policy.
       • Set the policy category to an appropriate category for the package's intended purpose.
       • Configure the desired automation triggers.
       • Set the desired Execution Frequency
         • Ongoing should only be used in conjunction with smart groups to avoid repeated executions (i.e., applications reinstall every check-in).
     • Locate the Maintenance node of the policy window and click the Configure button.
       • Ensure that Update Inventory is checked.
     • Locate the Files and Processes node of the policy window and click the Configure button.
       • In the Execute Command field, call the global level app trigger using the Jamf Pro policy command, for example:

         • jamf policy -event InstallFirefoxESR

  6. On the Scope tab of the policy, target the new policy at the desired deployment target, such as a computer group.
  7. On the the Self Service tab of the policy, do not configure anything.
  8. Save the policy.
• If the package was not configured as a globally available on-demand application, as is typical for packages that contain custom or department-specific licensing or configurations, IT Pros will need to create a site level policy with the desired automation trigger and uploaded .pkg:
  1. Login to the Jamf Pro console
  2. Ensure that you are in your department's site view using the dropdown in the top-right corner of the Jamf Pro console.
  3. Create a new Jamf Pro policy in the Jamf Pro console at Computers → Policies using the + New button.
  4. On the Options tab of the policy:
     • In the General node of the policy window:
       • Configure the Display Name, being sure to place your Jamf Pro site prefix at the beginning of the package policy.
       • Set the policy category to an appropriate category for the package's intended purpose.
       • Configure the desired automation triggers.
       • Set the desired Execution Frequency
         • Ongoing should only be used in conjunction with smart groups to avoid repeated executions (i.e., applications reinstall every check-in)
     • In the Packages node of the policy window:
       • Locate and add the package that was uploaded by the Endpoint Services team, configure it with an Install action.
     • Locate the Maintenance node of the policy window and click the Configure button.
       • Ensure that Update Inventory is checked.
  5. On the Scope tab of the policy, target the new policy at the desired deployment target, such as a computer group.
  6. On the the Self Service tab of the policy, do not configure anything.
  7. Save the policy.

Contact the EPS team