Thanks for the response Klaus,
Issue here is my org is looking to switch from users installing public releases
to an SCCM controlled ESR implementation. I have the ESR package as they wish,
but realistically the public releases are almost always numerically higher than
the ESR ones, ie: the upcoming ESR is 45.4 where the upcoming public release is
49, so numerically it will always be seen as a downgrade even if waiting for
the next release cycle. In my case SCCM sees it as numerically higher =
installed and calls it a success.
What I was looking for was whether anyone had run into this with SCCM and if
they had found a way to get around it short of an uninstall. The SCCM piece
works fine as long as the installed version is of a lesser numerical value, but
such isn’t always the case with our installed base since users have been
allowed to freely install. Matthew Haley’s solution was what I figured I was
going to have to do, and your explanation lends further credence I just didn’t
know if anyone had encountered an alternative.
Thanks!
Roger
On 9/14/16, 3:25 AM, "Enterprise on behalf of Klaus Hartnegg"
<enterprise-boun...@mozilla.org on behalf of hartn...@uni-freiburg.de> wrote:
Am 13.09.2016 um 21:56 schrieb Crawford, Roger:
> Trying to package ESR 45.3 into a SCCM 2012 package, have that all
> functional and installs like a breeze – on a machine with no install
> or lower than 45. Higher than 45 it sees the newer version and calls
> itself successful due to versioning and bails. Is there a Firefox
> CFG switch that allows the overwrite of a newer than 45.3 version
> since public is at 48 and change or do I need to script in an
> uninstall before proceeding with the ESR install?
Mozilla recommends to not downgrade, e.g. from 48 to 45.
Because they often include preliminary versions of new features together
with a preference setting to turn it off, such that only beta testers
try it. Then in a later version, when the new feature has been debugged,
they change the default to on. If you now downgrade, you can get the
broken earlier version of the new feature installed, and the preference
setting is now on for existing users, if they ran the newer version at
least once.
Also sometimes Mozilla changes the type of a preference in a
non-compatible way, e.g. from boolean to integer, and later versions
include an automatic conversion. That conversion works only in the
forward direction. The old version will not handle the converted value
correctly, either not run at all, or not honour that setting.
It is safer to do the switch when the next ESR cycle starts.
_______________________________________________
Enterprise mailing list
Enterprise@mozilla.org
https://mail.mozilla.org/listinfo/enterprise
To unsubscribe from this list, please visit
https://mail.mozilla.org/listinfo/enterprise or send an email to
enterprise-requ...@mozilla.org with a subject of "unsubscribe"
This message is private and confidential. If you have received it in error,
please notify the sender and remove it from your system.
_______________________________________________
Enterprise mailing list
Enterprise@mozilla.org
https://mail.mozilla.org/listinfo/enterprise
To unsubscribe from this list, please visit
https://mail.mozilla.org/listinfo/enterprise or send an email to
enterprise-requ...@mozilla.org with a subject of "unsubscribe"
