Join domain after image task - issues
-
Hello,
I am hoping you guys can help me resolve some intermittant issues. It took me quite some time getting sysprep configured the way i want. The end goal is to be able to push an image to a system and when the process is finished it would be at the login screen and the user would login with their domain credentials and away they could go.
Currently when i create a task and the image download completes sysprep runs. the system will autologin under the local admin account then reboot after a couple minutes then autologin to the admin account again then reboot. If all goes well it then boots to the login screen. This has worked on two machines.
I just started deployment on another desktop and the image downloads and it auto logs in to the admin account then nothing. It did rename the computer properly but didnt join domain. At the end of the fog log is “error code: 2” Here is a snippet for the fog.log. There is another error “error: 2692” which i believe just means that thesystem is not joined to the domain. [url]https://msdn.microsoft.com/en-us/library/windows/desktop/aa370674(v=vs.85).aspx[/url] Are there logs anywhere else i could pull to get more details about why its not completing the join domain process?
i saw another post that menitoned AD path not being correct. I know it is since it has worked on anther system.
Any ideas what the problem is?
Fog Ver: 1.2
------------begin paste ---------------
2/19/2015 1:06 PM FOG::HostnameChanger Attempting to connect to fog server... 2/19/2015 1:06 PM FOG::HostnameChanger Module is active... 2/19/2015 1:06 PM FOG::HostnameChanger AD mode requested, confirming settings. 2/19/2015 1:06 PM FOG::HostnameChanger Hostnames are different - LOCALAD-H05D2B3 - A237-12977 2/19/2015 1:06 PM FOG::HostnameChanger Attempting to unregister from domain... 2/19/2015 1:06 PM FOG::HostnameChanger Domain Error! ('Unknown Error' Code: 2692) 2/19/2015 1:06 PM FOG::HostnameChanger Using default fog method. 2/19/2015 1:06 PM FOG::HostnameChanger Computer is about to restart. 2/19/2015 1:06 PM FOG::GUIWatcher Message found, attempting to notify GUI! 2/19/2015 1:06 PM FOG::UserCleanup Starting user cleanup process... 2/19/2015 1:06 PM FOG::UserCleanup Attempting to connect to fog server... 2/19/2015 1:06 PM FOG::UserCleanup Module is disabled globally on the FOG Server, exiting. 2/19/2015 1:06 PM FOG::GUIWatcher Dispatch OK! 2/19/2015 1:09 PM FOG Service Engine Version: 3 2/19/2015 1:09 PM Starting all sub processes 2/19/2015 1:09 PM 12 modules loaded 2/19/2015 1:09 PM * Starting FOG.AutoLogOut 2/19/2015 1:09 PM * Starting FOG.SnapinClient 2/19/2015 1:09 PM * Starting FOG.DirCleaner 2/19/2015 1:09 PM * Starting FOG.GUIWatcher 2/19/2015 1:09 PM * Starting FOG.HostNameChanger 2/19/2015 1:09 PM FOG::GUIWatcher Starting GUI Watcher... 2/19/2015 1:09 PM FOG::AutoLogOut Starting process... 2/19/2015 1:09 PM FOG::DirCleaner Sleeping for 52 seconds. 2/19/2015 1:09 PM * Starting FOG.HostRegister 2/19/2015 1:09 PM FOG::ClientUpdater Starting client update process... 2/19/2015 1:09 PM FOG::ClientUpdater Sleeping for 386 seconds. 2/19/2015 1:09 PM * Starting FOG.MODDebug 2/19/2015 1:09 PM * Starting FOG.PrinterManager 2/19/2015 1:09 PM FOG::MODDebug Start Called 2/19/2015 1:09 PM FOG::MODDebug Sleeping for 100 Seconds 2/19/2015 1:09 PM * Starting FOG.SnapinClient 2/19/2015 1:09 PM FOG::HostnameChanger Starting hostname change process... 2/19/2015 1:09 PM FOG::HostnameChanger Yielding to other subservices for 7 seconds. 2/19/2015 1:09 PM FOG::HostRegister Starting host registration process... 2/19/2015 1:09 PM * Starting FOG.TaskReboot 2/19/2015 1:09 PM FOG::PrinterManager Starting interprocess communication process... 2/19/2015 1:09 PM * Starting FOG.UserCleanup 2/19/2015 1:09 PM FOG::TaskReboot Taskreboot in lazy mode. 2/19/2015 1:09 PM FOG::TaskReboot Starting Task Reboot... 2/19/2015 1:09 PM FOG::PrinterManager interprocess comm startup: OK 2/19/2015 1:09 PM * Starting FOG.UserTracker 2/19/2015 1:09 PM FOG::SnapinClient Starting snapin client process... 2/19/2015 1:09 PM FOG::UserCleanup Sleeping for 10 seconds. 2/19/2015 1:09 PM FOG::UserTracker Starting user tracking process... 2/19/2015 1:09 PM FOG::HostRegister Exiting because only 1 mac address was found. 2/19/2015 1:09 PM FOG::PrinterManager Attempting to connect to fog server... 2/19/2015 1:09 PM FOG::SnapinClient Sleeping for 477 seconds. 2/19/2015 1:09 PM FOG::UserTracker Attempting to connect to fog server... 2/19/2015 1:09 PM FOG::PrinterManager Module is active... 2/19/2015 1:09 PM FOG::PrinterManager Starting printer manager... 2/19/2015 1:09 PM FOG::PrinterManager Yielding to other services for 21 seconds. 2/19/2015 1:09 PM FOG::AutoLogOut Module is active... 2/19/2015 1:09 PM FOG::UserTracker Module is active... 2/19/2015 1:09 PM FOG::AutoLogOut Timeout value is Zero, disabling module. 2/19/2015 1:09 PM FOG::AutoLogOut c:\program files\fog\images\alo-bg.jpg 2/19/2015 1:09 PM FOG::AutoLogOut at System.Drawing.Image.FromFile(String filename, Boolean useEmbeddedColorManagement) at FOG.AutoLogOut.doWork() 2/19/2015 1:09 PM FOG::HostnameChanger Attempting to connect to fog server... 2/19/2015 1:09 PM FOG::HostnameChanger Module is active... 2/19/2015 1:09 PM FOG::HostnameChanger AD mode requested, confirming settings. 2/19/2015 1:09 PM FOG::HostnameChanger Hostname is up to date 2/19/2015 1:09 PM FOG::HostnameChanger Attempting to join domain if not already a member.... 2/19/2015 1:09 PM FOG::HostnameChanger Domain Error! ('Unknown Error' Code: 2)
~ Edited log formatting
----------- end paste ------------------ -
Its a problem with your AD settings in FOG.
A quick search of that error code reveals:
[url]http://fogproject.org/forum/threads/join-domain-unknown-error-code-2.11827/[/url] -
If that were the case then it would not have worked on two other computers, correct?
-
you can see if things are correct.
Remember, the AD settings you setup is on a Per Host basis, not a global thing.
So although the AD User/domain/pass/ou may be correct for the Global aspect, of which I guess your other 2 systems that worked fine is correct, verify if they are correct for this one host giving you issues.
-
when i check the box in the menu (main>host>choose host>active directory) to “join domain after image task” it populates the global settings which are in ‘fog settings’ so I don’t understand where the disconnect is. the machines are all the exact same model, same domain being joined, and same location (at my desk) at the moment.
Is there a way to re-run the join domain task without pushing the image again (and so i dont have to walk around later to join them to domain)?
-
the clients will check the hostname/domain on startup on every reboot. to reattempt, reboot.
-
restart the system, or restart the “FOG Service” service.
-
i was able to resolve the issue. for some reason it did not like the “Computers” container in AD. I had to make a separate OU and it is now working consistently.
Thanks for all the help.
-
Quote Belac
“Is there a way to re-run the join domain task without pushing the image again (and so i dont have to walk around later to join them to domain)?”
What about this? Is there a function for that?
-
@bigfr0g said:
Quote Belac
“Is there a way to re-run the join domain task without pushing the image again (and so i dont have to walk around later to join them to domain)?”
What about this? Is there a function for that?
If you rename or change the domain name, the client make the job without reimage the computer.
-
@ch3i said:
@bigfr0g said:
Quote Belac
“Is there a way to re-run the join domain task without pushing the image again (and so i dont have to walk around later to join them to domain)?”
What about this? Is there a function for that?
If you rename or change the domain name, the client make the job without reimage the computer.
Thats not working for me
I renamed the Domainname in the Host Configuration and in the FOG Configuration, then changed it back to the correct Name and nothing happens when I reboot.
The Computer is not in the Domain…
-
@bigfr0g FOG version? Old client or new client? Have you checked your service settings for that host?
-
@Wayne-Workman Based on the messages from the log, I’d say this is the old client, if it’s any help.