Windows 11 failing to join domain
-
We’re moving over to Windows 11. I’ve created an image after joining and un-joining to the domain. After loading this new image on a PC it fails to join the domain. I’m getting the following error message in fog.log.
------------------------------------------------------------------------------ --------------------------------HostnameChanger------------------------------- ------------------------------------------------------------------------------ 8/28/2025 6:24:02 AM Client-Info Client Version: 0.13.0 8/28/2025 6:24:02 AM Client-Info Client OS: Windows 8/28/2025 6:24:02 AM Client-Info Server Version: 1.5.10.48 8/28/2025 6:24:02 AM Middleware::Response Success 8/28/2025 6:24:02 AM HostnameChanger Checking Hostname 8/28/2025 6:24:02 AM HostnameChanger Hostname is correct 8/28/2025 6:24:02 AM HostnameChanger Attempting to join domain 8/28/2025 6:24:02 AM HostnameChanger The specified domain either does not exist or could not be contacted, code = 1355 ------------------------------------------------------------------------------Manually joining the domain works correctly so I have a work around. Any thoughts?
Thanks
-
I solved my issue. Turns out changing the global active directory value for the domain name doesn’t change existing hosts. Once I changed each existing host individually the PC joined the domain correctly.
Thanks
-
@chunter2 It does look like you’re on an older version of fog. Updating to the latest stable, dev-branch, or my favorite working-1.6 version may help.
But also, are you saying that you joined the domain, then unjoined and then captured an image of that? Generally you don’t want to join the domain where you’re capturing, it’s much cleaner if it’s never joined the domain.
Or are you saying you’re trying to re-join the domain on a normal host? This could be an issue on the host’s settings in fog, could that have been changed on accident? Maybe autofill from a password manager changed the domain and or domain join password? -
@JJ-Fullmer I’ll see about updating fog. I was waiting on that until I updated my Ubuntu install to 24.04.
Yes, I joined then unjoined. I did this because of an issue I had joining the domain when I was working on Windows 10 images a few years ago. You can see my ticket I just responded to about it. It seemed to fix things back then.
-
@chunter2 This domain does not exist or dcouldn’t be contacted seems to be indicative of the problem. Simply put, from the message you show, it seems the DNS isnt’ able to reach the domain controller.
I highly doubt this is due to the version of FOG based on this, but my perspective is obviously very limited at this point.
-
@Tom-Elliott I would agree. Is there any way to get any more logging out of the client to maybe help diagnose the issue? Like the values of the parameters that are being passed in?
-
I solved my issue. Turns out changing the global active directory value for the domain name doesn’t change existing hosts. Once I changed each existing host individually the PC joined the domain correctly.
Thanks
-
C chunter2 has marked this topic as solved
-
@chunter2 Ah, yes that would do it.
That just becomes the default value when creating new hosts.
If you set it via a group, it will update those values on all hosts in a given group, but it doesn’t do that dynamically/perpetually.
