6 Replies Latest reply on May 7, 2013 10:56 AM by IGFCSS.DSI

    New Package Firefox 20

    mattbaer

      I am trying to follow the PatchManagerAdministratorGuide.pdf creating the applicability and installed rules. I publish the update. It says Computers Installed 30, Computers needing 0. Firefox is only used on 5 of the 30 computers. Shouldn't all but the 5 that has Firefox installed show up as Computers not applicable? The 3 of the 5 have an older version of Firefox version 17. Those should show up as needing? and the 2 with Firefox 20 be listed as installed? The version for the Applicability rule is set to less than 20.0.0.0 and the Installed rule is set to equal to 20.0.0.0.

      What am I doing wrong?

        • Re: New Package Firefox 20
          jbaits

          There really isn't enough information here to figure out where you're going wrong. If you answer a few questions we might be able to figure it out.

           

          Are you trying to make an upgrade package which only upgrades existing installs?

          Are you using a file version rule for applicability and installed rules? File version with registry?

          Do you have any prerequisite rules set?

          Is there a reason you aren't using the pre-built Firefox packages from the SolarWinds catalog, or at least duplicating them to use as a base for customizations?

           

          Also the version numbers you're using are wrong. The latest version of Firefox is 20.0.1.4847 and the version number for the first release of 20 was 20.0.0.4833.

           

          If you could post the XML for your current rules it would also be helpful.

            • Re: New Package Firefox 20
              mattbaer

              The Patch Management server is running on a closed network. No internet access. Unless there is a way to download the cab file from SolarWinds.

              We would want it to update any system that is currently running a older version of Firefox. If a computer does not have Firefox installed we do not want it to be installed. No prerequisite rules are set.The Applicability and Installed rules are set up following the PatchManagerAdministratorGuide.pdf the only differance is the Version field by using different version numbers.


              Applicability Ruleset

              On the Rule Editor window, select Create Basic Rule.

              2. In the Rule Type field, select File Version with Registry Value.

              3. In the Registry Key field, enter HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\firefox.exe.

              4. In the Registry Value field, enter Path, and then select Use 32-bit registry.

              5. In the Sub-path field, enter firefox.exe.

              6. In the Comparison field, select Less Than.

              7. In the Version field, enter 20.0.1.4847.

               

              Installed Ruleset

              1. On the Rule Editor window, select Create Basic Rule.

              2. In the Rule Type field, select File Version with Registry Value.

              3. In the Registry Key field, enter HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\firefox.exe.

              4. In the Registry Value field, enter Path, and then select Use 32-bit registry.

              5. In the Sub-path field, enter firefox.exe.

              6. In the Comparison field, select Equal To.

              7. In the Version field, enter 20.0.1.4847.

                • Re: New Package Firefox 20
                  jbaits

                  If Firefox is not installed your applicability rule will evaluate to true since not existing is less than the specified version. You will need to add a rule checking for an existing install to prevent the package from applying to machines without Firefox installed. I typically will use a "Reg key exists" rule looking at the applications registry key (ex. HKLM\Software\Mozilla Firefox use 32-bit registry). Other than that, what you posted looks fine. I would delete the existing package from WSUS, make the required changes to the package, and republish the package. That should clear the existing data and give you a fresh start.