Avatar for Username

Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

Эта тема была архивирована. Если вам нужна помощь, задайте новый вопрос.

Firefox for enterprise setting up with MS Intune

  • 3 ответа
  • 1 имеет эту проблему
  • 14 просмотров
  • Последний ответ от Mike Kaply

MDragon1
MDragon1
more options

I am attempting to setup Mozilla for enterprise version 81.0 (x64) to deploy through Intune and update the previous versions on our client laptops. I set up Intune with the following detection rule(attached). The idea is that Intune looks for this registry key and if its not at version 81.0 it pushes out the updated MSI file. What happens so far is that when I have a older version installed such as 74.0. Intune DOESN'T push out the update. However when I completely remove Firefox within minutes Intune detects that its not installed and pushes out the current version. Therefore it would appear that the detection rule works but not as intended. A attempted to adjust the value on the detection rule with no success. The original detection rule was to detect a file inside program files\mozilla firefox. However that rule would not detect the current version installed.

Any ideas would be helpful.

I am attempting to setup Mozilla for enterprise version 81.0 (x64) to deploy through Intune and update the previous versions on our client laptops. I set up Intune with the following detection rule(attached). The idea is that Intune looks for this registry key and if its not at version 81.0 it pushes out the updated MSI file. What happens so far is that when I have a older version installed such as 74.0. Intune DOESN'T push out the update. However when I completely remove Firefox within minutes Intune detects that its not installed and pushes out the current version. Therefore it would appear that the detection rule works but not as intended. A attempted to adjust the value on the detection rule with no success. The original detection rule was to detect a file inside program files\mozilla firefox. However that rule would not detect the current version installed. Any ideas would be helpful.
Приложенные скриншоты

Все ответы (3)

Mike Kaply
Mike Kaply
  • Moderator
more options

CurrentVersion includes extra text at the end which probably breaks the version compare:

82.0 (x64 en-US)

You should compare against the (Default) value in Mozilla Firefox which is set to a correct version. See attachment.

MDragon1
MDragon1 Задавший вопрос
more options

Thanks for your response and made the changes. However on my test system which I have version 74.0 installed it will NOT push the updated 81 version we have loaded in intune. Attached is a screenshot of my detection rule settings as they are currently.

I am also attaching a screenshot of the firefox ADMX we have set up.

We enabled the APPUPDATE OMA-URI rule in our ADMX setup. However it seems to only remove the option for the end user to select their update option.

Is there a rule that will force the update to install after it is downloaded?

What we might do is move the Mozilla to our MS store to avoid these problems in with future deployments. Unless we can find a way to reliably push out updates through Intune.

Mike Kaply
Mike Kaply
  • Moderator
more options

I've exhausted my knowledge :)

This is the kind of question that is probably better asked on our enterprise mailing list:

https://mail.mozilla.org/listinfo/enterprise

It's a lot of folks that have done these kind of deployments and probably have more specific knowledge