2. Set a name for the CA.
3. Type: Launch an executable
Location: Stored in Directory Table
4 Source: Select SystemFolder
you'll modify this in just a bit...
5. Check "Wait..."
6. In-Script Execution: try Deferred, but you may need to make that "Deferred In System Context" if you get permissions-related errors.
7. Install UI Interface (<Absent..>)
Install Execute Sequence: sometime after "InstallFiles"
8. Okay, now take the directory table entry pointing to the install location of your batch file, let's say it's [MY_BIN], and let's say your batch file is called "MyBatch.bat". In the "Filename and Commandline" property of your new custom action (which currently says "[Systemfolder]cmd.exe") append the following: /c "[MY_BIN]MyBatch.bat"
That's just one solution. It's probably not recommended, but then again, neither is the use of batch files.
Alternatively, you could script a CA which essentially does the same thing using LaunchAppAndWait().