After 9.7 Upgrade no scripts will run using HTTP (path duplicates script name at end)

Yes, I suppose if Casper Imaging continues to work with the upgraded JSS, then I guess it could be overlooked. It would, I imagine, eventually get you though, as at some point the version drift is sure to create some headaches, not to mention that features or critical bug fixes may get added to the new version that won't be available to the admin still using the older version. A prime example is the fix for Yosemite's Core Storage volume format out of the box with new systems. Casper Imaging 8.5 isn't going to know how to handle that and the admin will have imaging problems. (I guess it would then get updated though)

If its an oversight, that's one thing, but I would hope there isn't anyone out there actively trying to stay on an older version of those applications. That doesn't sound like a good idea. :)

@amanda.wulff Migrating scripts to the DB keeps the originals on the share, but makes a copy in the DB & all new scripts are then only in the DB.. Right?

Also, does that mean a client will run the script from the JSS & not a local DP UNLESS that DP is a JDS?

@aamjohns - Arron - I have been experiencing the same problems as described by Mark Snowdon in his second post above, including the duplication of the script name in the log file.

@Amanda Wulff - With respect to the non-flat packages, I may have misunderstood what difficulties migrating may or may not cause me.

@CasperSally - some of my installer packages include pre and/or post install scripts... Composer indicates that these cannot be compiled as flat packages. Since my background is as a kindergarten teacher I will admit to ignorance for the exact definition of a flat or non-flat package. By far the majority of my packages are in fact dmgs rather than pkgs so not migrating for that reason may in fact be bogus.

FWIW.. seems like this is an issue on 9.71 too.

@amanda.wulff Migrating scripts to the DB keeps the originals on the share, but makes a copy in the DB & all new scripts are then only in the DB.. Right?

Also, does that mean a client will run the script from the JSS & not a local DP UNLESS that DP is a JDS?

Has this been resolved in 9.72?

Trying to get clarification from JAMF on this today, as it only says that the other defect around spaces/special characters in filenames has been fixed in 9.72

Anyone have updates on this issue? I am seeing it with a script I just tried using to set the computer name to DNS name. This script I need is a result of my computer names randomly getting changes to "localhost." I have a simple script to set the computer name to the dns name then update the name in jamf, but it keeps failing.

Executing Policy Set Computer Name to DNS Name
Creating directory structure for /Library/Application Support/JAMF/Downloads/
Downloading https://10.193.58.11/CasperShare/Scripts/setcomputername.sh...
Error running script: The script could not be found on the server..