I have an ongoing login policy that I want to be available offline. We've had a few issues where the casper server has gone down and that renders my computer lab virtually unusable as login takes about 5 minutes while the connections to the JSS time out.
The login policy just runs a shell script that makes sure some symlinks and permissions are set for the network user (LDAP) logging in.
The policy plan reads:
This policy is set to Ongoing
This policy is triggered by login
This policy will be made available offline
This policy is assigned to 2 computer groups
Run Script UH202login_v8.sh
But the "avialable offline" part does not seem to be sticking. When the JSS is unavailable (like yesterday when the server room flooded, yikes!) The logs show failed connections to the JSS on login. Eventually it times out, and the script never runs.
Is there something else hiding that I don't know about? What should I look for? Thanks,
-Baker
Baker Franke
Computer Science Dept.
University of Chicago Laboratory Schools
773.702.5419
