Posted on 07-19-2017 11:13 PM
I'm having some trouble getting two items to work as part of our New Machine Workflow. I've read a lot of documentation on this but can't seem to fix either, and some research indicates that it might not be possible.
1) We execute a New Machine Workflow based on a PreStage enrollment + policies that the system receives from DEP. During the build, though, it sits at the login screen with no indicator of progress. We wanted to use jamfHelper to load a fullscreen GUI to execute this. We have tried running a plist to execute as a LaunchDaemon, and also setting a cronjob to run a script. Both run fine when run as a user, but won't load at the loginwindow. Here's the plist:
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Label</key> <string>com.agdt.LoginMessage</string> <key>LimitLoadToSessionType</key> <string>LoginWindow</string> <key>ProgramArguments</key> <array> <string>/Library/Application Support/JAMF/bin/jamfHelper.app/Contents/MacOS/jamfHelper</string> <string>-windowType</string> <string>fs</string> <string>-title</string> <string>"Preparing your Desktop experience..."</string> <string>-description</string> <string>"We are getting your system ready. Please sit tight."</string> <string>-icon</string> <string>"/System/Library/CoreServices/Software Update.app/Contents/Resources/SoftwareUpdate.icns"</string> </array> </dict> </plist>
2) We have to sort computers into various sites and would like to do this through a GUI popup via AppleScript. We have this script working (pops up a department choice window and writes result to a text file) but cannot get that to load over the login window either.
Is it possible to load any windows over the loginwindow in any way that would allow us to do either of these?
Posted on 07-20-2017 03:17 AM
jamfHelper can appear over the login window, although I've only had it work recently with a launchagent (much like your example) in /Library/LaunchAgents. If you logout from a user account, jamfHelper will run then over the login window.
calling it via a script etc doesn't seem to work.