9 Replies Latest reply on Aug 9, 2012 6:35 PM by kevinr@firstpac.com

    Install rules not working

    kevinr@firstpac.com

      Install does not care what it says....

       

      We add a key to check for on some systems that has been working.

       

      But now does no.

       

      As a test I change it to say on install in ia86 system it still installs onx 32 and x64

       

      -<sdp:InstalledRule SchemaVersion="1.0">

       

      -<lar:Or>

       

      -<lar:And>

       

      <bar:Processor Architecture="6"/>

       

      <bar:RegExpandSz Key="HKEY_LOCAL_MACHINE"Subkey="Software\FPC\Flash"Value="Flash"RegType32="true"Comparison="EqualTo"Data="Yes"/>

       

      <bar:RegSzToVersion Key="HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Macromedia\FlashPlayerActiveX"Value="Version"RegType32="true"Comparison="EqualTo"Data="11.3.300.270"/>

       

      <bar:FileExists Path="System32\Macromed\Flash\Flash32_11_3_300_270.ocx"Csidl="36"/>

       

      </lar:And>

       

      -<lar:And>

       

      <bar:Processor Architecture="6"/>

       

      <bar:RegExpandSz Key="HKEY_LOCAL_MACHINE"Subkey="Software\FPC\Flash"Value="Flash"RegType32="false"Comparison="EqualTo"Data="Yes"/>

       

      <bar:RegSzToVersion Key="HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Wow6432Node\Macromedia\FlashPlayerActiveX"Value="Version"RegType32="false"Comparison="EqualTo"Data="11.3.300.270"/>

       

      <bar:FileExists Path="SysWOW64\Macromed\Flash\Flash32_11_3_300_270.ocx"Csidl="36"/>

       

      <bar:RegSzToVersion Key="HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Macromedia\FlashPlayerActiveX"Value="Version"RegType32="false"Comparison="EqualTo"Data="11.3.300.270"/>

       

      <bar:FileExists Path="System32\Macromed\Flash\flash64_11_3_300_270.ocx"Csidl="36"/>

       

      </lar:And>

       

      </lar:Or>

       

      </sdp:InstalledRule>

       

      Please help

        • Re: Install rules not working
          IGFCSS.DSI

          Hi kevinr,

           

          I'm not very sure to what you want to do. Can you explain better you goal?

           

          The XML from your post is for the InstalledRule and, if I got it right, you want to test the applicability of the Flash update to IA64, right? Or do you want to test if it was installed?

            • Re: Install rules not working
              kevinr@firstpac.com

              The goal is to stop it installing on Developers system that why I added

              Key="HKEY_LOCAL_MACHINE"Subkey="Software\FPC\Flash"Value="Flash"RegType32="true"Comparison="EqualTo"Data="Yes"/>

               

              This has always until now.

               

              So as a  test I change it to IA64 and still install.

               

              Rules are broken….

               

              Please help

                • Re: Install rules not working
                  Lawrence Garvin

                  I'm not aware that there is an Itanium edition of Flash. Preventing Flash from not installing on Itanium systems is trivial. Please review the provided Flash packages in the synchronized content for great examples of how do define rules for Flash updates. Either add two Processor Architecture rules in in an 'Any' block testing for x86 or x64, or add a single NOT rule that excludes IA64 systems. These go in the Prerequisite Rules section. Once you've isolated the package to the correct processor architectures, generally you won't need to do that level of testing anymore. If you actually have a version of Flash for IA64, then define a Processor Architecture rule for 'equals IA64'.

                   

                  If, beyond that set of basic tests, you further want to restrict the updating of the Flash Player on systems that have a Flash Developer's edition installed, then simply test in an Applicability Rule for a NOT Registry Key Exists or NOT File Exists rule that would uniquely identfy the machine as a development system --or where the absence of that key, value, or file would uniquely identify the machine as NOT being a development system.

                   

                  As for the actual rules posted -- rather than post the XML, generally it's easier to simply post the English-language statement of the rule. I don't have the schema memorized, so I'm not able to interpret your actual rules without a fair amount of research effort. What I can tell you, though, is that if you properly define your Processor Architecture rules in the Prerequisite Rules collection, then you won't need to do processor architecture tests in the Installed Rule ruleset because that ruleset would only ever be evaluated on IA64 systems anyway -- once the Prereq Rules have excluded the package from further consideration because the package and architecture don't match.


                    • Re: Install rules not working
                      kevinr@firstpac.com

                      The rules do not work.

                      NOT Registry Key Exists or NOT File Exists or ANY other do not work.

                       

                      It does not care what I put there.

                       

                      I'm not aware that there is an Itanium edition of Flash...  That is only a test to show your support team it does not work. ( that did not help just said not supported pst here.)

                        • Re: Install rules not working
                          Lawrence Garvin

                          Greetings Kevin

                           

                          I know you're not really asking for anything complicated from this customization, so it should certainly be solution that can be achieved. Would you do me a favor please -- understanding that generally SolarWinds does not provide support for custom packaging -- but this scenario has my interest, and is likely a scenario that will be of interest to others...

                           

                          Could you select your custom package, export it to a catalog file (without binaries), and email me the resulting CAB file. I'd like to take a look at your entire package and see if I can offer some specific guidance that will get this working for you the way you want it to.

                      • Re: Install rules not working
                        Lawrence Garvin

                        Greetings Kevin

                        Thank you for sending the package definition. It helped tremendously, and I believe I know exactly what the solution for you is.

                         

                        As I understand, just to repeat what we've said but to make sure I fully understand -- you want to prevent the installation of the Flash package on developer machines.

                         

                        This objective would not be achieved by defining rules in the Installed Rules ruleset. The Installed Rules ruleset identifies how the Windows Update Agent knows that the package is already installed.

                        It is the Applicability Rules ruleset that is used to determine IF an update should be installed.

                        So, in the case where you do not want to install the update on systems with the FPC registry key, use the same rule you have already defined in the Installed Rules ruleset, except put it in the Applicability Rules ruleset, and change it to a *NOT* rule. This will prevent the update from being evaluated as "applicable" on any system is identified as a development system.

                    • Re: Install rules not working
                      kevinr@firstpac.com

                      What email address do you want it sent to?