So we were on FOG version 1.4.3 and I have been putting up some Windows 10 boxes joining a SAMBA 4 PDC for Active Directory purposes.
It joins the domain and we can authenticate to it, but when I Iook into the logs, I see Errors where it is trying to re-join the domain.
I look into the fog.log and it shows the ollowing:
8/8/2019 9:53 AM Client-Info Client Version: 0.11.16
8/8/2019 9:53 AM Client-Info Client OS: Windows
8/8/2019 9:53 AM Client-Info Server Version: 1.5.7
8/8/2019 9:53 AM Middleware::Response Success
8/8/2019 9:53 AM HostnameChanger Checking Hostname
8/8/2019 9:53 AM HostnameChanger Hostname is correct
8/8/2019 9:53 AM HostnameChanger Attempting to join domain
8/8/2019 9:53 AM HostnameChanger The machine is already joined to the domain, code = 2691
(Note - I upgraded to 1.5.7 to see if this goes away, but as you can see from the log message, still having the same problem.)
When I look on System for the computer:
Computer name: <Hostname>
Full computer name: <Hostname>.<Domain>
In the past with Windows 7, it was usually:
Computer name: <hostname>
Full computer name: <hostname>
So my guess is that given that the Full computer name is outputting with the <hostname>.<domain> instead of the normal <internet domain name> is what is causing fog to constantly try and join the domain, even though it is joined.
Is there something I should be looking at on Fog Side, or Windows side? Or even our Samba side, given we went from Samba 3 to Samba 4 and had to use an NT4 Domain trick to get LDAP to pass authentication to Samba 4 and to Windows 10.
Edited: I also checked with another guy in our area who is using FOG 1.5.5 and they are doing a similar setup and also having the same problem.
The only thing I can think of is that the FOG client doesn’t seem to recognize that it is joined to the domain, so it tries again, and keeps trying, despite the Domain being set. My guy and the other guy both think this is a Windows 10 problem, but I think the FOG client may need to be updated to recognize when Windows 10 is joined to a domain, given Windows 7 will be phasing out soon.