2 Replies Latest reply: Jan 16, 2013 12:47 PM by txt xtra RSS

    MSI transform file does not seem to be preventing updates

    txt xtra Community Member

      So I have noticed that in the last few versions, the MSI transform file (MST) that i have been using does not seem to be working in terms of stopping the update nag on the users machines.

       

      My transform file has the following entries:

       

      4. under property, change the ISCHECKFORPRODUCTUPDATES to 0 and the AgreeToLicense to Yes

       

      5. Under Checkbox, also change ISCHECKFORPRODUCTUPDATES to 0

       

       

      Has there been a new key added or something? Becuase my users are still getting prompted, even with these changes.

        • 1. Re: MSI transform file does not seem to be preventing updates
          roymeo_ Employee Hosts

          Did you ever find a solution for this?

          • 2. Re: MSI transform file does not seem to be preventing updates
            txt xtra Community Member

            I think it was previous versions of flash which had been installed outside of the gpo that was causing it. The problem has dissapeared somewhat, or well I havent noticed it on the last few flash updates. I would make sure that the version of flash on the machine is the one installed via GPO. It could be that the user or an administrator had installed a non GPO/MST version of it, which was I think the case with us.

             

            I attached both my transforms for acrivex and plugin for version 11.5.502.110, but it should be similar. I have not noticed the popup in a while so i think i got rid of the problematic flash copies on the machines due to reimaging or uninstalling old flash on a case by case basis. sorry to say!

             

            Oh i cant upload files, oh well. its just 3 properties:

            SP32-16012013-124551.png

            SP32-16012013-124535.png

             

            But if anyone else has the problem and knows a solution, feel free to update! there could be another property in there somewhere, however like i said I have not seen the behaviour reoccur, especially on newly imaged machines.