Host won't join Domain after admin password change.
-
Hello,
I’m experiencing problems after dispatching new images to my hosts.
I’m currently running FOG 1.2.0 and can’t change that.Up until yesterday everything worked perfectly fine. But then I had to change the Administrator password on my domain for security reasons.
I then used the FOGCrypt tool to encrypt the password and changed is globally in the FOG Settings/Active Directory.
I realised that the new password was not automatically changed in all my hosts. Theses still had the old encrypted password. So I changed it manually in the host settings (Host menu/Active Directory).Unfortunately it didn’t work. After cloning the host was not automatically joined into my domain.
Please help:)
Kind regards
Alex
-
@Sebastian-Roth Thank you so much. You found the solution. The new password had an underscore ( _ ) as a chracter. I changed it and all is well again. Now I’m planning the upgrade to the latest FOG. Thanks again for your help. Alex
-
@deckerta Please provide the fog.log from one of the clients that failed domain join.
-
This post is deleted! -
@Sebastian-Roth Here the required file - Sorry for posting twice.
-
@deckerta Nothing about domain join in the log. But we only see it logging for good two minutes. So maybe the join just has not been tried yet. Let it run for at least 20 minutes and post log file again.
-
@Sebastian-Roth Thank you for your answer. You can see from my questions that I am a FOG novice. I didn’t know that it could take so long to join the domain.
So far the hosts always almost immediately rebooted and joined the domain.I will post the log in the morning.
-
@deckerta You are right there! Usually it does not take long at all. But as I did not see anything useful in the logs I though of giving it a bit more time.
We don’t actually support such old FOG versions anymore. But I was hoping to be able to give you a quick hint. I myself have not used the old client much and never debugged errors on it. This was before I joined the FOG team. So either someone else has an idea or you might think about updating your server and clients at some point.
-
@Sebastian-Roth Thank you for your answer. I now waited over night but nothing happened.
When I logged in manually I was prompted to reboot. I did so but nothing else happened.I could however manually join the host to the domain without problems using the new password.
I would like to upload the fog.log from this morning but it doesn’t seem to work.
-
@deckerta Maybe upload to some cloud space and post a link here.
-
@Sebastian-Roth Here the link to the log file.
https://1drv.ms/f/s!As00uPIEvs3Ih656JzjUG1-jxhn0Xg -
@Sebastian-Roth I now set back the password of the domain to the old values and it worked again.
It seems to be a password problem or an encryption problem.
I tried to re-encrypt the old password agai and the values are exactly the same.
Are there special restrictions as far as the password use is concerned? Are special characters prohibited from use? -
@Sebastian-Roth
That leaves me with the second part of my problem: I changed the password globally in the FOG Settings/Active Directory.
I realised that the new password was not automatically changed in all my hosts.
Do I have to do that manually? -
@deckerta said in Host won't join Domain after admin password change.:
I realised that the new password was not automatically changed in all my hosts.
Do I have to do that manually?Yeah, as far as I know the global setting will only be used for new hosts to be added but it won’t populate out to all the existing hosts.
Thanks for the log. Here we got the error:
FOG::HostnameChanger Der Index und die Länge müssen sich auf eine Position in der Zeichenfolge beziehen.
Parametername: lengthGerman for:
FOG::HostnameChanger Index and length must refer to a location within the string.
Param name: lengthJust a guess but I think this could be caused by some special character. But we won’t fix the old client so I won’t waste the time to look into it. You might just try different special characters within your password to see if you can figure out which one is causing this. Please keep us posted.
-
@Sebastian-Roth Thank you so much. You found the solution. The new password had an underscore ( _ ) as a chracter. I changed it and all is well again. Now I’m planning the upgrade to the latest FOG. Thanks again for your help. Alex