@Sebastian-Roth said in Host can’t join AD:

In a fair amount of cases people had to use domain\username in the username field but also specific the domain in it’s own field to make it work

You have totally right, it works with myDomain\userName.

Thanks Sebastian.

@Lemeunier Sounds strange. Possibly your disk is full? Run df -h and post output here.

@Quazz ok, then i keep my already downloaded kernels/inits, and wait for next release for further tests.

Something i don’t anderstand is : I’ve got an other highscool to handle and i’m using fog on ubuntu too. I’ve got to upgrade the distribution here (to 17.10) and i’ve got no issue like this or at all…

I’ve got a new issue just only with the AD join function… Here in the fog log :

03/05/2018 20:49 HostnameChanger Logon failure: unknown username or bad password, code = 1326

I havn’t change anything about the acount for joining the domain… Is there a new way to configure that ?

EDIT: a server update has desactivated the fog acount (for modifying the password)… Problem solved

@scott-b Yes i’me sure (“control userpasswords2” tells me it). I’m using the local admin acount.

Is this still happening? Including after updated my please.

@george1421 I did thoses manipulations… It didn’t works.

EDIT: wait i’ve forget to run ./installfog.sh again… And its works fine! Tanks

@george1421 In fact i never had to purge the fog directory after removing the legacy client but i’ll try that too. I just remove it and install the new fog service… It works everytime except here. I’m not backing up this image for archive, the idea is to migrate from the 1.2 to the latest version of fog and, by the way, to recapture theses old images (with new fog client, update, etc…) and get better compression of images.

For this PC, the image in the old fog was corrupted. All i can do its taking it from a PC allready in the park. Or remake it…
When i redeploy an old image, update client, and register the host i have no problem.

Last thing, i’ve no idea how the image was created the first time i didn’t worked here at this time. But i see a recovery partition so i think it was an pre-installed windows 7 pro x86