Have you tried adding a line to the script to output to a network/shared location? Or run the job as script job and run it centrally.
can't you just add some logic to copy the file to a central server in the same script.
I hope my below understanding is correct.
file deploy is used to just copy the script
how you are executing the script ? Are using pre/post command option in file deploy job ?
The issues is this will be ran on a lot of systems and due to firewalls paths reverse may not be open. The script is deployed then executed is a post command yes.
With some help from the BMC team the solution we landed at was building a host list to the central NSH servers and executing a loop to pull the files back.