Avatar for Username

Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

Wątek został zarchiwizowany. Jeśli potrzebujesz pomocy, zadaj nowe pytanie.

Automatic updates

  • 4 odpowiedzi
  • 1 osoba ma ten problem
  • 8 wyświetleń
  • Ostatnia odpowiedź od Mike Kaply

rob.scott1
rob.scott1
more options

We have recently enabled background updates in our organization, however I noticed that a requirement for this to work is that Firefox needs to be run with the default profile at least once after the feature is enabled. The issue we have is that not all users are actively using Firefox and therefore they are not being updated. I realize the security flaws won't be exposed if it's not in use, but management doesn't like seeing out of date browsers. Is there a way to force auto updates on all device where Firefox isn't not being used. Background updating is working for the majority of those that do use Firefox.

Also, we do have a couple of users reporting a credential prompt when updating from 119 to 119.0.1. These same users had no issues updating from 118 to 119. I have not figured out why this is happening just yet and why only for a handful of users so far. Would anyone have an idea why that is happening?

We have recently enabled background updates in our organization, however I noticed that a requirement for this to work is that Firefox needs to be run with the default profile at least once after the feature is enabled. The issue we have is that not all users are actively using Firefox and therefore they are not being updated. I realize the security flaws won't be exposed if it's not in use, but management doesn't like seeing out of date browsers. Is there a way to force auto updates on all device where Firefox isn't not being used. Background updating is working for the majority of those that do use Firefox. Also, we do have a couple of users reporting a credential prompt when updating from 119 to 119.0.1. These same users had no issues updating from 118 to 119. I have not figured out why this is happening just yet and why only for a handful of users so far. Would anyone have an idea why that is happening?

Wszystkie odpowiedzi (4)

Terry
Terry
more options

With regard to the first question, you can install a policy.

https://support.mozilla.org/en-US/kb/customizing-firefox-using-group-policy-windows https://support.mozilla.org/en-US/kb/see-active-policies-firefox-enterprise

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

See also:

I will move the thread to Firefox for Enterprise.

rob.scott1
rob.scott1 Zadający pytanie
more options

Thanks for the reply, I should have mentioned that we have the latest policy set from github installed (v5.3).

From this page: https://support.mozilla.org/en-US/kb/enable-background-updates-firefox-windows, there is a requirement that states: Firefox must have a default profile, and it must run using that profile at least once after the feature is enabled - unless this does not matter if policies are set.

As far as I can tell, all the update policies are set to allow updates. About:policies shows AppAutoUpdate - True, DisableAppUpdate - false, BackgroundAppUpdate - true

One thing I did notice is that the Firefox Background Update task isn't created until after Firefox has been opened one time on the device.

Did I miss something?

Mike Kaply
Mike Kaply
  • Moderator
more options

Firefox does have to have been started at least once and have a profile in order for background updates to happen.