I have created a scripted instal with autoit and compiled it to an exe, I then added this to an msi package as a custom action. the msi works beatifuly when run manualy but when it is deployed through Group policy the custom action is never run so the scripted install never takes place. as far as eventlogs and add/remove programs is concerned the msi installed. but since the custom action never occured the realy is no program installed. Does any one have an ideas??
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.


Are you using an advertised installation?
Answered 03/28/2006 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
In which sequence is the custom action placed?
Answered 03/29/2006 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment
Sounds like it's probably down to sequencing or condition.
e.g if it's in th ui sequence then it will never run.

we need some more info really
Answered 03/29/2006 by: timmsie
Fourth Degree Brown Belt

Please log in to comment
How to use the custom action Install MSI From installation and install MSi from destination
please test it and let me know.
Answered 06/14/2010 by: reddyk
Yellow Belt

Please log in to comment
You almost certainly have the CA set to run in user context and I'd wager that your users have insufficient privileges.

- Change the CA's execution options so that it runs in system context.
- Better, abandon the lash-up you have now and capture the install to an MSI.
Answered 06/14/2010 by: VBScab
Red Belt

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