Smartinstaller Client not joining computers to Domain after imaging
-
This year we are using the Smartinstaller instead of the Legacy Client. After imaging the computer will not automatically join the domain. We have used the legacy client in the past and had to copy our config file into Programs Files (x86)\FOG\etc in order to get this to work. This is the first image ever we are attempting to use the new version of the client so I am sure it is something simple I am missing. I also verified that the FOG services are set to delayed automatic start to no avail. Does anyone have ideas or thoughts on what I am missing?
Thanks,
Michael
-
@michaeloberg Please post the contents of the log file from the client (either in C:\fog.log or C:\Program Files (x86)\FOG\fog.log).
-
5/1/2019 12:56 PM Middleware::Communication URL: http://10.1.1.138/fog/management/index.php?sub=requestClientInfo&configure&newService&json 5/1/2019 12:56 PM Middleware::Response Success 5/1/2019 12:56 PM Middleware::Communication URL: http://10.1.1.138/fog/management/index.php?sub=requestClientInfo&mac=A0:66:10:07:73:ED|7C:76:35:28:66:D0|7C:76:35:28:66:D1|7E:76:35:28:66:D0|7C:76:35:28:66:D4&newService&json 5/1/2019 12:56 PM Middleware::Response Success 5/1/2019 12:56 PM Middleware::Communication URL: http://10.1.1.138/fog/service/getversion.php?clientver&newService&json 5/1/2019 12:56 PM Middleware::Communication URL: http://10.1.1.138/fog/service/getversion.php?newService&json 5/1/2019 12:56 PM Service Creating user agent cache 5/1/2019 12:56 PM Middleware::Response Invalid time 5/1/2019 12:56 PM Middleware::Response No Printers 5/1/2019 12:56 PM Middleware::Response Module is disabled globally on the FOG server ------------------------------------------------------------------------------ ---------------------------------ClientUpdater-------------------------------- ------------------------------------------------------------------------------ 5/1/2019 12:56 PM Client-Info Client Version: 0.11.16 5/1/2019 12:56 PM Client-Info Client OS: Windows 5/1/2019 12:56 PM Client-Info Server Version: 1.5.5.3 5/1/2019 12:56 PM Middleware::Response Success ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ ----------------------------------TaskReboot---------------------------------- ------------------------------------------------------------------------------ 5/1/2019 12:56 PM Client-Info Client Version: 0.11.16 5/1/2019 12:56 PM Client-Info Client OS: Windows 5/1/2019 12:56 PM Client-Info Server Version: 1.5.5.3 5/1/2019 12:56 PM Middleware::Response Success ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ --------------------------------HostnameChanger------------------------------- ------------------------------------------------------------------------------ 5/1/2019 12:56 PM Client-Info Client Version: 0.11.16 5/1/2019 12:56 PM Client-Info Client OS: Windows 5/1/2019 12:56 PM Client-Info Server Version: 1.5.5.3 5/1/2019 12:56 PM Middleware::Response Success 5/1/2019 12:56 PM HostnameChanger Checking Hostname 5/1/2019 12:56 PM HostnameChanger Hostname is correct 5/1/2019 12:56 PM HostnameChanger Attempting to join domain 5/1/2019 12:56 PM HostnameChanger Logon failure: unknown username or bad password, code = 1326 ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ ---------------------------------SnapinClient--------------------------------- ------------------------------------------------------------------------------ 5/1/2019 12:56 PM Client-Info Client Version: 0.11.16 5/1/2019 12:56 PM Client-Info Client OS: Windows 5/1/2019 12:56 PM Client-Info Server Version: 1.5.5.3 5/1/2019 12:56 PM Middleware::Response No snapins ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ --------------------------------PrinterManager-------------------------------- ------------------------------------------------------------------------------ 5/1/2019 12:56 PM Client-Info Client Version: 0.11.16 5/1/2019 12:56 PM Client-Info Client OS: Windows 5/1/2019 12:56 PM Client-Info Server Version: 1.5.5.3 5/1/2019 12:56 PM Middleware::Response No Printers ------------------------------------------------------------------------------ ------------------------------------------------------------------------------ --------------------------------PowerManagement------------------------------- ------------------------------------------------------------------------------ 5/1/2019 12:56 PM Client-Info Client Version: 0.11.16 5/1/2019 12:56 PM Client-Info Client OS: Windows 5/1/2019 12:56 PM Client-Info Server Version: 1.5.5.3 5/1/2019 12:56 PM Middleware::Response Success 5/1/2019 12:56 PM PowerManagement Calculating tasks to unschedule 5/1/2019 12:56 PM PowerManagement Calculating tasks to schedule ------------------------------------------------------------------------------ -
@michaeloberg said in Smartinstaller Client not joining computers to Domain after imaging:
Logon failure: unknown username or bad password, code = 1326The error is pretty clear. Username and/or password don’t match the credentials needed to join the machine to the domain.
We had some rumor about special characters in the password causing an issue with domain join but were never able to nail that down. See here: https://forums.fogproject.org/topic/12407/active-direcory-join-fail-bad-password-1-5-4/7 and https://forums.fogproject.org/topic/11692/active-directory-join-failing
As well you might want to read through this topic: https://forums.fogproject.org/topic/11137/ad-join-works-with-legacy-client-fails-with-new-client
-
@michaeloberg Did you ever solve this?