Anyone have any idea how I can fix this?
I have a self service policy for AD bind issues, it first runs a script that does a forced unbind then it applies the Directory Binding from the JSS.
Everytime I run it, it throws up a failled message but when you check... it actually succeeded and bound the machine perfectly.
Here's the policy log from one such event:
Executing Policy AD Re-Bind...
[STEP 1 of 2]
Running script Force Un-Bind...
Script exit code: 0
Script result:
[STEP 2 of 2]
Binding usernamemac to domain.foo.local...
An error occurred binding to Active Directory: . (Attempt 1)
An error occurred binding to Active Directory: dsconfigad: This computer is already 'bound' to Active Directory. You must 'unbind' with '-remove' first. (Attempt 2)
An error occurred binding to Active Directory: dsconfigad: This computer is already 'bound' to Active Directory. You must 'unbind' with '-remove' first. (Attempt 3)
An error occurred binding to Active Directory: dsconfigad: This computer is already 'bound' to Active Directory. You must 'unbind' with '-remove' first. (Attempt 4)
An error occurred binding to Active Directory: dsconfigad: This computer is already 'bound' to Active Directory. You must 'unbind' with '-remove' first. (Attempt 5)
Error: Giving up on Active Directory binding after 5 attempts.Anything I can try? Since it works it's really just an annoyance factor of throwing up that failed message so I never really know if it did or did not fail unless I double check it.
