Is there any particular reason that would cause policies triggered at login to be so unreliable?
I have a login script which needs to run every time a user logs in. The actual outcome can be one of the following:
- The script runs perfectly
- There is a delay, but once the script gets started it runs perfectly
- Only parts of the script seem to get executed
- The script doesn't run at all and has to be manually triggered by the user from Self-Service
What causes this? How do I troubleshoot this? It's not due to the age of the Mac because we see this behaviour even on brand new Macs.
This seems to have been a problem ever since we started using the Jamf system - we're currently on version 10.6.0 and it still happens.
Alternatively if the login trigger can't be fixed, is there an alternative way to run a script at login while still having it centrally stored and managed in the Scripts area of the Jamf system? I don't want it to have to be a file that I have to deploy out every time I need to make a change.
I'm happy to post the script if that's needed, but it is quite long so I didn't want to spam everyone with a massive wall of text in the opening post.
Thanks,
Dan Jackson (Senior ITServices Technician)
Long Road Sixth Form College
Cambridge, UK.
