Hi Petri,
I sent an email to you this morning which points to where the problem originated and also provides you with steps to solve the issue by using the "Perform Clean Install" setting in our Firefox packages. For the sake of transparency to help other users who might run into this, here is what causes such issues:
https://support.mozilla.org/en-US/questions/1173274
Attached to this comment you will also find a quick screenshot showing the options that could solve this.
To solve such issue, new package must be re-deployed to affected systems with this enabled in it.
Machines that already ran previous package with the newest versions might need package re-enforcement.
This could be done by enabling the "AlwaysInstallable" option, but then you have to approve the patch only to machines who have Firefox on them via WSUS/SCCM and be careful to not include systems that didn't have it.
‎Apr 18, 2019 05:22 AM
‎Apr 16, 2019 10:22 AM
Hi Petri,
I sent an email to you this morning which points to where the problem originated and also provides you with steps to solve the issue by using the "Perform Clean Install" setting in our Firefox packages. For the sake of transparency to help other users who might run into this, here is what causes such issues:
https://support.mozilla.org/en-US/questions/1173274
Attached to this comment you will also find a quick screenshot showing the options that could solve this.
To solve such issue, new package must be re-deployed to affected systems with this enabled in it.
Machines that already ran previous package with the newest versions might need package re-enforcement.
This could be done by enabling the "AlwaysInstallable" option, but then you have to approve the patch only to machines who have Firefox on them via WSUS/SCCM and be careful to not include systems that didn't have it.
‎Apr 18, 2019 05:22 AM