Our build specialist has solidly identified this as a bug in the InstallShield build engine and has added Jenkins code to the Jenkins build project to work around folder output issues. Because we have to have both an exe and an msi file for the same install, Jenkins runs the build twice to get both objects. However, the objects apparently don't go to the specified output folders and sometimes end up swapped; i.e. the exe in the msi output folder and vs versa. Another oddity I can't explain is the add/remove icon does not show up at all on the Jenkins build but is just fine on a local build using the GUI. The icon file is specified with a relative path to the project file and it exists in the correct place on both machines, but only the GUI gets it right. We are running with the build engine recently updated for 2015 SP2.