I have an Installshild Script driven application (Real Legal Binder 7.5) that requires Installshield Script Engine ver 7 prior to the application installation. I create the transform, and add the redistributable for ISSCRIPT 7 to the mst. I also remove the setup.exe dependancy. The issue here of course occurs within the DCOM for ISSCRIPT 7 using the Interactive User to launch the application. I know this issue has been covered so much it should be buried already (and I know the resolution is to remove the RunAs string value for this version of ISSCRIPT), my issue is trying to apply it. I though maybe I could import the registry key removing this value into the .msm, but everytime I deploy the application through SMS (using the system account), the application installation fails (because ISSCRIPT 7 sets the DCOM impersonation back to Interactive User).

So how should this change be applied? Would it work by removing this value through a CA? Any help here would greatly appreciated! Thanks in advance.
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


Since the installer is already running when the MSI is being 'executed' it stands to reason that the process is already running with the wrong execution level/credentials/privileges/whatever-DCOM-calls-it. You must make the change to the IS driver BEFORE running the installation. The simplest route would be to create a pre-requisite MSI/EXE to change the driver's execution level and run that before the MSI.
Answered 12/10/2007 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity