FogService will not join windows 10 machine to domain

[theBiggestRick]

I am attempting to get the fog service to auto join the computer to my domain on windows 10. After imaging it will reboot a few times and then remain on windows 10 multi user login, not domain login. Upon checking the error log (shown below) I believe it might have to do with the account specified in the web interface for domain joining? Any help on this would be greatly appreciated.

[Joe Schmitt]

@theBiggestRick Please attach more of the log. That one section is only renaming the computer. I need to see the HostnameChanger log section when it attempts to join the domain.

[theBiggestRick]

^ this may be the issue…

[Joe Schmitt]

@theBiggestRick you can change that setting under the Active Directory tab on a host/group. (The Make changes even when users are logged on? checkbox)

[theBiggestRick]

thanks for the help, host joined domain successfully. Now however I have encountered this issue with every domain account when trying to log into that machine. Anybody seen this before? I’ve googled around for it, but apparently doesn’t happen much in a domain.

[Avaryan]

@theBiggestRick Did you enable the Administrator account and set a password in your unattend file?

[Wayne Workman]

@theBiggestRick New one on me… Our whole district is basically Win10 now (thank you, fog), and we have not seen this. That’s about 5,000 devices and 25 different models, fyi. We didn’t sysprep one of them, either. We have about 8 or 9 domains, they all work just fine. Accounts work fine.

[theBiggestRick]

@Avaryan yes and those accounts will show before the fog service joins the computer to the domain

[theBiggestRick]

@Wayne-Workman you didn’t sysprep? What type of image did you set in the configuration? Also, Windows doesn’t freak out when imaged to other models??

[Wayne Workman]

@theBiggestRick We don’t sysprep because it’s not necessary, and creates a layer of complication. We have an image for each model. And this works fine. Space is cheap, fog compresses well, and we can build images pretty fast, and we don’t have any issues with this method. The skillsets involved are those that everyone in my department have and understand.

I’d like to transition to a single universal image - but my co-workers just aren’t there yet, they don’t get it, and it really takes one or two people that really know how to do it instead of having just everyone trying to do it. I’m in a weird scenario…

[theBiggestRick]

@Wayne-Workman when you create the image, do you use the built in audit mode or create a local account?

[Wayne Workman]

@theBiggestRick We use a local account to build the image from scratch. From scratch meaning we format the drive - install all drivers ourselves, don’t include any terrible security-risk manufacturer bloatware. We optimize the image for the model and use it will be used for.

[theBiggestRick]

@Wayne-Workman Alright, I will have to test it out. Thanks!