This sounds like a situation where I'd put the third party software in setup.exe as a setup prerequisite and have the EXE manifested to require elevation. This should give the third party installer full permission to do whatever it needs to do. I've never needed to care about UAC settings in an installer. I just assume the strictest case and design around it. ... View more

I don't think you are allowed to change the destination path of any component when performing a minor upgrade. You would be able to install the files to the new destination, but the ones that were previously installed would be left behind, which would mean that the RemoveFile table must be used. If I were you, I would rather go for a major upgrade. Check here: http://helpnet.installshield.com/installshield18helplib/MajorMinorSmall.htm ... View more

How could I change the image of the first dialog "Prepare install" before welcome to the Patch dialog? I am using IS 2013 Professional Edition version. ... View more

With a Basic MSI project, one could set up a launch condition with the following condition to detect Windows Server 2008 R2 SP1. VersionNT = 601 AND MsiNTProductType = 3 AND ServicePackLevel = 1 For more info, please refer to Operating System Property Values. ... View more

Create a CA and have a condition if running silent to run it. You can basically go through your features and re-add them to ADDLOCAL and REMOVE checking their FeatureState to see if it is already installed: [HTML] myList = ListCreate(STRINGLIST); ListAddString(listID,"Feature1", AFTER); etc... nResult = ListGetFirstString(myList,featureName); while (nResult != END_OF_LIST) MsiGetFeatureState (hMSI, featureName, nvInstallState, nvActionState); if nvInstallState = INSTALLSTATE_LOCAL then // add to Addlocal flag else if secretProperty = OK then Addlocalflag=true; else Addlocalflag=false; endif; endif; if AddLocal then if strAddlocal = "" then strAddlocal = featureName; else strAddlocal = strAddlocal + "," + featureName; endif; else if strRemoveFlag = "" then strRemove = featureName; else strRemove = strRemove + "," + featureName; endif; endif; nResult = ListGetFirstString(myList,featureName); endwhile; MsiSetProperty(hMSI, "ADDLOCAL", strAddlocal ); MsiSetProperty(hMSI, "REMOVE", strRemove ); endif;[/HTML] Or if you know what features are to be installed - just add them directly to the ADDLOCAL and REMOVE variables. ... View more

Hi all, As described above, I have an installation which includes one .net component that is installed to the GAC and set as "scan dependencies and properties" in feature A. In case I install the Release version with feature A not selected (this feature includes this problematic component), And then install a service pack for this product, Trying to modify the product and add feature A after SP installed causes this error: Note: 1: 2262 2: Binary 3: -2147287038 Error 1310.Error writing to file I would appreciate if anyone can share suggestions for resolution of this issue. Thanks, ... View more

Hi Sharon, You just need to IS2010 with SP1 on any Windows machine. Then you should be able to create Installers, which can run on Windows 7. Thanks, Alpesh ... View more

Just an idea: Have you try LAAW_OPTION_WAIT_INCL_CHILD instead of LAAW_OPTION_WAIT? ... View more

Hi, all 3 installers are msi. As the 2 prerequsiites are 3rd party, I knew that on some machines users will get the note: would you like to run.... due to security issues. As this is a 3rd party, the creator of it is unidentified and our customers might fear from installing it. I tried to prevent that by signing the main installer with our signature. The note shown to users that run main installer from network is shown after they have selected the feature that has the prerequisites under, and it is not shown in case we run the installation from DVD. it is saying: would you like to run setup.exe of the MAIN installer. Do you have an idea how can I solve this issue? ... View more

Hi, Did you find solution this problem? I am seeing the same issue with IS 2013 Premier on Windows 7 64 bit. See my post for details of the problem I am facing: http://community.flexerasoftware.com/showthread.php?206841-SQLRTGetConnections-issue-with-IS-2013-Premier-on-Windows-7-64-bit Thanks Akash. ... View more

😮 Thanks for your response, I was asking about one replacement for a few seperate edit fields, In a dialog of a basic msi installer This option seems interesting. Thanks again, Sharon. ... View more

That's right, and since IA 2008 VP1 or 2009 (I don't remember), action group can be used in "Install" part while it was only in pre & post previously. good point, thanks Jerome 😉 ... View more

Maybe you can use IA registry files stored in "Program Files\Zero G Registry\.com...xml" (windows) or "/var/.com.....xml", then parse those files looking for your component unique ID (component id="..") and find the corresponding location ?. ... View more

My bad, I've misunderstood your issue. AFAIK, the buildlog.xml is automatically generated in the same folder as your project is built (but for instance I'm using the build tool within ANT and have the output in the ANT output, so I immediately see when the IA build project has failed why it has failed; I don't think I've ever used the buildlog.xml file... ... View more

I think this is what you're looking for: $INSTALLER_LAUNCH_DIR$ This is a full path to the installer's self-extractor. This variable is read-only. ... View more