I have tried that, and because of your message I deleted the existing software package and config and started over.
When I create the software package and enter the entire path with the script in the "installation command" field I immediately get an error. "Enter a valid installer name."
I saved the software package any way, then created the Computer Windows installation config.
Still does not run correctly, batch file triggers but exe run from batch file fails or the config fails with the "extended attributes are inconsistent", "network path not available" all depending on different options I select.
It also seems to be forcing me to select "copy folder to client machines" not ideal as I would like to have everything run from the network and not all the files are in that directory.
The closest I have come is the run the batch file as a "Computer Custom-Script", that seems to succeed but not perfectly all the time. This requires the computer to be rebooted also before being triggered, a possible solution but not ideal.
Speaking of time, maybe I will try configuring a scheduled task to run the batch file.
Steven R