Skip to main content
Solved

Patch Management - Not updating

R
Forum|alt.badge.img+4

Hi Team,

Hope everyone had a great weekend.

I have a question related to Patch Management. So I was able add my current package (Ver.108.0.1) to the Definition tab as well as I was able to add some machines to my scope as a 'TEST' along with the target version of the program that I want installed. I was wondering if there's anything else that I need in order to get these machines updated or do I just give them time and they will populate on their own? Here are some screenshots of what I've done so far. - I'm sure there's an answer somewhere on here, but I can't seem to find it. - Thanks.

 

Best answer by Jaykrishna1

Hi Rdeleon,

Everything looks fine based on the screenshot. You mentioned that you wanted to upgrade your Firefox to the latest version 144.0.1, but please note that the most recent version is now 144.0.2, which was released recently. If any machines are still running version 144.0.1 or below, the patch will be triggered for those machines. Additionally, I couldn't find any pending or completed machines in the patch policies in the second screenshot. Please double-check the scoping settings, particularly the test smart group that you have selected.

I hope this information is helpful to you.

View original
    Did this topic help you find an answer to your question?

    6 replies

    sdagley
    Forum|alt.badge.img+25
    • sdagley
    • Jamf Heroes
    • 3540 replies
    • June 27, 2023

    @rdeleon What version of Firefox is currently deployed on your Macs? You appear to be trying to set things up to downgrade any install currently at version 114.0.1 to version 108.0.1 but you don't have the Allow Downgrade option enabled in your patch policy, and if your Mac have already upgraded to version 114.0.2 then the policy for 114.0.1 will ignore them.

    Jaykrishna1
    Forum|alt.badge.img+7
    • Jaykrishna1
    • Jamf Heroes
    • 81 replies
    • Answer
    • June 27, 2023

    Hi Rdeleon,

    Everything looks fine based on the screenshot. You mentioned that you wanted to upgrade your Firefox to the latest version 144.0.1, but please note that the most recent version is now 144.0.2, which was released recently. If any machines are still running version 144.0.1 or below, the patch will be triggered for those machines. Additionally, I couldn't find any pending or completed machines in the patch policies in the second screenshot. Please double-check the scoping settings, particularly the test smart group that you have selected.

    I hope this information is helpful to you.

    aparten11
    1 person likes this
    • aparten11
      aparten11
    mickl089
    Forum|alt.badge.img+11
    • mickl089
    • Valued Contributor
    • 147 replies
    • June 27, 2023

    114.0.2 ;-)

    R
    Forum|alt.badge.img+4
    • rdeleon
    • Author
    • Contributor
    • 20 replies
    • June 28, 2023
    sdagley wrote:

    @rdeleon What version of Firefox is currently deployed on your Macs? You appear to be trying to set things up to downgrade any install currently at version 114.0.1 to version 108.0.1 but you don't have the Allow Downgrade option enabled in your patch policy, and if your Mac have already upgraded to version 114.0.2 then the policy for 114.0.1 will ignore them.


    Hey@sdagley Currently, I'm doing a test batch of users first and some are currently running 108.0.1. Ideally, I was trying to update to the version before the new version because I didn't want to run into any bugs. I did notice that some of my machines updated on their own when I went to "About Firefox" on the top left corner to the latest version 114.0.2. The weird thing is it doesn't seem that it hasn't checked in JAMF yet so I was wondering if that take time as well.

    R
    Forum|alt.badge.img+4
    • rdeleon
    • Author
    • Contributor
    • 20 replies
    • June 28, 2023
    Jaykrishna1 wrote:

    Hi Rdeleon,

    Everything looks fine based on the screenshot. You mentioned that you wanted to upgrade your Firefox to the latest version 144.0.1, but please note that the most recent version is now 144.0.2, which was released recently. If any machines are still running version 144.0.1 or below, the patch will be triggered for those machines. Additionally, I couldn't find any pending or completed machines in the patch policies in the second screenshot. Please double-check the scoping settings, particularly the test smart group that you have selected.

    I hope this information is helpful to you.


    Hey @Jaykrishna1 Prior to replying back to you guys, I had a few machines with Ver 108.0.1. So far, I have one machine that is set to pending because I noticed that on other machines that had version 108.0.1 were able to update on their own once I went to "About Firefox" to Ver 114, but they don't show as completed in my Mozilla Firefox patch management group so I was wondering does that take time as well? The machine in the screenshot has been on "Pending" for a while. I'm assuming that the machine is on sleep mode at the moment.

    sdagley
    Forum|alt.badge.img+25
    • sdagley
    • Jamf Heroes
    • 3540 replies
    • June 28, 2023
    rdeleon wrote:

    Hey@sdagley Currently, I'm doing a test batch of users first and some are currently running 108.0.1. Ideally, I was trying to update to the version before the new version because I didn't want to run into any bugs. I did notice that some of my machines updated on their own when I went to "About Firefox" on the top left corner to the latest version 114.0.2. The weird thing is it doesn't seem that it hasn't checked in JAMF yet so I was wondering if that take time as well.


    @rdeleon If you don't enable the Allow Downgrade option then Patch Management will ignore any Mac which already has a newer version installed. You'd also want to establish a 108.0.1 patch policy if that's the version you're targeting, and if you want 104.0.1 use the installer for that version on that patch policy, not the 108.0.1 installer. None of that will be especially helpful if automatic updates are enabled by the installer you're using (or if the user has enabled it).

    Reply


    Most helpful members this week

    Terms & ConditionsCookie settingsAccessibility statement

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie settings