Овај сајт ће имати ограничену функционалност док га будемо ажурирали у циљу побољшања вашег искуства. Ако неки чланак не реши ваш проблем и желите да поставите питање, на располагању ће вам бити наше заједнице подршке @FirefoxSupport на Twitter-у и /r/firefox на Reddit-у.

Претражи подршку

Избегните преваре подршке. Никада од вас нећемо тражити да зовете или шаљете поруке на број или да делите личне податке. Пријавите сумњиве радње преко „Пријавите злоупотребу” опције.

Сазнај више

Firefox GPO disables updates for both ESR and customer version

  • 4 одговорa
  • 2 имају овај проблем
  • 16 прегледа
  • Последњи одговор послао hozekes

more options

We use GPO for Firefox ESR and we disable update using the GPO and it works perfect. However some developers need to test with the Firefox Customer version and the GPO disables the update for the customer version as well. Is there a possibility to split the GPO in half and let us the choice which version we would like to disable the update?

Thanks in advance.

We use GPO for Firefox ESR and we disable update using the GPO and it works perfect. However some developers need to test with the Firefox Customer version and the GPO disables the update for the customer version as well. Is there a possibility to split the GPO in half and let us the choice which version we would like to disable the update? Thanks in advance.

Изабрано решење

As far as I know we don't have the ability to split the GPO in "half." I think your best bet would to put them in a test group and go from there.

Прочитајте овај одговор са објашњењем 👍 0

Сви одговори (4)

more options

Do you have the ability to move their computers to a new tree and apply the specific GPO you want to this?

more options

Thanks for your reply, unfortunately we don't have the ability. We don't have an overview of all the computers who need the consumer version of Firefox and they aren't in just one group of people.

more options

Одабрано решење

As far as I know we don't have the ability to split the GPO in "half." I think your best bet would to put them in a test group and go from there.

more options

Thanks for the reply. That solves it. If somewhere in the future you guys will implement it that would be very kind. :-)