EDIT: This seems to be an issue effecting multiple JamfCloud hosted
environments. I have Logged a support case with Jamf, as have other
community members.I will keep this thread up to date with any
information from Jamf Support. On two JAMFCloud Jamf...
You can actually just drag text files into the scripts area via
JamfAdmin, and then rename them to .shThis is the workaround we have
been using so far, following the 403 issues on the web uithe process is