Fog Client will change name but will not join Domain

[Gary Kulovics]

I am running SVN Revision: 5864 version of Fog and Fog Client v0.11.2 Fog will change the name of the PC then after reboot for name change it looks like the client does not start-up again at reboot and therefore won’t join domain
Anyone have this problem and if so did you get to fix this probem I have 1200 pc’s to image and that would be a pain to have to join the domain manual

PS
It did use to work

Thanks
Gary

[URfog]

Hi

@Gary-Kulovics said in Fog Client will change name but will not join Domain:

I am running SVN Revision: 5864 version of Fog and Fog Client v0.11.2 Fog will change the name of the PC then after reboot for name change it looks like the client does not start-up again at reboot and therefore won’t join domain
Anyone have this problem and if so did you get to fix this probem I have 1200 pc’s to image and that would be a pain to have to join the domain manual

PS
It did use to work

Thanks
Gary

I use the
FOG_ENFORCE_HOST_CHANGES option and it works.

[Wayne Workman]

@Gary-Kulovics There was a problem on 0.11.2 that caused the client to crash in certain situations concerning JIT, read here for more information: https://news.fogproject.org/fog-client-v0-11-3-released/

I’m not saying that’s your issue, but it could be possible. To get the latest version, all you need to do is update fog to the latest, all clients will automatically update.

Additionally - we need a fog.log from an affected host. It’s here: C:\fog.log
Please deploy one of the affected hosts and let it do it’s thing, and grab the log afterwards and upload here.
Also, what OS are you deploying?

[Gary Kulovics]

Have updated to the new svn and fog client is at v.0.11.3 Good news it doesn’t crash bad news still does not join domain attached is the file your requested 0_1468592748985_fog.log

[Gary Kulovics]

@URfog Thanks for the help That option was turned on but still did not join domain Thanks for your help thou

Gary

[Quazz]

@Gary-Kulovics

15/07/2016 10:16 AM HostnameChanger ERROR: Required ADDom Joining information is missing

So you’ll need to update your info at the relevant location (hosts or group)

[Wayne Workman]

@Gary-Kulovics What Quazz is refering to is the new domain joining password. You type it in as clear text. There’s a global default in Web Interface -> FOG Configuration -> FOG Settings -> Active Directory Defaults -> FOG_AD_DEFAULT_PASSWORD

After doing this, you can use groups to mass-apply these defaults to hosts.

[Gary Kulovics]

@Wayne-Workman Thanks that setting was already done But I had to change it at the host level and now it work Thanks everybody for there help Now have a bigger problem will open a new tread Again Thanks