Skip to main content
Question

AD Binding Issues in DeployStudio 1.6.14??

  • May 4, 2015
  • 8 replies
  • 36 views
C
Forum|alt.badge.img+5

Hi, has anyone else faced this issue? New 1.6.14 does all the job except binding Mac to AD. I am sure the password entered in workflow is correct still it gives error -
Initially, I get error that credentials are invalid.
it tries for 5 attempts, and then:
dsconfigad: Credential verification failed because account is expired (5302)
And it locks out the account after 5 attempts and starts giving me the error 5302.

This means the password entered is not working, or DS is taking it incorrect after upgrade, before upgrade it was working all well.
The same password works when I get it unlocked and try to bind a Mac manually to the same OU. This password has been entered there since quite few years. I also tried to reenter the password in the workflow to ensure it is correct. But no luck...
Any suggestion?

    8 replies

    bentoms
    Forum|alt.badge.img+35
    • bentoms
    • Hall of Fame
    • May 4, 2015

    @cindySingh @timsutton posted an issue over at the DS Forum

    G
    Forum|alt.badge.img+4

    Exactly right @bentoms Pushing it back to 1.6.12 fixed it for me. Try in your setup @cindySingh

    A
    Forum|alt.badge.img+3
    • achilver
    • New Contributor
    • May 6, 2015

    Experiencing the same issue. Upgraded DeployStudio to v1.6.14 (150502) last night and today AD bind reporting credential errors. I know the account is fine and the password is ok as I can log in to a computer using the credentials. This appears then to be a DeployStudio issue. I am rolling it back to previous version.

    C
    Forum|alt.badge.img+16
    • chriscollins
    • Honored Contributor
    • May 6, 2015

    They just released a new version today that fixes this issue.

    bentoms
    Forum|alt.badge.img+35
    • bentoms
    • Hall of Fame
    • May 6, 2015

    Yup 1.6.15

    A
    Forum|alt.badge.img+3
    • achilver
    • New Contributor
    • May 6, 2015

    Anyone care to test it. :-) I rolled back this morning to v1.6.13 and am not prepared to do it all over again unless I know it works.

    B
    Forum|alt.badge.img
    • bradh
    • New Contributor
    • May 7, 2015

    Hooray! 1.6.15 update fixed the AD binding issue from 1.6.14 for us.
    The DC it was trying to contact was not our local DC (wrong IP address logged at post-install window), therefore the credentials were not accepted.

    A
    Forum|alt.badge.img+3
    • achilver
    • New Contributor
    • May 7, 2015

    I concur. Upgraded to v1.6.15 then tested and now working fine.

    Terms & ConditionsCookie settingsAccessibility statement