Additionally since I have SCCM my version detection is made so a baseline is detect like for version 38 of FFESR I have it so it detects FF as installed if the version string matches 38 or higher... Since I update the package once a year I let the browser upgrade itself and I update the package I increment the minimum version detection up to the latest package so any box lingering behind gets pushed an update.
:) From: Eric Periard Sent: Friday, March 18, 2016 4:04 PM To: [email protected] Subject: RE: [Mozilla Enterprise] Legit Firefox MSI HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall Anything installed on your system will leave a trace there, if you're using SCCM/SMS solution you can trigger the detection from there or simply point it to the firefox.exe inside its installation directory.... Eric From: Enterprise [mailto:[email protected]] On Behalf Of Skrivseth, Daniel Sent: Friday, March 18, 2016 11:52 AM To: Acosta, David; [email protected]<mailto:[email protected]> Subject: Re: [Mozilla Enterprise] Legit Firefox MSI I use a File System detection with the following settings. Type: File Path: %ProgramFiles%\Mozilla Firefox File or folder name: firefox.exe Check the box labeled "This file or folder is associated with a 32-bit application on 64-bit systems". Choose the option "The file system setting must satisfy the following rule to indicate the presence of this application" Property: Version Operator: Greater than or equal to Value: 45.0 Obviously you choose the value appropriate to the version you are deploying. Daniel Skrivseth Infrastructure Engineer Milwaukee Center for Independence (MCFI) [email protected]<mailto:[email protected]> www.mcfi.net<http://www.mcfi.net/> From: Enterprise [mailto:[email protected]] On Behalf Of Acosta, David Sent: Friday, March 18, 2016 10:26 AM To: [email protected]<mailto:[email protected]>; Timo Pietilä <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Subject: Re: [Mozilla Enterprise] Legit Firefox MSI What do you use when using the exe installer, for detection method? For me when I have an msi, the created detection method, seems to be the most reliable, I then go back to change the installer to my script or exe (like Office) Dave David E. Acosta Network Administrator Randolph Township Schools Technology Department [email protected]<mailto:[email protected]> (O) 973-361-0808 x7205 (C) 201-317-5961 From: Enterprise [mailto:[email protected]] On Behalf Of [email protected]<mailto:[email protected]> Sent: Friday, March 18, 2016 11:15 AM To: Timo Pietilä <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Subject: Re: [Mozilla Enterprise] Legit Firefox MSI Hello, Yes MSI technology is slower than other installation technologies (Inno Setup, NSIS, etc.) in any environment. Moreover it takes several month to master the art of creating good msi packages. (Even some Microsoft products are not delivered with an msi installer...) For Firefox we do not need repackaging because all the corporate settings are applied separately by another package. But if we needed repackaging we would certainly not use msi repackaging. For all our SCCM packages we create some script that launches the original installer (silent mode), then our script goes on and applies some corporate settings. By using the original installer we have a better chance to obtain a good (and standard) installation or upgrade and we do not spend much time in repackaging. (Yes some of them are .msi packages, we use them but do not try to modify them. Some of them have issues with re-installation, repair, upgrades... Our scripts have to deal with this.) For Firefox we do not disable the autoupdate: in the ESR branch, autoupdate only applies security fixes so why would we disable this? (By the way in our environment the FF auto-update is not efficient: only 50% updated systems after 3 weeks. So we re-deploy the new installation package with SCCM. It updates all the machines in 3 days, 12000 machines all over the world.) If we needed to disable autoupdate I suppose we would try installing with a .ini file containing "MaintenanceService=false" ( see here : https://wiki.mozilla.org/Installer:Command_Line_Arguments ) or figure out some other way to disable or uninstall it inside our script just after the installation.) Hope this will help :) -----Original Message----- From: Enterprise [mailto:[email protected]] On Behalf Of Timo Pietilä Sent: Thursday, March 17, 2016 15:40 To: [email protected]<mailto:[email protected]> Subject: Re: [Mozilla Enterprise] Legit Firefox MSI On 17.3.2016 12:53, [email protected]<mailto:[email protected]> wrote: > Hello, > > The MSI installation technology is not mandatory for SCCM : We deploy > Firefox ESR with an SCCM package using the.exe installer. Our > installation script mainly launches the command "Firefox Setup > 38.7.0esr.exe -ms". It works to install for the 1^st time but also to > update an existing Firefox (Very quick installation or update: not > like > MSI...) Could you elaborate a bit that last point? Is msi somehow slower in your environment than exe? Or did you just mean that you don't need to repackage it? Do you add or change any prefs in FF using that (like disable autoupdate)? Timo Pietilä _______________________________________________ Enterprise mailing list [email protected]<mailto:[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]<mailto:[email protected]> with a subject of "unsubscribe" _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. This message may contain information which may be privileged or confidential and is intended for the sole use of the individual or entity to which it is addressed. It is prohibited for anyone else to disclose, copy, distribute or use the contents of this message for any purpose whatsoever. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please immediately notify the sender by reply email and delete/destroy the original message and any copy of it from your computer or paper files. Personal messages, if any, express the views of the individual sender only, and not that of the Agency.
_______________________________________________ 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"
