Hostname CHanger not working since moving to 1.0.1
-
namechange is working for me. the computer you create an image from should NOT be joined to the domain, if that’s what you’re asking.
-
I have the same problem since version 1.0.1.
The name of the position changes well but the post does not add to domain.
This is a hassle, I redid the procedure using FOG-Crypt days then making the customer. No change. -
It could be your using a different pass key for FOG-Crypt. If you are, then you need to recompile HostnameChange.dll in the client.
[url]http://www.fogproject.org/wiki/index.php/Managing_FOG#Encrypting_Your_Password[/url]
-
i use this key :
Input string: *******
Passkey: FOG-OpenSource-Imaging
Output: b711a695df5558b61be85cc70caf0860this is the default key.
-
FOG_AD_DEFAULT_DOMAINNAME : mydomain.local
FOG_AD_DEFAULT_USER : mydomain\myuserad
FOG_AD_DEFAULT_PASSWORD : b711a695df5558b61be85cc70caf0860My parameters is correctly. i think ? No
The hostname of the computer changed the computer not detect purpose, that he is in workgroup and not domain.So this one is not added to the domain.
-
[quote=“M@x-3d, post: 27416, member: 24254”]FOG_AD_DEFAULT_DOMAINNAME : mydomain.local
FOG_AD_DEFAULT_USER : mydomain\myuserad
FOG_AD_DEFAULT_PASSWORD : b711a695df5558b61be85cc70caf0860My parameters is correctly. i think ? No
The hostname of the computer changed the computer not detect purpose, that he is in workgroup and not domain.So this one is not added to the domain.[/quote]
Try this:
FOG_AD_DEFAULT_USER : myuserad
FOG_AD_DEFAULT_PASSWORD : b711a695df5558b61be85cc70caf0860With FOG 0.33 and UP, I’ve moved the method of the user so the Domain automatically gets sent. What this means is you no longer have to specify the domain with the name. I didn’t get a chance to check if it is already set, so the reason it’s most likely failing is because it’s literally trying to send the username as:
mydomain.local\mydomain\myuseradThis wouldn’t work because this particular user doesn’t exist.
-
Thanks Thoms Elliot.
Everything works again.
I think it will update the wiki.
[url]http://www.fogproject.org/wiki/index.php/Managing_FOG[/url] # Encrypting_Your_Password
So other than me find the documentation for version 1.0.1
Thank you again and good luck. This is a good project.
-
I am having similar issues. Clients will not join the domain on 1.0.1.
The Fog Log on the client says: HostnameChanger Domain Error! (‘Unknown Error’ Code: 2725)
(My Setup)
[I][SIZE=12px]FOG_AD_DEFAULT_DOMAINNAME : mydomain.local[/SIZE][/I]
[I][SIZE=12px]FOG_AD_DEFAULT_USER : myuserad[/SIZE][/I]
[I][SIZE=12px]FOG_AD_DEFAULT_PASSWORD : b711a695df5558b61be85cc70caf0860[/SIZE][/I]Any info would be greatly appreciated.
-
Is your setup literally showing with:
mydomain.local
myuserad
and that password?If so, this is likely the problem. The Password is a hash and not one YOU should be attempting to use.
mydomain.local is a variable based on your environment. You can’t literally use mydomain.local if your domain is not named mydomain
myuserad must also be a valid Active Directory user.
-
Thanks, sorry about the lack of info. I’ve been using FOG for about 5 years now, but installing, building images and deploying images is about all I have experience with.
I put generic info in my post to protect the innocent and didn’t literally put that info in
I have used FogCrypt from the client portal to create the encrypted password for my unique local AD Admin Account and then placed that info in the FOG Active Directory Section of the UI, (following the wiki and forum instructions). I have scoured to see if similar issues have occurred and this is the closest thread I have found.
My Environment:
I recently did a clean install of 1.01 to a Ubuntu 14.04 box.Everything seems to be working great except the HostnameChanger Joining to the Domain. I’m hoping it’s something dumb that I missed.
Thank you for continuing this project and all of your help!
-
well, if you’re looking for “dumb” things that can keep this from working, here’s some mistakes i’ve made in the past…
make sure that “Join Domain after image task” is set, with the proper information, under “Host Management” > “Active Directory”
make sure that the “Hostname Changer” under “Service configuration” setting is enabled under “Service Settings” -
Yeah, I am really hoping that it might be a Monday detail, but I do think I have both of those correct. Thank you though, it might be that simple with something else I missed.
[LEFT] [/LEFT]
[LEFT]Here is the UI config.[/LEFT]
[LEFT] [/LEFT]
[CENTER][IMG]http://vanlueschool.org/pictures/snip.png[/IMG][/CENTER]
[CENTER][IMG]http://vanlueschool.org/pictures/snip2.png[/IMG][/CENTER] -
One more piece of info needed is the Active Directory settings on that host.
Host Management --> (the host having issues) --> [URL=‘http://rasdfog.dyndns.org/fog/management/index.php?node=host&sub=edit&id=1#host-active-directory’]Active Directory[/URL]
IS that info checked and filled out?
Edit: (facepalm)
-
Yes. That screen shot was from the actual host settings in FOG. It is also the default in the FOG active directory section as well.
-
Welp, I FOG’d a second image, Windows 8 32bit and deployed it without changing any settings and it automatically joined the domain. So I am going to delete the 64bit host from FOG, perform full host inventory it and redeploy and see what happens. I will keep you posted. There may be something going on with that particular Windows 8 x64bit image.
-
you’ve been using fog for 5 years, right? do you have a custom compiled [FONT=sans-serif][COLOR=#000000]HostnameChange.dll on your images? will this match the passkey used in fogcrypt?[/COLOR][/FONT]
-
Good thought but no I do not have a custom compiled HostnameChange.dll.
I’m thinking it has something to do with the way the image was made. I had it on the domain, installed the fog client, took it off the domain and then uploaded it, so I may have caused the issue. I am going to build a fresh 64bit windows 8 image and see if this solves the issue.
-
I have recently done a clean windows 8.1 install and image and the hostname changer is not doing anything. completely stock FOG (latest trunk as of this morning) and stock FOG client, etc. Any news on this issue?
EDIT: No active directory usage here either.
-
check your fog.log in the c:\ of the client, is it connecting to the server? are there any errors?
-
[quote=“Junkhacker, post: 27579, member: 21583”]check your fog.log in the c:\ of the client, is it connecting to the server? are there any errors?[/quote]
That log shows exactly what i would expect it to if the hostname changer had worked… it even says “Hostname is up to date”… yet the hostname is still the same as the base image’s.
