Skip to main content

Hi All,

 

We did the update to a more recent version of Jamf Pro. We lost the Jamf Admin.app feature and now I'm having issues getting packages into Jamf Pro. I have tried using Jamf Sync, and also just copying the files directly to one of our FSD points. Then I create the package entry under Settings -> Computer Management -> Packages  with the package filename as the display name and add the filename of the package and save.

 

Here's what I am seeing:

 

 It's not even trying to install the package from an FSD. I had a similar situation a few weeks ago, and it just starting working on its own, so I am wondering do I have to do anything else for Jamf to 'see' the package? We have 24 FSD points, do I need to sync the file with each FSD? I thought it used to sync automatically if I added the file to the principal distribution point. 

 

Any info is helpful..  

How are you uploading packages? 

I've tried directly copying them to the fileshare and with Jamf Sync. 

I've tried directly copying them to the fileshare and with Jamf Sync. 


Directly copying them to the file share won't work, there is more that needs to happen than for the files to exist on the share. 

 

What output are you getting from Jamf Sync when trying to upload files? It uses Jamfs API to upload packages much like Jamf Admin did, it just uses the newer API.

Directly copying them to the file share won't work, there is more that needs to happen than for the files to exist on the share. 

 

What output are you getting from Jamf Sync when trying to upload files? It uses Jamfs API to upload packages much like Jamf Admin did, it just uses the newer API.


"Directly copying them to the file share won't work, there is more that needs to happen" what more needs to happen? My understanding is the latest version of Jamf does not need indexing or checksum of the file to be preformed. I have Jamf pro 11.8 in our dev (we are on 10 in production) and I have tested doing what the above poster did, copied the PKG to a share (since Jamf admin no longer works with 11) and it seems like it's working here. Am I missing something?

 

The Jamf documentation says this:

  • Manual upload—If you do not have a cloud distribution point configured as your principal distribution point (e.g., you have a file share distribution point), you can manually upload the package to your distribution point and create a matching package record in Jamf Pro. This method involves manually copying the package to the distribution point and then entering information about the package in Jamf Pro. For more information, see Manually Adding a Package to a Distribution Point and Jamf Pro.

@BCPeteo Yep. That's exactly what I am doing. So I got in to work today, and the package is installing now. ¯\\_(ツ)_/¯ 

I reached out to Jamf Support to see if there is some process that runs so Jamf Pro 'sees' the package. Weird right?

@BCPeteo Yep. That's exactly what I am doing. So I got in to work today, and the package is installing now. ¯\\_(ツ)_/¯ 

I reached out to Jamf Support to see if there is some process that runs so Jamf Pro 'sees' the package. Weird right?


Interesting. Do you have more than one DP? Because you need to use the sync program on manually upload the package to both.

We have 24 distro points. I uploaded the package to the main distro point and my laptop that I was testing on is set to use that distro point as defined in network segments. What I usually see is Jamf at least looking for the package, which you can see in the screenshot it isn't saying the package is missing.

We have 24 distro points. I uploaded the package to the main distro point and my laptop that I was testing on is set to use that distro point as defined in network segments. What I usually see is Jamf at least looking for the package, which you can see in the screenshot it isn't saying the package is missing.


yeah Its not showing any data for step 2 or 3. On the successfully deployment does it show data for those steps? 

Yep. After sitting all weekend, it worked on Monday morning. 

 

Ok, so 24 hours later, the policy is working. I did notice that when uploading packages with Jamf Sync the package entry is added to Jamf Pro. I didn't do anything on my end. 

Ok, so 24 hours later, the policy is working. I did notice that when uploading packages with Jamf Sync the package entry is added to Jamf Pro. I didn't do anything on my end. 


Cool. How is Jamf sync have you had good success with it? was it easy to set up?

It was not hard at all. I created a folder on my NAS to store local packages and just pointed the program to my Jamf Pro server and it found all my FDPs. I just open Jamf Sync, select my local folder and then select the FDP and hit the Synchronize button and it uploads the packages. 

It was not hard at all. I created a folder on my NAS to store local packages and just pointed the program to my Jamf Pro server and it found all my FDPs. I just open Jamf Sync, select my local folder and then select the FDP and hit the Synchronize button and it uploads the packages. 


That sounds good. The only thing I would worry about is if the NAS store/SMB share changes, Like packages being removed then it will remove the packages from all FDP's. So I guess you would need another dedicated network storage setup to sync the DP's

Terms & ConditionsCookie settingsAccessibility statement