Closed Sebastian-Roth closed 4 years ago
Having a closer look at this I reckon this isn't something we can fix in the fog-client because it seems to be something special in the AD environments of those users. For example the case mentioned above states that using white_spire\fog
worked in his case although the domain is mentioned as whitespire.local
(without underscore)! Reading between the lines white_spire
seems to be the name of the AD controller and so this doesn't seem to be a normal AD account. Not sure.
In the FOG code sending the information to the fog-client Tom already added some logic that would check if username has \
or @
in it and just use that or if no delimiter is found it sends DOMAIN\username
to the fog-client (code ref). So there is nothing we can do in the FOG/fog-client code I suppose.
Seems like in some cases AD user information needs to be in the format
DOMAIN\username
to make AD join/rename work and sometimes simplyusername
(and domain given in the separte field) works.Here is one case described in the forums https://forums.fogproject.org/topic/13257/error-code-1326 and on our test system I ran into the same thing when using an account other than the official domain admin account. Maybe that's somehow making a difference. Maybe just on Win 10 clients - not sure yet.