5 Replies Latest reply on Mar 5, 2013 12:33 PM by adamg23

    Mozilla ESR products not getting updated or updating to non-ESR.


      There are two problems that I am experiencing across my patched systems with Firefox ESR and Thunderbird ESR products.


      Weeks back I pushed out FF13-1702 (FireFox ESR 17.0.2) and TB12-1700 (Thunderbird ESR 17.0), but neither have been getting updated since.


      Thunderbird ESR: First, there have been NO new patches added to vCenter Protect (looking in Patch View - see attached) for Thunderbird ESR line since 17.0 ESR even though the Mozilla site shows that they are up 17.0.3 ESR. In that time the non-ESR line patches have been added and are now up to 17.0.3 in Protect. I am assuming that VMWare employees who create the patch definitions are failing to make the distinction between the ESR and the non-ESR products, and thus are accidentally ignoring the ESR patches. Please let me know if this is purposeful.


      Second, if I manually update an install to Thunderbird ESR 17.0.2, vCenter Protect will then detect and update Thunderbird to the 17.0.3 non-ESR line. This is a real problematic situation that keeps cropping up over and over with ESR products and the vCenter Protect, and it's getting rather tiresome. I am trying really hard to maintain ESR installs, but vCenter Protects keeps pulling my installs over to the main line installs rather randomly. Is there ANY way you guys can shore this up, or just say you will not support ESR.


      Firefox ESR: Ever since distributing Firefox ESR 17.0.2 weeks ago with a software ditribution scan and deploy, patches aren't being detected as missing (I am using the default Security Patch Scan). So my Firefox ESR applications aren't getting updated even though newer patches exist in Patch View. Interestingly, the Firefox ESR 17.0.2 application is NOT listed in either the Informational, or Patch Installed sections for any computers that have FF17.0.2 installed (even when it was manually installed). In fact, rerunning my software distribution scan still shows the product as missing, even though it is installed. I have a feeling that the patch scan detection definitions aren't properly working for these recent versions of the FF ESR line.



      Please, please, please shore up your detection and patching for Mozilla ESR products, or officially dump support for them. This is getting quite frustrating.

        • 1. Re: Mozilla ESR products not getting updated or updating to non-ESR.

          It is possible there are a couple of things that maybe causing the problems here. The template you are using is not filtering the detection correctly and maybe skipping appropriate patches.  Please run a WUscan with the base template and identify if the patch was not identified correctly. If you feel the patch should have been found, look at the detection criteria for the replacement patch in the patch view, and compare to what is currently installed on the system.


          To do so: Under Patch View > Type in the Bulletin ID or QNumber for the patch.  In the details portion of the screen look at the detection criteria for either the files or registry keys it is looking for.


          If you have questions about this, or feel that the patch is not being detected properly, please call in a support request at 1-866-407-5279 when you are ready to work on it, and we will be glad to help. If indeed there is a detection problem, we will be more than happy to help identify it, or escalate it to our data team.


          Thank you.

          • 2. Re: Mozilla ESR products not getting updated or updating to non-ESR.

            Hi, here is some information that I have gotten directly from our data team concerning Mozilla ESR patches and why you may run into some problems with these currently.


            Mozilla ESR products not getting updated or updating to non-ESR is essentially because we are not able to differentiate the two (regkey and file detection are identical) for a specific version and not able to release that specific ESR version. Because of this, when customers install this non supported version manually it causes the updating to non-ESR version error. Even if we drop support of ESR this will continue to happen because we are not detecting the ESR versions whether intentionally or not. In the end it comes down to Mozilla releasing versions that have build files that are not unique between the two. Some releases they get it right but, then the next they break it and then get it right again. We can't control this so for now I can supply a list of bad versions and as a workaround we suggest customers to not upgrade to these version if they plan to patch Mozilla ESR with protect.


            Known unsupported ESR versions are:
            Firefox 10.0.1 ESR
            Firefox 17.0 ESR
            Thunderbird 10.0.1 ESR
            Thunderbird 10.0.2 ESR
            Thunderbird 17.0.2 ESR
            Thunderbird 17.0.3 ESR


            So in summary if you avoid the listed versions you will not see the update error.

            FYI Firefox 17.0.3 ESR is latest ESR version for firefox and is detectable.
            Thunderbird 17.0.3 ESR is latest ESR version for Thunderbird and is not detectable.


            I hope this information is helpful.

            1 of 1 people found this helpful
            • 3. Re: Mozilla ESR products not getting updated or updating to non-ESR.



              Welcome to the communities.


              In one line I will suggest go one by one ,

              If one not getting update proceed to next .



              "With normal actions you get normal   results."
              • 4. Re: Mozilla ESR products not getting updated or updating to non-ESR.

                Thanks Adam. That is a great list. I understand what's going on now. Since detection is based on file version, it seems that FF 17.0.3 ESR will update to the next ESR because 17.0.3 ESR = 18.x in the non-ESR version. But, TB 17.0.3 ESR = 17.0.3 in the non-ESR version. My guess is that once the non-ESR TB moves to 18.x+, then TB ESR will update properly. So in a sense, the ESR versions will start detecting and patching properly at the version where the non-ESR equivenlent version makes the first major version jump. So it may be necessary to disable updating the products until the second major version of the non-ESR line is out for each product, then enable updates and push out the most recent ESR version. Let me know if this sounds reasonable.



                I wonder if there is anything additionally that can be used for ESR detection? There is a text file which will differentiate the version, if you are able to either match text inside the file, or differentiate the size difference between the two (which is small).


                For TB, the text file is in %Program Files%Mozilla Thunderbirddefaultsprefchannel-prefs.js

                The text for ESR is:

                pref("app.update.channel", "esr");

                File size is 343 bytes


                The text for non-ESR is:

                pref("app.update.channel", "release");

                File size is 328 bytes


                These files are the same for FF, but in the FF program folder. From the looks of it, these files haven't changed in a long time. I'd have to get a look at the files in thier svn repo to really see.

                • 5. Re: Mozilla ESR products not getting updated or updating to non-ESR.

                  This is a good suggestion, however, I confirmed with our data team that our scan is currently unable to open a file to run tests based on information inside the file.


                  We determine if a patch is missing based on either a file version number on certain file names or based on registry keys (existence or values).


                  Since ESR does not offer any of these methods the best suggestion at this point is to follow the guidelines above when using Protect as your patching method, or you can submit a bug to Mozilla requesting they provide a reg key or particular file name/version for ESR vs. Release versions.


                  Bugs to Mozilla can be submitted at https://bugzilla.mozilla.org/. I would suggest reviewing their guidelines before submitting anything.