![use adobe cloud packager for mac use adobe cloud packager for mac](https://helpx.adobe.com/content/dam/help/en/enterprise/package/help/creating-packages/jcr%3Acontent/main-pars/procedure/proc_par/step_5/step_par/image/app-updates.png)
- #Use adobe cloud packager for mac how to#
- #Use adobe cloud packager for mac manual#
- #Use adobe cloud packager for mac Patch#
- #Use adobe cloud packager for mac mac#
#Use adobe cloud packager for mac mac#
As always, if you have any questions, queries or comments, let me know below (or on Mac Admins Slack) and I’ll try to respond to and delve into as many as I can.
#Use adobe cloud packager for mac how to#
This post covers how to create an AutoPKG recipe to only upload packages to your Jamf Pro server. I’ve uploaded an example of the changes to a Firefox recipe here. Well altogether, the process section of the recipe looks as follows: Process Please Note: In order to avoid confusion with already existing. The JSSImporter processor will automatically create this category if required, upload the package and set the category. But, it will also upload it without a category, so if you need / want this, you’ll need the second key: category That key alone will upload the package into your Jamf Cloud server without any of the Smart Groups or Policies. jss policy (in this case the Firefox one) and started removing the various Arguments keys until I found the minimum required.
#Use adobe cloud packager for mac Patch#
What if you could have the best of both worlds? What if you could use AutoPKG/r to package and upload software to your Jamf Cloud server, ready for you to link to your Patch Policies / Versions?
#Use adobe cloud packager for mac manual#
As explained in the previous post, this could be a manual task.Īlternatively you can use the AutoPKG recipes to package and upload your software patches, but this will also include smart groups and policies (since this pre-dates the Jamf Patch Management system). If you wish to utilise the included Patch Management system you will need to upload packages ready to link them to software versions. No smart groups, no policies, just the packages! But….Why?Ī fair question. Hi all, in a follow up to a previous post on using AutoPKGr with Jamf Cloud ( Using AutoPKGr with a Jamf Cloud Distribution Point), I worked with a second customer on how to use the same system, but only to upload the packages.
![use adobe cloud packager for mac use adobe cloud packager for mac](https://image3.slideserve.com/5417194/creative-cloud-packager-1-6-walk-through-for-cct-packaging-l.jpg)
Updated 2020.10.08 – As with all things committed to page, this topic has aged! I’ll leave the content up for context, but if you’re after this feature, take a look at the Wiki page here – Migrating macOS Devi… on Migrating macOS Devices from o…ĭazwallace on Moving devices from Adobe Shar…įoigus on Moving devices from Adobe Shar…ĭazwallace on Uninstalling Adobe Software