The moment the InstallScript setup.exe is completed (success/failure) in silent mode... there's a setup.log file that gets created in the same directory as setup.exe (if i'm not wrong here) based on that you can proceed. Also, you can check for the process based on your installer's name .... ... View more

I guess there's no built-in way to do this. May be a powershell script as a pre-requiste may help, or a powershell custom action. ... View more

Entries written to Registry key is by default logged for uninstallation by InstallScript. you may want to call Disable(LOGGING) just before the registry key write function and then enable the same. ... View more

You can use SETUPEXEDIR for MSI based (Basic MSI, InstallScript-MSI) projects to get the setup.exe location. ... View more

You can run a Prerequisite which creates a folder for you. It can be a VBScript/batch file which will be executed in a .prq. ... View more

Yeah, you can set the pre-req's to be embedded in setup.exe... Right Click on the Pre-requisite >> Properties >> select "Extract from Setup.exe" ... View more

Excerpts from the log here: [HTML]InstallShield 12:36:35: GetAdminSection for section 'system.webServer/handlers' and path 'MACHINE/WEBROOT/APPHOST/WebApplications/SISApps_GEO' and commitpath 'MACHINE/WEBROOT/APPHOST/WebApplications/SISApps_GEO'. InstallShield 12:36:35: PutPropertyValue: sProperty accessPolicy sValue Script, Read bIsPath 0 InstallShield 12:36:35: PutPropertyCommon: sProperty accessPolicy sValue Script, Read bIsPath 0 InstallShield 12:36:35: Setting property 'accessPolicy' to value 'Script, Read' for element 'system.webServer/handlers'. Old value: '513'. m_sSectionName : 'system.webServer/handlers'. InstallShield 12:36:35: put_value succeeded. get_StringValue now returns '0' with string value 'Read, Script'. InstallShield 12:36:35: CommitChanges for path 'MACHINE/WEBROOT/APPHOST/WebApplications/SISApps_GEO' and physical path 'D:\WebApplications\SISApps_GEO\'. InstallShield 12:36:35: CommitChanges failed with the following HRESULT: '-2147024891'. [/HTML] HRESULT: '-2147024891 This translates to "Access is denied" I guess there should be a config file probably read-only ... or may be not enough permissions to write/update. ... View more

There's lot of things you can look for: Did the pre-requiste install or it's still in process ... check for it's process and install log if it has any Can the same prq be installed outside of InstallShield with same set of command line parameters (if any) ... View more

May be you just missed the "Domain". I just tried with the below setting and that worked for me. ... View more

I can think of InstallShield's build reports to your 2nd part of the question.. where people without InstallShield license can still see what went into the installer. This has helped us in case of Dynamic File linking where you can answer people's question to what went into installer (viz. InstallScript project- as there's no MSI so can't use Orca) from a given dynamically linked folder. look for the below folders (if you haven't already) in the InstaallShield project Release folder. "Report Files" in InstallScript projects "Reports" in MSI based projects Btn: I would be interested in the WiX part which you are taking about... could you share some link? we have been using WiX for an year and the report part which you mentions seems interesting. ... View more

I guess it could be due to the conditions on the pre-requistes which is not satisfied on the particular system you been trying. In any ways, if you want to really verify if "ISSetupPrerequisites" folder is being created then just navigate to: Media >> Releases >> Setup.exe tab >>and then set "InstallShield Prerequisites Location" to "Copy From Source Media". ... View more

if you have set "Extract from Setup.exe" then the pre-requistes will be bundled into the setup.exe wrapper ... View more

I see that you want to get the return code of dism.exe when launched from InstallScript. I would recommend using "LaunchApplication" instead which has can help you find out the return code of the launched app (dism.exe in this case) InstallShield Help on LaunchApplication Note: If the application cannot be launched, the LAAW_PARAMETERS system variable’s nLaunchResult member contains the result of calling the Windows API function GetLastError after the CreateProcess or ShellExecuteEx call. If the function is successful and the LAAW_OPTION_WAIT option was specified, the LAAW_PARAMETERS system variable’s nLaunchResult member contains the return code of the launched application. ... View more

RemoveExistingProducts sets UPGRADINGPRODUCTCODE in immediate execution and if you feel that's late then you can also look at these custom properties which InstallShield sets for you (action ISSetAllUsers) IS_MAJOR_UPGRADE and IS_MINOR_UPGRADE and for this to happen you should have set the upgrade item in your project. ... View more

Uninstalling/removing the files/folders laid down by MSI is a default behavior and you are seeing that in a Major upgrade is obvious. In your case, if you still want to retain specific folders/components you may look at the component's setting "Permanent". Use this with caution as these files/folders will not be uninstalled at all. Usually this setting is used in case of font files. Hope this helps. ... View more