Help with Binding OSX 10.7.3 Machines to Microsoft AD

You used the term "package" a few times in your post. Are you using a physical package to deploy this or is it a binding configuration stored in the JSS?

I'm sorry. Guessing that I'm not using the right jargon yet. :)

Here's what I did.

I went into Casper Admin on my JSS. Created a binding configuration
Launched Casper Remote, and attempted to apply that binding config, by checking the name of the Binding under the 'Accounts' tab.

Bill

No prob. That's what I figured you were doing. Just wanted to make sure you weren't building a pkg with a post flight script in it or something. :)

So, the next step I would try is a manual bind in Directory Utility with the same settings, which you may have already tried. If so, try putting a script together using dsconfigad with the same settings and run that manually.
Something else you could try is on one of the affected Macs, use the jamf binary to bind the Mac (type 'jamf help bind' in Terminal for the full rundown of how to use it)

Lastly, I have seen times when Casper Remote does not properly execute scripts or binding configs as opposed to a regular policy. You could optionally try assigning the binding configuration to a policy and scope one Mac to it, use your everyX minutes check in and let it try to run normally to see if there is any difference.

Awesome info, and suggestions. I'll get working on them!

btw, I did try this through a policy, though forgot to mention it. --That also failed.--

Thanks again!

That was it!!! The system time was 14 minutes off. I changed it to the actual time, used Casper Remote to kick the binding off. BINGO!

Wow, thank you both so much!

Thanks you SOOOOO MUCH! This is the ANSWER!!!!!

a little tip if you are setting this by hand first.

you can put this in a preflight script or whatever to have your package do the work for you.

ntpdate -u yourtimserver.domain.com

I was having the same problem. I tried everything and it was also the time. Thanks!

nevermind