We had a situation at work where we needed to lock down a few laptops over the summer break. The problem with jamfHelper and OS 10.7 and 10.8 is that you can CMD+Q and it will quit. That is okay if you just want to be annoying, but I want to lock down the computer so you can't CMD+Q the message.
I played around with a few things, like setting the keyboard to some strange language where the Q was located somewhere else but I found a better way.
/System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Support/LockScreen.app/Contents/MacOS/LockScreen
This is what Remote Desktop calls when you lock the screen, but it doesn't run on top of JamfHelper and it locks out the keyboard when it is running.
LockScreen supports an attribute tag called -msgHex and if you convert your message to hex it will display fine. But it is easier to use jamfHelper with that, as long as I run LockScreen after it locks out the keyboard and locks down the computer with my custom jamfHelper message.
Example script below..
#!/bin/sh
iconpath=""
icon=""
heading=""
description=""
/Library/Application Support/JAMF/bin/jamfHelper.app/Contents/MacOS/jamfHelper -windowType fs -icon "$iconpath$icon" -heading "$heading" -description "$description" &
/System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Support/LockScreen.app/Contents/MacOS/LockScreen -session 256 &
Now you could use this with your software update routines or other installer routines, just remember you have to kill the process if you want to get keyboard control back
/usr/bin/killall LockScreen
Anyway it is working for us rather well, just wanted to share... let me know if I missed anything or it is working for you.
Cheers