The login / logout hooks don't change, they just call a script which runs any policies using the login and / or logout triggers. So they should be reading the script from the JSS.

Wrong post : )

Heh, never mind.

@davidacland this particular one runs a script that is also set to run offline... I failed to mention this, sorry.

Ah, you may be running into an issue where the offline cached script is getting called instead of downloading it from the server. I'd flush out the cached policy from the Mac. These get stored inside /Library/Application Support/JAMF/Offline Policies/ and will be inside a folder in that location with the name of the policy, so you may need to delete that entire policy name directory.
Note that the "Offline Policies" folder is a protected location, so you'll need root to even peek inside it.

@mm2270 Thanks dude... I think that will do the trick

Hmm, not sure without testing. Some things that I suspect would refresh it:

• Removing the computers from the scope of the policy, waiting for them to check-in, and then adding them back into scope. I would expect that they would remove the offline copies from the clients if they are no longer in scope.
• Switching off the offline setting, waiting for clients to checkin and then re-enable it.

Bit of a pain either way though.