<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[1.6.0.158 Unable to join machine to he domain and change Hostname]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">I am unable to join a machine to the Active Directory domain and change its NetBIOS hostname after deploying an image.<br />
Here is my current workflow and status:<br />
• Master image creation (including fog-client 0.1.24), Sysprep, and image capture on FOG: OK<br />
• Image deployment to target machine: OK<br />
• Domain join and NetBIOS name change: Failed (NOK)</p>
<p dir="auto">In the file fog-agent.log:</p>
<pre><code>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 stopped
</code></pre>
<p dir="auto">In the Host Agent Activity<br />
When                    | Event            |  Detail | Outcome |<br />
2026-11-16 16:53 | Agent.enroll | issued via token, key 02… | allowed<br />
2026-11-11 16:33 | Agent.enroll | issued via admin, key 3f… | allowed<br />
2026-11-16 16:10 | Agent.enroll | waiting: unknown-host | allowed</p>
<p dir="auto">Do you know where I could look for answers?<br />
Thx</p>
]]></description><link>http://forums.fogproject.org/topic/18320/1-6-0-158-unable-to-join-machine-to-he-domain-and-change-hostname</link><generator>RSS for Node</generator><lastBuildDate>Tue, 17 Nov 2026 21:41:14 GMT</lastBuildDate><atom:link href="http://forums.fogproject.org/topic/18320.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 17 Nov 2026 12:31:06 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to 1.6.0.158 Unable to join machine to he domain and change Hostname on Tue, 17 Nov 2026 12:48:18 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="http://forums.fogproject.org/uid/49814">@Yoh</a> 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.</p>
<p dir="auto">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 <code>https://&lt;your-server&gt;/fog/management</code> in a browser on the master machine. It must load.</p>
<p dir="auto">Then reinstall the agent on the master image with the <code>https://</code> address:</p>
<pre><code>msiexec /i fog-agent-x64.msi /qn SERVER=https://&lt;your-server&gt;/fog TOKEN=&lt;your-token&gt; /l*v C:\fog-agent-install.log
</code></pre>
<p dir="auto">Then run Sysprep and capture the image again. On machines you already deployed, run the same command.</p>
<p dir="auto">The next agent release also says this in its log. An <code>http://</code> address will be named as the cause.</p>
]]></description><link>http://forums.fogproject.org/post/159042</link><guid isPermaLink="true">http://forums.fogproject.org/post/159042</guid><dc:creator><![CDATA[Tom Elliott]]></dc:creator><pubDate>Tue, 17 Nov 2026 12:48:18 GMT</pubDate></item><item><title><![CDATA[Reply to 1.6.0.158 Unable to join machine to he domain and change Hostname on Tue, 17 Nov 2026 13:18:30 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="http://forums.fogproject.org/uid/7217">@Tom-Elliott</a> So that was all it took, thank you very much, the issue is resolved.</p>
]]></description><link>http://forums.fogproject.org/post/159047</link><guid isPermaLink="true">http://forums.fogproject.org/post/159047</guid><dc:creator><![CDATA[Yoh]]></dc:creator><pubDate>Tue, 17 Nov 2026 13:18:30 GMT</pubDate></item><item><title><![CDATA[Reply to 1.6.0.158 Unable to join machine to he domain and change Hostname on Tue, 17 Nov 2026 12:48:18 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="http://forums.fogproject.org/uid/49814">@Yoh</a> 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.</p>
<p dir="auto">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 <code>https://&lt;your-server&gt;/fog/management</code> in a browser on the master machine. It must load.</p>
<p dir="auto">Then reinstall the agent on the master image with the <code>https://</code> address:</p>
<pre><code>msiexec /i fog-agent-x64.msi /qn SERVER=https://&lt;your-server&gt;/fog TOKEN=&lt;your-token&gt; /l*v C:\fog-agent-install.log
</code></pre>
<p dir="auto">Then run Sysprep and capture the image again. On machines you already deployed, run the same command.</p>
<p dir="auto">The next agent release also says this in its log. An <code>http://</code> address will be named as the cause.</p>
]]></description><link>http://forums.fogproject.org/post/159042</link><guid isPermaLink="true">http://forums.fogproject.org/post/159042</guid><dc:creator><![CDATA[Tom Elliott]]></dc:creator><pubDate>Tue, 17 Nov 2026 12:48:18 GMT</pubDate></item><item><title><![CDATA[Reply to 1.6.0.158 Unable to join machine to he domain and change Hostname on Tue, 17 Nov 2026 12:37:38 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="http://forums.fogproject.org/uid/7217">@Tom-Elliott</a> Thank you for your reply, however my FOG server is running over HTTP.</p>
]]></description><link>http://forums.fogproject.org/post/159041</link><guid isPermaLink="true">http://forums.fogproject.org/post/159041</guid><dc:creator><![CDATA[Yoh]]></dc:creator><pubDate>Tue, 17 Nov 2026 12:37:38 GMT</pubDate></item><item><title><![CDATA[Reply to 1.6.0.158 Unable to join machine to he domain and change Hostname on Tue, 17 Nov 2026 12:34:52 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="http://forums.fogproject.org/uid/49814">@Yoh</a> 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.</p>
<p dir="auto">The most likely cause is a server address that starts with <code>http://</code>. 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.</p>
<p dir="auto">Please post the <code>server_url</code> line from this file on the deployed machine:</p>
<pre><code>C:\ProgramData\FOG\agent\config.json
</code></pre>
<p dir="auto">If it starts with <code>http://</code>, reinstall the agent with the <code>https://</code> address of the server.</p>
]]></description><link>http://forums.fogproject.org/post/159040</link><guid isPermaLink="true">http://forums.fogproject.org/post/159040</guid><dc:creator><![CDATA[Tom Elliott]]></dc:creator><pubDate>Tue, 17 Nov 2026 12:34:52 GMT</pubDate></item></channel></rss>