Skip to main content
Question

Updating Patch Management packages automatically

  • December 30, 2019
  • 3 replies
  • 39 views
L
Forum|alt.badge.img+7

Hey,

my current Patch Management Workflow is to upload the newest version of an app as soon as an update is rolled out. I am doing this for Chrome, Firefox and all Office apps.

Over the holidays I ran into the problem that there were new versions released and I was not in the office to update them.

Does someone know of a way to automatically upload new versions into the patch management definitions and apply them? How do you guys manage this?

I think that I am maybe just missing an important point...

Best regards

3 replies

T
Forum|alt.badge.img
  • Tunaluna94
  • New Contributor
  • December 30, 2019

Depends on the app, I know for Chrome/ FireFox/ Adobe we have scripts that keep our software updated automatically. Instead of constantly having to repackage.

    T
    Forum|alt.badge.img
    • tgrimshaw
    • New Contributor
    • January 20, 2020

    https://github.com/autopkg/autopkg

    https://github.com/jssimporter/JSSImporter

    From Autopkg GitHub: "AutoPkg is an automation framework for macOS software packaging and distribution, oriented towards the tasks one would normally perform manually to prepare third-party software for mass deployment to managed clients."

    This should do exactly what you need.

    D
    Forum|alt.badge.img+1
    • duggan1972
    • New Contributor
    • April 12, 2021

    I'm working on moving away from Munki to Jamf and JSS exclusively. We currently have Autopkg running on our Munki instance, and I've looked into JSSImporter. However, after reading through the Wiki I saw this:

    JSSImporter's goal is to allow you to, with AutoPkg, automate the drudgery of managing a testing workflow. It is not meant to deploy software straight to production machines. It is not meant as a way to bootstrap all of a JSS's policies.

    I'm going to stick with making Patch Management work, and updating Policies for App deployment whether in JSS or silent install.

    Terms & ConditionsCookie settingsAccessibility statement