Thanks for posting this. I'm not sure what the scan saw in the script that thought it needed updating. The scan looks at literal text vs actually executing something and analyzing it's output. We can take a look at it here.
Regarding rescanning - we didn't add a rescan function in. We basically wanted it to scan it once, show where there is potential changes needed, and then stop scanning. The decision was mostly made to not add the expense of scanning on a regular basis. Our thoughts were that changing the path is top of mind for this short time frame, but then won't need to happen again so didn't want to add functionality to continuously scan.
Let us know if there are some other issues we need to look into there. Thanks!
@john.miller Any ideas on why some folks would not be seeing a "Dismiss" button in the bar with the alert message? I have seen it in every case of a script or policy needing to be updated. I found that I needed to click that even after changing the invalid references. My assumption is because of what you just mentioned, that the JSS does not rescan for the invalid references so there's no way for it to auto clear after the fact. Hence the need for the dismiss button. But if some folks aren't seeing that, how would they get rid of the messages?
I had one like that where the script wasn't wrong. I dismissed it.
There should have been a "re-check" command/button to make sure you'd gotten everything.
I think these are the MySQL commands they are using. Don't try this if you're not comfortable with the MySQL command-line interface:
select script_id, file_name from scripts where script_contents like "%/usr/sbin/jamf%";
select policy_id, name from policies where run_command like "%/usr/sbin/jamf%";