I recently created a basic rm script to handle removing some pesky plist files across a group of machines. I had created a similar script policy last week and it ran fine, but now when I run it I get
Script exit code: 126 Script result: sh: /private/tmp/remove 1-5 banner.sh: bin/sh: bad interpreter: No such file or directory
The kicker, is if I run the same script file via terminal on a test machine, it works and behaves perfectly. The script was not created in any DOS/Windows environments, so the standard ^M issue isn't in play.