Machines won't join AD
-
Hello FOG Users,
I am running FOG 1.3.0-RC-8 (i don’t want to update to RC-10 because of the issues I’ve seen so far)
I noticed that since FOG 1.3 there is now 2 Domain Password columns and I think that’s where the issue is. I tried using the normal password which auto-encrypts by itself and also the Domain Password Legacy which I had working in 1.2 but nothing seems to work.The logs just read:
------------------------------------------------------------------------------ --------------------------------HostnameChanger------------------------------- ------------------------------------------------------------------------------ 2016-09-15 12:26 PM Client-Info Client Version: 0.11.5 2016-09-15 12:26 PM Client-Info Client OS: Windows 2016-09-15 12:26 PM Client-Info Server Version: 1.3.0-RC-8 2016-09-15 12:26 PM Middleware::Response Success 2016-09-15 12:26 PM HostnameChanger Checking Hostname 2016-09-15 12:26 PM HostnameChanger Hostname is correct
but it won’t join the Domain or does it even give any error to why it’s not joining. I checked the AD Defaults and tried adding the default password for the “vancouveradmin” account which had been used successfully in 1.2 without any issues.
Is there something I am missing? Oh the computer is running the updated FOG Agent and can ping FOG server just fine.
Thanks
-
thanks guys! I got it working, i ended up using the Domain Password Legacy and checking the “Join Domain after Image Task” worked. I don’t know something wonky happened.
Thanks
-
@anthony-delarosa Please post more of the fog.log. The snippet you posted cuts out any potential domain binding information.
-
ok here is the rest of that log,
------------------------------------------------------------------------------ ---------------------------------ClientUpdater-------------------------------- ------------------------------------------------------------------------------ 2016-09-15 12:26 PM Client-Info Client Version: 0.11.5 2016-09-15 12:26 PM Client-Info Client OS: Windows 2016-09-15 12:26 PM Client-Info Server Version: 1.3.0-RC-8 2016-09-15 12:26 PM Middleware::Response Success ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ ----------------------------------TaskReboot---------------------------------- ------------------------------------------------------------------------------ 2016-09-15 12:26 PM Client-Info Client Version: 0.11.5 2016-09-15 12:26 PM Client-Info Client OS: Windows 2016-09-15 12:26 PM Client-Info Server Version: 1.3.0-RC-8 2016-09-15 12:26 PM Middleware::Response Success ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ --------------------------------HostnameChanger------------------------------- ------------------------------------------------------------------------------ 2016-09-15 12:26 PM Client-Info Client Version: 0.11.5 2016-09-15 12:26 PM Client-Info Client OS: Windows 2016-09-15 12:26 PM Client-Info Server Version: 1.3.0-RC-8 2016-09-15 12:26 PM Middleware::Response Success 2016-09-15 12:26 PM HostnameChanger Checking Hostname 2016-09-15 12:26 PM HostnameChanger Hostname is correct ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ ---------------------------------SnapinClient--------------------------------- ------------------------------------------------------------------------------ 2016-09-15 12:26 PM Client-Info Client Version: 0.11.5 2016-09-15 12:26 PM Client-Info Client OS: Windows 2016-09-15 12:26 PM Client-Info Server Version: 1.3.0-RC-8 2016-09-15 12:26 PM Middleware::Response No snapins ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ --------------------------------PrinterManager-------------------------------- ------------------------------------------------------------------------------ 2016-09-15 12:26 PM Client-Info Client Version: 0.11.5 2016-09-15 12:26 PM Client-Info Client OS: Windows 2016-09-15 12:26 PM Client-Info Server Version: 1.3.0-RC-8 2016-09-15 12:26 PM Middleware::Response Module is disabled globally on the FOG server 2016-09-15 12:26 PM PrinterManager Getting installed printers ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ --------------------------------PowerManagement------------------------------- ------------------------------------------------------------------------------ 2016-09-15 12:26 PM Client-Info Client Version: 0.11.5 2016-09-15 12:26 PM Client-Info Client OS: Windows 2016-09-15 12:26 PM Client-Info Server Version: 1.3.0-RC-8 2016-09-15 12:26 PM Middleware::Response Module is disabled globally on the FOG server ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ ----------------------------------UserTracker--------------------------------- ------------------------------------------------------------------------------ 2016-09-15 12:26 PM Client-Info Client Version: 0.11.5 2016-09-15 12:26 PM Client-Info Client OS: Windows 2016-09-15 12:26 PM Client-Info Server Version: 1.3.0-RC-8 2016-09-15 12:26 PM Middleware::Response Success ------------------------------------------------------------------------------ 2016-09-15 12:26 PM Middleware::Communication URL: http://192.168.170.128/fog/management/index.php?sub=requestClientInfo&configure&newService&json 2016-09-15 12:26 PM Middleware::Response Success 2016-09-15 12:26 PM Service Sleeping for 114 seconds
-
@anthony-delarosa the log indicates that
Join Domain after image task
is not checked for the host. You can find this setting underActive Directory
on the host / group. -
i already tried that but let me try again and see if it even reboots, also it does say “after image” and this was not after the image but rather a computer name change and re-join. let me try that again, thanks for your help btw
-
@anthony.delarosa
it happened to me 2 days ago…
for my problematic host, disabling AD settings and then re enabling, put all things to work.it really reminded me of the ‘it crowd’ series…lol
-
thanks guys! I got it working, i ended up using the Domain Password Legacy and checking the “Join Domain after Image Task” worked. I don’t know something wonky happened.
Thanks
-
@anthony.delarosa The legacy pass field is in no way, shape, or form used by the new client. Probably ticking the “Join Domain” checkbox and saving caused the machine to Join the Domain.