I have an application which installs properly in the UI mode. It basically installs ISScript 9 first and then the main application. But when I install the application using At command, it does not install as ISScript does not get install. The command line that I used to install the application was "at 7:30 <Path of the application> /install /s ". When i checked the Event Viewer, it pointed that the application failed as some custom action does not work. The custom action is ISStartup. Is there any condition that has to be present with this custom action to make it work? Kindly let me know where I am going wrong.
0 Comments   [ + ] Show Comments

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.

Answers

0
Almost certainly the Custom Action is set to run only in the User Interface sequence. You'll need to apply a transform to the MSI in which a copy of the CA is made in the Execute Immediate sequence. Also be aware that the Scheduler runs in the context of the local System account. If there are any user-level components being installed, you'll want to trigger those using either self-healing (if there are advertised entry-points e.g. shortcut(s) or Active Setup.
Answered 10/31/2011 by: VBScab
Red Belt

Please log in to comment
0
yay .. changing the CA to Execute Immediate worked..thanks VBScab... [:)]
Answered 10/31/2011 by: richa_shetty86
Senior Yellow Belt

Please log in to comment
0
If you changed it rather than copying it, the package will no longer work in UI mode. Always copy. Depending on the CA, you may also want to set its operation to run only once, i.e. if it was run in the UI sequence it should not run in the EI sequence. The Windows Installer help file MSI.CHM will contain details of the attributes you need to set.
Answered 10/31/2011 by: VBScab
Red Belt

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