Skip to main content

We like to use Patch Management for whatever we cannot patch with app installers but will use Patch Management for reporting even if there is an entry being used in app installers.


Sometime early last week we noticed that Microsoft Teams was listed in patch management as having the latest be 25122.1207.3700.1444. App installers never updated and even this morning it still reports 25107.1606.3643.3915 while patch management says 25151.505.3727.5755 is now the latest. I'll give that a little leeway since it says 17 min ago. It reads to me like patch management has a system in place for Teams that keeps it on top with the latest version but app installers not so much.


At any rate it seems a bit strange for patch management and app installers to not be in sync.


On a related note Jamf Connect 3.0 was recently released yet patch management says 3.2.0 is the latest and there is no 3.0 listed. Jamf Connect Login is listed as 3.0.0 and so is Jamf Connect Configuration. This confusion isn't super critical for us since we're in the middle of a trial for it but it's confusing nonetheless.


I have not sent any of this to support(yet) as sometimes there might be something someone can educate me from the community that might explain this rather than throwing possibly one more of the same inquiry to support.

Until such time as Jamf converts all of the App Installers over to using the vendor provided installer media (see https://www.jamf.com/blog/app-installers-whats-new/ for more info on that) there's going to be a lag in availability via the App Installer process after a vendor release. If the new process will provide App Installer updates as quickly as the Patch Management updates remains to be seen, but I expect it'll be close. 

Jamf updates the App Catalog (App Installers) usually the next business day after the developer releases the update. This seems pretty reasonable to me and allows time for testing, packaging, uploads and replication. Patch Management is also updated usually next business day after a developer releases an update, but is far less overhead as we manage the packages so there is less for Jamf to test.


 


My crystal ball says Jamf will retire Patch Management at some point. Honestly, Patch Management is little more than a Policy with built in Smart Groups and Extension Attributes.

Jamf updates the App Catalog (App Installers) usually the next business day after the developer releases the update. This seems pretty reasonable to me and allows time for testing, packaging, uploads and replication. Patch Management is also updated usually next business day after a developer releases an update, but is far less overhead as we manage the packages so there is less for Jamf to test.


 


My crystal ball says Jamf will retire Patch Management at some point. Honestly, Patch Management is little more than a Policy with built in Smart Groups and Extension Attributes.


I don't think Jamf publishes any specific SLA for how long between a publisher releases an update and that's reflected in the Patch Management and App Catalog offerings, but it's been my experience many of the Patch Management definitions will update the same day as a vendor change.


As for Patch Management I hope it isn't going anywhere since it supports adding arbitrary Patch definitions unlike the App Catalog which is limited to what Jamf offers. I greatly appreciate that Jamf offers both so customers can choose simplicity when appropriate, and customization when necessary.

I don't think Jamf publishes any specific SLA for how long between a publisher releases an update and that's reflected in the Patch Management and App Catalog offerings, but it's been my experience many of the Patch Management definitions will update the same day as a vendor change.


As for Patch Management I hope it isn't going anywhere since it supports adding arbitrary Patch definitions unlike the App Catalog which is limited to what Jamf offers. I greatly appreciate that Jamf offers both so customers can choose simplicity when appropriate, and customization when necessary.


I agree. We are trying to make more use of Installomater and App Installers. But I still find myself using Patch Management to catch stragglers. 


 


So we are a hybrid now.

Do you guys primarily use one more than the other? Or a combo, hybrid patch?

Reply


Terms & ConditionsCookie settings