@AUTH-IT-Center the hostname changer is enabled, yes. The hosts are created via full registration and inventory. Using the group-based workaround provided by @Tom-Elliott works so far.

I think there are two problems here, the fog client detects the lightdm linux user and stops and the settings don’t get applied to clients from FOG Configuration -> FOG Settings -> Active Directory defaults.

Note that we don’t join the clients to our domain, we only change their hostname.

@Tom-Elliott but why is it not enforced despite that setting being enabled?

@Tom-Elliott thanks for the reply, but there is no “FOG_ENFORCE_HOST_CHANGES” in FOG Configuration -> FOG Settings, only “ENFORCE HOST CHANGES” under FOG Configuration -> FOG Settings -> Active Directory Defaults and that one is already ticked.
Either that or I’m just blind.

We use FOG to deploy linux machines. After the image has been deployed, the FOG Service needs to change the hostname.
This works perfectly fine on windows, on linux the lightdm user gets detected:

------------------------------------------------------------------------------
----------------------------------UserTracker---------------------------------
------------------------------------------------------------------------------
 04.10.2024 13:17:29 Client-Info Client Version: 0.13.0
 04.10.2024 13:17:29 Client-Info Client OS:      Linux
 04.10.2024 13:17:29 Client-Info Server Version: 1.5.10
 04.10.2024 13:17:29 Middleware::Response Success
 04.10.2024 13:17:29 Middleware::Communication URL: https://fog.lan/fog/service/usertracking.report.php?action=login&user=tcimagehost\lightdm&mac=<MAC>&newService&json

this causes the hostname changer module to not change the hostname:

------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
 04.10.2024 13:15:54 Client-Info Client Version: 0.13.0
 04.10.2024 13:15:54 Client-Info Client OS:      Linux
 04.10.2024 13:15:54 Client-Info Server Version: 1.5.10
 04.10.2024 13:15:54 Middleware::Response Success
 04.10.2024 13:15:54 HostnameChanger Users still logged in and enforce is disabled, delaying any further actions
------------------------------------------------------------------------------

In “FOG Configuration -> FOG Settings -> Active Directory Defaults” the checkmark is set by “ENFORCE HOST CHANGES”.

In “FOG Configuration -> FOG Settings -> FOG Client - Task Reboot” the checkmarks are set by “Client Taskreboot enabled” and “Task Force Reboot”.

Going to “Hosts -> <Host> -> Active Directory” and enabling “Name Change/AD Join Forced reboot?” fixes the issue, but I don’t know how to force this for all hosts by default, especially including new hosts.

FOG Version 1.5.10
FOG Client Version 0.13.0

@Bhav Do you use FOG for DHCP and if not, did you follow the documentation when setting up your DHCP Servers?
IIRC you need to point your DHCP server to bios and uefi bootfiles respectively.

Hi all, FOG has been wonderful in its usefulness at our main location, so we decided to establish nodes in other locations as well.
Following the documentation, I created new ubuntu servers, ran the installer, selected storage node and added them to the webinterface of the main fog server.
Then I created storage groups, added the respective nodes to their group and checked “master node”.
After that, I went to “images” and added the new storage groups to the images that I want to have synced, created a cron job on the main server to schedule when syncing is supposed to happen and waited for some of the images to be sent to the new nodes.
After that, I configured the windows DHCP servers in the other locations to point to the main FOG server.

From what I understand, new clients booting PXE in the other locations will be directed to the main FOG server, but what I can’t seem to find exact information on is how the deployment of images to new clients will be handled.
When a new client boots PXE from one of the seperate locations, receives the bootfile from the main FOG server and a technician selects “perform full registration and inventory”, then how does FOG decide which server will send the image? Will the new storage node be used automatically, or will FOG send the image from the main server in our main location?
I understand that captures will always go to the master of their main storage group, but what about deployments?