Thanks a lot MichaelU, It is working fine,I made Install option to yes in LicenseAgreement dialog , even made changes to enable and disable the install button on selection of the radio buttons. ... View more

Any updates on this issue please ... View more

MichaelU wrote: I would expect that, for detection, the Product Version would match the version that's in your Suite (this is easiest to do with the dedicate InstallScript package type, as you can put a * here, or better yet let the empty default detect condition work its magic), with a comparison of Greater Than or Equal To. This will only detect the package if a matching or higher version is installed, allowing it to install over lower versions, and to remove equal or higher versions if uninstalled. Eligibility is different, and while it's useful to reference them to see example condition elements, they may not help you craft a detect condition. @DLee65, your eligibility condition seems a little suspect to me. By having a root condition of Any, you're saying your package is eligible if any of the following are true: a lower version is present, a higher version is not present, the computer is XP SP3, or whatever's in ETC. I would expect you typically want both your Platform and your MSI Package conditions to be true; that would be represented by something more like this: All: Any: MSI Package: ProductCode: *; PackageCode: *; ProductVersion: ; Compare:LessThan None: MSI Package: ProductCode: *; PackageCode: *; ProductVersion: *; Compare:GreaterThan (Prevents overwriting newer installs) Any: Platform: OSVersion: 5.1; ServicePack: 3; ETC (other Platform conditions) Hi MichaelU, One more point is we are using exe packages , not Installscript packages. And * value is not working in exe packages. I tried to fill product code package code in different conditions but nothing worked out for upgradation ... View more

MichaelU wrote: If your .exe packages are actually InstallScript setups, we tend to suggest using the "InstallScript package" option rather than the "Executable package." Since you're using an "InstallScript Package" condition to identify whether the package is present on the machine, be sure to fill in the Product Version and Comparison settings so that when version 1.2.3 is present, your suite doesn't think version 2.4.6 already installed just because a package with the same Product Code is present on the machine. Hi MichaelU I fill the Product version to 1.00.0000 and Comparision setting to different values eg:Equal to, Greater than, less than . And tried but its not upgrading, actually I changed the exe package version to 3.00.0000 ... View more

MichaelU wrote: What do your detection conditions for your EXE packages look like - in particular, do they take into account any version information? From your description, I'm guessing they do not, and thus the Suite is detecting the EXE packages as already installed, and doing nothing. You should be able to confirm this by examining a log generated by /debuglog, or by modifying your conditions. Hi MichaelU, In detection conditions , we are setting it as Any and adding Installscript packages condition in that by filling the product code of the respective exe packages ... View more

Hi Hysteresis, They are getting upgrade successfully if we install them stand-alone (i.e. not from the suite) ... View more

Thank you Hysteresis, I created an "Registry comparision" Exit condition. It is working grt ... View more

Thanks a lot Michael, it is working grt ... View more