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 wrote:
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 verify the
install/update was successful. When we import the 68.2 .msi into SCCM,
it does handy things like automatically populate the install detection
method to check for {1294A4C5-9977-480F-9497-C0EA1E630130} in the msi
directory. Unfortunately, while the Firefox .msi runs successfully,
installing/updating to 68.2, it doesn’t detect that reference in the
.msi directory.
Has anyone else experienced this? Should I log a bug report?
Regards
Will
**
*Will Spratt*
*IT Scientific Support Specialist*
*Fera Science Ltd.***
[email protected] <mailto:[email protected]>| Tel +44
(0)1904 46 2631 | Mob +44 (0)7810855621
www.fera.co.uk <http://www.fera.co.uk/>| Twitter
<https://twitter.com/ferascience>| LinkedIn
<https://www.linkedin.com/company/fera-science> | YouTube
<http://www.youtube.com/user/FeraUK1>
_______________________________________________
Enterprise mailing list
[email protected]
https://mail.mozilla.org/listinfo/enterprise
To unsubscribe from this list, please visit https://mail.mozilla.org/listinfo/enterprise
or send an email to [email protected] with a subject of
"unsubscribe"
_______________________________________________
Enterprise mailing list
[email protected]
https://mail.mozilla.org/listinfo/enterprise
To unsubscribe from this list, please visit https://mail.mozilla.org/listinfo/enterprise
or send an email to [email protected] with a subject of
"unsubscribe"
