Windows 10 EDU 1709 Domain Join Doesn't Work
-
@Jay-Bosworth you mentioned you’re using sysprep. Did you follow the client instructions for sysprep? We need more information to help solve this issue https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep
. The fact that the client isn’t logging indicates that the client didn’t start. The sysprep mis-configuration is the most likely cause. Regardless, at this point this is likely just an image configuration issue.
@andreiv A quick comment:
Why use an external tool, when the built-in one works just fine?
There are situations where the client is desired over sysprep when joining the domain, such as when you want computers to have the same hostname they have in FOG, and automatically take care of renaming the machine if you change the name in FOG. The client can also deploys software after imaging to help keep images smaller. Now if you’re in an environment where you don’t use the client (no snapins, printer management, hostname, …) then the sysprep unattended file is absolutely the way to go.
TL;DR: The client should be responsible for managing domain bindings if you want to use FOG as a management solution for software, printers, user tracking, and hostname. If you dont want the client, then sysprep unattended work just fine.
-
Yes, I have followed the client directions. It just seems to be these Lenovo’s I am having issues with. Before the sysprep I disabled and stopped the fog service. The setup complete script is in my scripts folder just like I usually do. In my sysprep I have a local account created. After I image I can login with that account and the fog service is running again.
-
@Jay-Bosworth hmmm that is strange then. So its running and not logging? New client logs are appended to the end of the
fog.logfile. -
@jay-bosworth said in Windows 10 EDU 1709 Domain Join Doesn't Work:
Yes, I have followed the client directions. It just seems to be these Lenovo’s I am having issues with. Before the sysprep I disabled and stopped the fog service. The setup complete script is in my scripts folder just like I usually do. In my sysprep I have a local account created. After I image I can login with that account and the fog service is running again.
Hi,
is the service really running? i cant believe that the log stay completely empty, is the fog.log file created?
What your fog service start option? auto or delayed-auto?If auto please try to set it do delayed.
@Joe-Schmitt wasn’t there a race condition with network and service startup?
Regards X23
-
I’ve had it happen where the service appears to be running, but it’s not actually working. I had to re-install the FOG client.
-
I think there might have been an issue where I wasn’t running sysprep fast enough while in audit mode and it was actually joining to the domain before I had a chance to run that like someone mentioned. I am testing that theory right now though. It also appears there may have been a subtle version difference between client version on my images. I will post again when this finished imaging in a couple of minutes.
-
Nope, that didn’t seem to make a difference. I applied my new sysprep imaged and waited at the login screen for about 15 minutes and it never restarted like it usually does after joining the domain.
-
I am going to just start over from scratch with this image and see what happens. I am running out of time to get this ready for production. I will update once I try this again.
-
Looks like it was something wonky in my image. I apologize for any of your time I may have wasted sorting this out. Thanks for all of the help. Now I have an updated server and a working image.
-
