Home > Jamf Pro, Mac administration > Downloading installer packages from Jamf Pro when no other options are available

Downloading installer packages from Jamf Pro when no other options are available

Every so often, Mac admins who administer Jamf Pro may run into a situation like this:

  1. They need an installer package For Reasons.
  2. That installer package is only stored on their Jamf Pro server.
  3. They don’t have access to the distribution point which stores their Jamf Pro server’s installer packages.

In a situation like this, you can use a Jamf Pro policy to provide the installer to a specified Mac. For more details, please see below the jump.

To enable downloading an installer to a specified Mac using Jamf Pro, use the following procedure.

1. Create a policy in Jamf Pro.

Screenshot 2023 05 25 at 3 22 50 PM

2. Add the installer package to the policy.

3. Set the installer package’s Action to Cache.

Screenshot 2023 05 25 at 3 21 46 PM

Set policy trigger and scoping as preferred.

Once the policy runs on the Mac(s) it’s scoped to run on, Jamf Pro will download the installer package to the following directory on the Mac(s):

/Library/Application Support/JAMF/Waiting Room

Note: The Waiting Room directory is only accessible using root privileges.

Once the policy finishes running, you can collect the downloaded installer from /Library/Application Support/JAMF/Waiting Room.

Screenshot 2023 05 25 at 4 33 12 PM

  1. May 26, 2023 at 12:13 am

    Thanks, Rich. This is helpful 🙂

  2. Michael Crispin
    May 26, 2023 at 12:55 am

    The other useful technique here is to use Jamf Admin (the app), and drag a folder in the left side window. Then highlight said folder, and you will see a button on the bottom left to “Replicate” and then you can have a local copy of all your assets.

    • JimH
      May 26, 2023 at 1:18 pm

      Michael, if you’re on-premise, you’re over engineering things if you only need one package. When Jamf Admin is open with the drive mounted, open /Volumes. There you will find the smb share and can navigate to the pkg you need. I have no experience with Jamf Cloud so I can’t speak to that.

  3. Andreas Schenk
    May 26, 2023 at 5:09 am

    While this is a good addition in tools/workflows, I have been using Jamf CPR with the „save only“ option in these situations. Then you don’t need a policy.
    And probably it would be good, if the GUI just had a download button for each pkg.(I think there is a feature request for this, that we all should upvote)

  4. Sander
    May 26, 2023 at 5:55 am

    If you use the Jamf Cloud distribution point you can also use the following trick:

    1) Create a policy similar to your policy example, but add a custom trigger to it. In my example i use the trigger office365

    2) Open the terminal on a client device that is scoped to the policy

    3) In the terminal, run the policy with the custom trigger in verbose mode

    user@Macbook ~ % sudo jamf policy -trigger office365 verbose
    Checking for policies triggered by “office365” for user “user”…
    Executing Policy Microsoft Office 365 Business Pro – Install
    Downloading Microsoft Office Business Pro Suite-16.72.0.pkg…
    Downloading https://euc1-jcds.services.jamfcloud.com//download/a28e865336904d1197154f168d767530/Microsoft%20Office%20Business%20Pro%20Suite-16.72.0.pkg?token=173d5759c1a54ad0bcdd2af1a5b3d80ba9aubrac28lo3nyx3m9o5zcvvh2sbgka

    4) After a few seconds you can cancel the policy with control + C

    5) In the verbose feedback you can see the full URL, including the temporary token.

    6) Copy the URL (including the ?token=……..) and use this URL to download the package with you browser

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: