Re: [Mozilla Enterprise] Thunderbird 68.2.0 preinstalling add-ons

They can't be directories. They need to be XPI files named the same as the ID. Mike On Fri, Oct 25, 2019, 10:48 AM Osdoba, Sascha wrote: > Hi, > > until TB version 60.x I could preinstall addons during TB deployment via > SCCM per copying to >

[Mozilla Enterprise] Thunderbird 68.2.0 preinstalling add-ons

Hi, until TB version 60.x I could preinstall addons during TB deployment via SCCM per copying to "programfiles(x86)"\thunderbird\extensions\extensionID\" (we use TB x86 on Windows x64) and I deployed 5 or 6 addons without problems. Now with 68.2.0 its not working this way anymore but I did not

Re: [Mozilla Enterprise] Firefox msi detection in SCCM

Installer engineer here. We have bug 1505436 on file for this problem. This was a known limitation of the design of our MSI, but I didn't realize how big of a problem it would be in practice. I would like to do something about it, but there's

Re: [Mozilla Enterprise] Firefox msi detection in SCCM

In that case, I have some quick suggestions for the MSI "wrapper" deployment. * Turn off automatic updates for the MSI package? Use case for the big majority of MSI installations would be provisioning through SCCM/Intune or other deployment toolset. The user in these deployment scenarios

Re: [Mozilla Enterprise] Firefox msi detection in SCCM

It's not that we don't care it's that using a real MSI won't update properly using our infrastructure. It's simply not something we can do right now. Mike Kaply On Fri, Oct 25, 2019 at 7:17 AM Alexandre GAUVRIT wrote: > All these packaging problems were addressed to Mozilla teams many month >

Re: [Mozilla Enterprise] Firefox msi detection in SCCM

All these packaging problems were addressed to Mozilla teams many month ago, they just don't care : https://bugzilla.mozilla.org/show_bug.cgi?id=1511835 Don't go with MSI right now, stick to *.exe, since they're not able to release correctly formed packages. Regards Alex Le 25/10/2019 à 13:29,

Re: [Mozilla Enterprise] Firefox msi detection in SCCM

If it were a proper .msi and not .exe wrapper all those problems could go away. However I prefer .exe -wrapper that doesn't leave any trace of itself behind than something that pollutes computer with .msi reg entries and leaves them behind when user decides to uninstall program using

Re: [Mozilla Enterprise] [SPAMVERDACHT] Firefox msi detection in SCCM

I had the same problem in the test scenario. However, I do not vaccinate the WSUS via SCCM but via WPP. Since the .MSI is only a package for the .exe and not a full MSI installation, I still use the installation with .exe. If I have to add extra rules for the installation and deinstallation,

Re: [Mozilla Enterprise] Firefox msi detection in SCCM

I'm with you on that, Will - I don't feel that this should be "expected behavior" or "by design" for the MSI binaries. The allure of using MSIs is for classic win32 app consistency and convenience that "msiexec" brings for both installation and uninstallation by using the product code GUID.

Re: [Mozilla Enterprise] Firefox msi detection in SCCM

Thank for the quick response, Timo and John, I've had .msi installers in the past that barely did more than populate the application name. I'm assuming this aspect does something else, and populating the detection method is a side-effect... otherwise I fail to see the point. To be honest, if

Re: [Mozilla Enterprise] Firefox msi detection in SCCM

We use here file version of the firefox.exe as detection rule. Timo Pietilä On 25.10.2019 12.49, Gage, John wrote: Just adding confirmation to Timo's comments that using the MSI GUID will not work. - Will, I use SCCM heavily, and for my Firefox ESR Application's "Detection Method", I use

Re: [Mozilla Enterprise] Firefox msi detection in SCCM

Just adding confirmation to Timo's comments that using the MSI GUID will not work. - Will, I use SCCM heavily, and for my Firefox ESR Application's "Detection Method", I use the following "Detection Rule" instead of the MSI GUID: Setting Type: Registry Hive: HKEY_LOCAL_MACHINE Key:

Re: [Mozilla Enterprise] Firefox msi detection in SCCM

AFAIK that is by design. That msi is exe-wrapper and after install there is no trace that it was installed using .msi. You can't uninstall it using msiexec /x {productcode} either. You need to treat it like if it were installed using .exe. Timo Pietilä On 25.10.2019 11.52, William Spratt

[Mozilla Enterprise] Firefox msi detection in SCCM

Hi All, So with the 68.2 ESR release, I thought I'd try pushing it out with the new .msi installer. We use SCCM to push out Firefox, and this has worked fine with the .exe versions, manually configuring SCCM to check the file version of "C:\Program Files\Mozilla Firefox\firefox.exe" to

[Mozilla Enterprise] Tabs on bottom

Hello. Just a suggetion to future FF releases: could we please get back the option to put tab bar back where it belongs below bookmark toolbar. Now to do that you need to tweak userchrome.css etc. files to get that done. This is nice place to fix that: