12-21-2023 11:04 AM - edited 12-21-2023 11:12 AM
I just got autopkgr installed and it's copying the built packages to my distribution point. What it's not doing is creating a policy. I've checked that the account has the privileges specified in the readme. I don't see anything helpful in the logs. Anything else that I can check? The category already exists in Jamf, so it should just show up in the category?
Posted on 12-21-2023 11:13 AM
@ChrisTech Is the recipe something you created, or one someone else wrote? And is the recipe using the JamfUploader JamfPolicyUploader processor (see https://github.com/grahampugh/jamf-upload/wiki/JamfUploader-AutoPkg-Processors), or just a JamfPackageUploader processor?
Posted on 12-21-2023 11:20 AM
It's not something I created, it's using the JamfUploader integration inside AutoPkgr. I am testing out the 'zoom.us.jamf' recipe.
Posted on 12-21-2023 11:41 AM
Can you post a link to that recipe? It's possible the only thing that recipe does is upload a package since some/most people may not want an autopkg recipe creating policies for them.
12-21-2023 11:53 AM - edited 12-21-2023 12:03 PM
Posted on 12-21-2023 12:11 PM
That recipe make use of JSSImporter, and if you look at the JSSImporter GitHub page it shows the following message:
This project is deprecated and is likely to stop functioning with upcoming versions of Jamf Pro. Please consider using JamfUploader instead.
Posted on 12-21-2023 12:14 PM
I posted the wrong one. The link now is to the correct recipe.
Posted on 12-21-2023 12:30 PM
Have you created the JamfPolicyTemplate.xml template file that recipe relies on? See https://github.com/grahampugh/jamf-upload/wiki/JamfUploader-Templates for more info on JamfUploader templates.
Posted on 12-22-2023 09:51 AM
Thanks @sdagley that got me pointed in the right direction. It still wasn't working for me because the package was uploaded already and I needed to do a
autopkg run zoom.us.jamf --key replace_pkg=True
before it would show up. Thanks for the link.