Clean up NoMADLogin Window after configuration

jalbert
Contributor

I have a policy that runs the following script, however what I think is happening is that the user is getting logged out before the command gets sent back to JamfPro that the policy has been run and it while it works, the computer is always showing as pending for the policy. Anyway, here is my script.

How can I handle this so Jamf is kept informed that the policy has been run?

#!/bin/bash
#Disable the NoMAD login window after the user has logged in and their local
#Account has been created and authenticated via AD
echo "Removing NoMAD Login Window"
/usr/local/bin/authchanger -reset
killall loginwindow
echo "Complete"
1 REPLY 1

sharriston
Contributor III

Have you tried it without the killall loginwindow? Thats how I reset the login window back to default once the user has logged in, also that script is part of my enrollment policy with the trigger "Login". Hope this helps.