Software Deployment

There are 2 ways to go about this. 1 is to open the msi in Orca or Wise MSI editor and find out what that property is called (look in the properties table). You can then set it in the MSI via command line options like this: msiexec /i A:\Example.msi PROPERTY=VALUE (where PROPERTY is the name of the property and VALUE is whatever the checked value is.) The second option along the same lines is to create a transform package and use that when running your original MSI. I know Orca can do this as well but haven't used it for this purpose. Wise is a little better suited for creating transforms. They are pretty easy to make.

Open the MSI in Orca and look for a table under Property called ISCHECKFORPRODUCTUPDATES. Try changing the Value from 1 to 0. This may or may not work but it's worth a shot.

Sam,

It would help if you could say which application you're referring too.
Have you looked in the Package KB for any reference of the application?

I am working on Romeo and Dye's section 16 and its not in the package KB. I've also tried ISCHECKFORPRODUCTUPDATES=0 in the property table its still asking me the same option after i launch the app.

I am working on Romeo and Dye's section 16 and its not in the package KB. I've also tried ISCHECKFORPRODUCTUPDATES=0 in the property table its still asking me the same option after i launch the app.
That's because ISCHECKFORPRODUCTUPDATES is used by InstallShield-built (and dependent) MSIs. If your product doesn't use InstallShield, this is irrelevant.

You need to walk through the Property table looking for a property with a likely-looking name. If there's nothing there, turn your attention to the Custom Action table. Many vendors set options by calling functions in DLLs via custom actions.

If you are unable to locate either, it might be worth monitoring the app with ProcMon (or your favourite file/registry monitor) and/or force it to auto-update. You'll then see immediately what file/registry activity is involved.

The "AutoUpdate check option" may be a application configuration and not an MSI related thing.

My best guess would be that it's stored in the registry or a file.
Using Ian's favourite tool (ProcMon) ;) should work this out.

What I do for these types of issues is this:

1./ Install app on your base system.

2./ run the application with 'procmon' running so it captures the registry changes. You can download this free utility frmo Sysinternals

3./ When youa re prompted click 'No' and see if it captures anything.

More cases then not there is a registry key entry under the HKLM/Software/<AppNAME> that refers to this feature and can be turned off. If you find such a key you can turn it off and export that key and add it to your MSI's registry ADD or create a custom action to add it. If you don't want to repackage to do this you can create a batch file that calls the MSI and then applies the registry change using REG or REGEDIT.

Good luck.