@lambo Well done. Looking through your notes and logs I find it very awkward that we have different results for tests that should end up the same! The fog-client simply calls official MS API to do rename, AD join/leave and so on. While it’s still possible that it’s something we do wrong in the code I find it very strange that it would work one time and fail the next few tries.
What I found in the fog-client logs is a few unknown return codes:
FOG Test 1.log: 2/25/2021 9:10:45 AM HostnameChanger Unknown Return Code: 1791
FOG Test 5.log: 2/26/2021 10:19:55 AM HostnameChanger Unknown Return Code: 1791
FOG Test 7.log: 2/26/2021 1:34:39 PM HostnameChanger Unknown Return Code: 1791
FOG Test 8.log: 2/26/2021 2:26:16 PM HostnameChanger Unknown Return Code: 1332
FOG Test 8.log: 2/26/2021 2:28:48 PM HostnameChanger Unknown Return Code: 1332
FOG Test 9.log: 2/26/2021 3:49:57 PM HostnameChanger Unknown Return Code: 1791
1791: A remote procedure call is already in progress for this thread. (reference)
1332: No mapping between account names and security IDs was done. (reference)
Possibly you have some other software interfering with the fog-client? Do you have other tools installed that would run straight after the client comes up after imaging?
Did you find anything obvious in the event logs on the client or the AD server when it fails to create the machine account?
As a side note: You still have the 0.11.19 fog-client installed. Unfortunately the CA certificate shipped with that binary ran out last year and so the auto updater can’t pull up to the 0.12.0 version coming with FOG 1.5.9. It downloads the SmartInstaller but cannot verify the signature and therefore cannot install it. So at some point you’ll need to update your base image with the newer fog-client.
Though I don’t think 0.12.0 will make much of a change in this scenario you are facing here. There have not been updates to the HostnameChanger module since 0.11.19.