1.6.0.158 Unable to join machine to he domain and change Hostname
-
Hi,
I am unable to join a machine to the Active Directory domain and change its NetBIOS hostname after deploying an image.
Here is my current workflow and status:
• Master image creation (including fog-client 0.1.24), Sysprep, and image capture on FOG: OK
• Image deployment to target machine: OK
• Domain join and NetBIOS name change: Failed (NOK)In the file fog-agent.log:
directory rejoin: could not ask the server wich features it offers; the agent aks again later. Check that the server is reachable generated a new key for this machine's identity enrolled as host 252, certificate valid until 2027-11-12 15:35:26 service started directory rejoin: could not ask the server wich features it offers; the agent aks again later. Check that the server is reachable service restart policy was missing and has been set; this service can now come back on its own after a self-update facts: sending inventory=true software=87 directory=true printers=2 network=1 server refused this certificate (0s); keeping it and retrying facts: sending inventory=true software=88 directory=true printers=2 network=1 server refused this certificate (5m1s); keeping it and retrying facts: sending inventory=true software=88 directory=true printers=2 network=1 server refused this certificate (10m1s); keeping it and retrying facts: sending inventory=true software=88 directory=true printers=2 network=1 server refused this certificate (15m1s); keeping it and retrying service stoppedIn the Host Agent Activity
When | Event | Detail | Outcome |
2026-11-16 16:53 | Agent.enroll | issued via token, key 02… | allowed
2026-11-11 16:33 | Agent.enroll | issued via admin, key 3f… | allowed
2026-11-16 16:10 | Agent.enroll | waiting: unknown-host | allowedDo you know where I could look for answers?
Thx -
@Yoh Thanks, that confirms it. The agent needs HTTPS for every call after enrollment, because the server identifies each machine by the agent’s certificate. Plain HTTP cannot carry that certificate.
Your server can stay on HTTP for imaging. A FOG 1.6 install normally serves HTTPS as well. The redirect from HTTP to HTTPS is optional. First, open
https://<your-server>/fog/managementin a browser on the master machine. It must load.Then reinstall the agent on the master image with the
https://address:msiexec /i fog-agent-x64.msi /qn SERVER=https://<your-server>/fog TOKEN=<your-token> /l*v C:\fog-agent-install.logThen run Sysprep and capture the image again. On machines you already deployed, run the same command.
The next agent release also says this in its log. An
http://address will be named as the cause. -
@Yoh The agent enrolls, but the server then rejects every call that uses the agent’s certificate. The domain join and the rename never start, because they need those calls.
The most likely cause is a server address that starts with
http://. The certificate travels only over HTTPS. Over plain HTTP the server never sees it, so it rejects the call. The first line of your log points the same way: the agent checks the server’s features only over HTTPS.Please post the
server_urlline from this file on the deployed machine:C:\ProgramData\FOG\agent\config.jsonIf it starts with
http://, reinstall the agent with thehttps://address of the server. -
@Tom-Elliott Thank you for your reply, however my FOG server is running over HTTP.
-
@Yoh Thanks, that confirms it. The agent needs HTTPS for every call after enrollment, because the server identifies each machine by the agent’s certificate. Plain HTTP cannot carry that certificate.
Your server can stay on HTTP for imaging. A FOG 1.6 install normally serves HTTPS as well. The redirect from HTTP to HTTPS is optional. First, open
https://<your-server>/fog/managementin a browser on the master machine. It must load.Then reinstall the agent on the master image with the
https://address:msiexec /i fog-agent-x64.msi /qn SERVER=https://<your-server>/fog TOKEN=<your-token> /l*v C:\fog-agent-install.logThen run Sysprep and capture the image again. On machines you already deployed, run the same command.
The next agent release also says this in its log. An
http://address will be named as the cause. -
@Tom-Elliott So that was all it took, thank you very much, the issue is resolved.
-
T Tom Elliott has marked this topic as solved