Fog 1.0.1 and Ubuntu 14.04 joining domain problems
-
My guess to the problem?
The password salt you used (changed in config.ini) is not what the HostnameChanger.dll file is expecting.
-
I guess I’m not that familiar with the hostnamechanger.dll, is that something I can change?
-
I think I found this here [url]http://www.fogproject.org/wiki/index.php?title=Managing_FOG[/url]
Am I understanding correctly, I should recompile the hostnamechanger.dll?
-
I also tried generating an encrypted password with the default config.ini, same result
-
Ok, I double checked the HostNameChange on the server using Microsoft Visual Studio Express, the client name is still updating however I am still unable to join it to the domain… This is what the log is showing now
5/28/2014 10:00 AM FOG::HostnameChanger Unknown error, module will exit.
5/28/2014 10:00 AM FOG::HostnameChanger Host name was not found in the database.I also tried removing the client from FOG and re-imaging like it was a brand new PC, however still the same result
-
try going to [url]http://<fog-server-ip>/fog/service/hostname.php?mac=<mac[/url] address of host> and let me know what you get
-
[SIZE=4][FONT=Times New Roman][COLOR=#000000]#!ok=a0481c7ef9cd #AD=1 #ADDom=domain #ADOU= #ADUser=mydomain\mydomainuser#ADPass=encryptedpassword[/COLOR][/FONT][/SIZE]
[SIZE=3][FONT=Times New Roman][COLOR=#000000]I changed the results for security reasons, but I can confirm the domain and user were correct[/COLOR][/FONT][/SIZE]
-
you might try setting the fog service on the client to delayed start
also, some people have had trouble if they installed the client for “Just me” instead of “Everyone” -
Ok, trying the Automatic (Delayed Start) I know when I installed the service piece I installed it “for Everyone”
I think we’re getting closer though, it’s showing a new error in the log “Domain Error! (‘Unknown Error’ Code: 1326)”
-
-
also just to put my 2 cents in i found that in Fog 1.0.1 that if you just use your usename and not youdomain\username it works unlink in fog 0.32 i had to use yourdomial\username
-
I tried all that yesterday as noted in my first post, the .ini file, made sure it wasn’t in AD already, and were not previously joined to the domain, and checked all of the global and client service settings
I also tried manually forcing it to the OU instead of leaving it blank for default
still getting the 1326
-
Ok, I on a whim created a new user in AD with sole purpose of joining computers to AD, re-encrypted a new password and it appears to have resolved the issue.
Can’t thank you guys enough for the help and the amazing software
Thanks,
Matt
