jss recipes, you may be contemplating having to write a bunch of. However, if your policy and smart group design is compatible with the “standard” design devised for. For example, if you’re using Patch Management, or creating multiple policies, JSSImporter recipes were not well designed for this, and you can benefit from the new opportunities available with JamfUploader. JamfUploader is designed to be more flexible than JSSImporter, so a straight conversion may well not be the best course of action. jss) recipes, so new recipes need to be written. The design is significantly different to JSSImporter-based (. jamf) recipes are modular in design (see my original blog post, JamfUploader - new AutoPkg processors for importing packages to Jamf Pro). The JamfUploader project is my replacement of JSSImporter, for Jamf Pro customers that want to continue to benefit from the power of AutoPkg for obtaining deployable packages for thousands of third party applications and other software. In case you missed it, the JSSImporter processor is deprecated, and will cease to function when Jamf remove basic authentication from the Classic API endpoints, which they have announced will happen sometime between August and December 2022.

What is jamf used for