Hey guys,
I'm facing a problem where it seems, that some scripts are cached somehow. When I look at the policy Logs everything is fine, my Script is downloaded. But i changed the script recently and the old version is executed. When I download the script file manually, I get the new Version. At the moment, this occurs on a script run by the LoginHook trigger, but I'm sure, that I seen this behavior also on a normal policy some time ago.
Renaming the script gets the new version executed, but this is obviously not a solution for every script.
Is there a known caching directory used by the jamf binary? If I look at the /Library/Application Support/JAMF/ directory, there is no cached script, not even in a renamed version. Problems caused by multiple Distribution Pionts can be excluded, as we only have one.
Any hints?
Thank you!
Oliver Kett