If the package is an installer and the installer runs but doesn't error out then there's no way for JAMF to know it failed.
I know this happened when I had institutional Adobe CC installs run on a computer that didn't meet the system requirements - the installer would finish without errors but no software.
This issue we are having is that absolutely nothing at all installs - and this is on models that can definitely run the software. Not one thing is installing. So there's got to be a configuration issue (or user error) somewhere. Even the jamf.log file shows successful installs with no error.
That the odd thing - the install log shows that it was successful. And I can't even place a pkg file on to the target Mac. All I can do is have the Mac view the Self Serve Store and kick off an install (that says successful even though it is not) but can't do ANYTHING else... even though it looks like everything is working.
I've got Jamf Support involved and so far, they haven't been able to figure it out. I was hoping someone might have run into this issue. It is literally ANY package. All logs show nothing but successful installs. Installing locally works fine - it only fails when trying to use JAMF. The packages do not require anything special, by the way. It seems to be a configuration issue. All of the problems started when the IP address of our file distribution point changed (and I subsequently updated the IP address in JAMF Pro to reflect the new address). I can see the Macs, I can send policies to them, etc. I just can not push software to them from the Distribution point (which is physical, not a cloud share).