Skip to main content
Question

Troubleshooting AD binding

  • February 7, 2012
  • 2 replies
  • 6 views
GeorgeCasper
Forum|alt.badge.img+4

Hello!

One of the things we'd like to start doing with the Casper Suite is binding machines to our AD domain. For years, we've done it by hand with no trouble, and indeed, we seem to still be able to on 10.7.3. However, using Casper Suite's built-in AD binding totally fails. Looking at the logs, the Jamf log looks like the process ran successfully, and the open directory log doesn't seem to mention the attempt at all. Is there somewhere else I ought to look to get a handle on what's actually happening during the AD binding attempt? Thanks.

    2 replies

    P
    Forum|alt.badge.img+12
    • pat_best
    • Contributor
    • February 8, 2012

    Have you taken a look at the console logs of any of the (attempted) binding clients?

    E
    Forum|alt.badge.img+21
    • ernstcs
    • Contributor
    • February 8, 2012

    I haven't done much for troubleshooting in Lion for AD binding since it has been working for us, particularly with 10.7.3. You may need to enable the logging level to be higher like to debug on a system, then use a Casper Remote session to attempt to bind, then look at the opendirectoryd.log to see if it gives you more detail.

    Found this article that sort of reviews the new stuff in Lion, specifically the odutil.

    http://krypted.com/active-directory/directory-services-scripting-changes-in-lion/

    Terms & ConditionsCookie settingsAccessibility statement