@Sebastian-Roth I found a workaround. I was able to clear the “Domain Password Legacy” value and then typed the current password in the “Domain Password” field and that worked. I will work some sql magic and will be good to go. Thanks for responding.

@Sebastian-Roth I updated to 1.5.8 a couple of weeks ago and everything went smoothly until I went to fog a workstation today. Sure enough, it would not auto-join to our domain and I am seeing the username or bad password, code 1326 in the logs. We do have encrypted AD passwords in our DB. Is the only solution to upgrade to the dev-branch or is there another workaround? Will 1.5.9 be released in the near future?