NVM. I am dumb. I had it as a launch daemon.
If you want to use this process with macOS 10.15 (10.15.0 specifically), I've found that you need to kill the loginwindow process twice back to back in order for jamfHelper to stay present. Killing loginwindow once quickly flashes a jamfHelper screen and then it goes away.
Also, I've updated the script I'm using for this to be more versatile. I've put the LaunchAgent creation and loginwindow restarts into a function, making it easy to change the jamfHelper message if you want to.
Computer_Enrollment_LaunchAgent.sh
@cbrewer Thanks for that, I came in just to see if someone had a Catalina update available. We're going to start testing your script. Cheers!
If you want to use this process with macOS 10.15 (10.15.0 specifically), I've found that you need to kill the loginwindow process twice back to back in order for jamfHelper to stay present. Killing loginwindow once quickly flashes a jamfHelper screen and then it goes away.
Also, I've updated the script I'm using for this to be more versatile. I've put the LaunchAgent creation and loginwindow restarts into a function, making it easy to change the jamfHelper message if you want to.
Computer_Enrollment_LaunchAgent.sh
Thank you for your contribution. I am trying to use your script on Monterey and having issue.
When I apply it to Mac which no one logged on previously, log in screen flash and goes back to the log in screen. When I apply it to Mac after any account logged on and out, it works perfectly. Any suggestion I can try? thanks!
@cbrewer Thanks for that, I came in just to see if someone had a Catalina update available. We're going to start testing your script. Cheers!
Delete
Thank you for your contribution. I am trying to use your script on Monterey and having issue.
When I apply it to Mac which no one logged on previously, log in screen flash and goes back to the log in screen. When I apply it to Mac after any account logged on and out, it works perfectly. Any suggestion I can try? thanks!
I am no longer using this method. Running jamfHelper at the login window got too unreliable for us. We are now creating a dedicated setup user account, logging into that account and then using DEPNotify for progress status. I then use a jamf startup policy and script to remove the setup account. It's much more reliable and DEPNotify is a very common workflow at this point.
I am no longer using this method. Running jamfHelper at the login window got too unreliable for us. We are now creating a dedicated setup user account, logging into that account and then using DEPNotify for progress status. I then use a jamf startup policy and script to remove the setup account. It's much more reliable and DEPNotify is a very common workflow at this point.
Thanks. I will check out the workflow using the DEPNotify.
