Is there any sort of internal mechanism in which the jamf binary can determine whether or not a computer is enrolled, and if not, attempt an enrollment? We are hoping to begin pre-installing Casper as part of our DeployStudio imaging workflow, but these do not always occur when the JSS itself is reachable. It appears that if the enrollment process triggered by the postinstall script fails, it never tries to subsequently enroll again.
So far with Casper all of our computers have been enrolled through User-Initiated Enrollment (going to the JSS URL/enroll, logging in with LDAP credentials, downloading the QuickAdd.pkg installer, running it manually). This has had the benefit of having the computer's Location information populated with the correct info of the primary user of the machine, but the down side of relying on the end user to go through the steps of getting Casper installed.