I have two custom actions in my .exe profile.

One will launch an MSI to install some 3rd party software.
The other will execute a vbs which in turns kicks off a .bat file to set some permissions.

Both work - just not in the right order.

Right now, my vbs (kicking off the .bat file) runs before my 3rd party msi installer. I need them reversed - so my vbs starts after the 3rd party msi is ran and installed.

My vbs, which starts a bat file sets permissions - on folders that are created when the 3rd party msi is installed. You can see my problem. I can't set permissions on folders that don't exist yet.

How would I change the order or at least make my vbs start last of all things?

Thanks in advance. (if you need screen shots of my project, please do let me know and I can attach them here).
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.


to set the permissions with your vbs sequence your ca after installfinalize - (immediate execute)

sequence your ca to install the 3rd party software before intallfinalize - (immediate execute)

remenber you might need to run it as an Asynchronous Custom Action
Answered 04/06/2010 by: cygan
Fifth Degree Brown Belt

Please log in to comment
Hi steve02aa,

As per the information you are using an exe to run the 3rd party application and vbs file to run next. Is this an wise script exe , if so you can use "wait" option.
or if it is not wise script exe then do let me know which exe you are using.

Answered 04/07/2010 by: joseph
Orange Belt

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