Skip to main content

Since we upgraded to Casper 8.51 our bind script has stopped working under Lion. (haven't tried SL). Basically the script just sets the time server then binds to the domain.



This morning I setup Casper 8.52 and tried to image a machine.



I checked the imaging logs and it shows it's going to run it, and I looked at jamf.log and it says it's running the script and there's no errors.



The machine doesn't end up binding though.
I let it sit for 2 hrs and it never binds.



As a test I just used Casper Remote to push the same bind script and it bound fine.

I'm using Casper binding as opposed to a script. I've noticed that after imaging a Lion machine, I have to restart that computer before it'll allow a domain user to logon.

It was working in 8.43 on lion just fine, in fact, with the time zone change bundled in with the bind, that's how the deployment group knew the machine was safe to log into.

8.51 and 8.52 have issues with AD and MDM profile while imaging atm.
https://jamfnation.jamfsoftware.com/discussion.html?id=4257



These issues have been logged with QA Engineers at JAMF already with instructions given to reproduce the behavior.



With v8.5x Imaging Tasks Completed After Reboot Process has been changed and causing these issues for us. I have JSS v8.51 installed and for the workaround we use Casper Imaging 8.43 in our NetBoot image until JAMF fixes these issues.

Bit of Background:
We use InstallESD image method described in https://jamfnation.jamfsoftware.com/discussion.html?id=3841 by Jason and all the custom settings like Localisation, NTP, Language, etc setup via a post image script 'At Reboot' (customised script of Tom Larkin's post install script - https://jamfnation.jamfsoftware.com/discussion.html?id=51)



Everything works fine with JSS 8.43.



Issues with v8.51/8.52:
1. We have MDM profile and AD binding issues with v8.51 and v8.52
https://jamfnation.jamfsoftware.com/discussion.html?id=4257




  1. With v8.51 when you compile a configuration from Casper Admin, if you have packages with “install at imaging time” ticked, those packages will not install when compile.



I'm pretty sure that JAMF engineers will address these issues in no time as they are the best!!!!

I was under the impression the binding and stuff would have been addressed in .52 - seeing as .50 was a test (but probably showed up), .51 was public (but still the first patched version), and now .52 it's still broken (technically the 2nd patched version). I guess I've just been spoiled by JAMFs past awesomeness. I will continue with the workaround till they get it resolved. Thank you for the background on it though, that helps.

Terms & ConditionsCookie settings