scrippitng support - block imessage

which doesn't work if the student reproduced the application as another name.

The problem right there is that you're using the full application name, probably including the .app at the end. Drop that and simply use the "Messages" process name and it will work no matter how many times they copy the app and rename it.

@mm2270 all the student needs to do is duplicate the app and rename it to something random, and it will continue to function.

Might be other ways... but one solution might be to use AppWarden, and modify the 'AppWarden-WillLaunch' script to look something like this:

#!/bin/bash
sv_ThisAppBundleIdentifier="$(echo ${1} | cut -d":" -f3)"
if [ "${sv_ThisAppBundleIdentifier}" = "com.apple.iChat" ]
then
  sv_ThisAppProcessID="$(echo ${1} | cut -d":" -f6)"
  kill ${sv_ThisAppProcessID}
fi

@Malcolm I don't think you understand what I was saying. If you use the full application name for the restriction, like Messages.app then yes, naming it something random gets around the restriction, because it can no longer see Messages.app but will instead see Foo.app or whatever it was renamed to.

This isn't the case however, if you use just Messages and check the "Restrict Exact Process Name" checkbox in the Restricted Software entry. This is because buried within the Messages.app is a "Messages" binary, in the path /Applications/Messages.app/Contents/MacOS/Messages This is actually the program that runs when it's launched. The end user cannot rename that or the app won't run at all, and Restricted Software will pick up the process name if you set it up as I outlined above, and close it down.