@aknisly said in Linux FOG Client, Hostname Changer not working:

If I hadn’t been able to get what I wanted with that, I’d be happy to help with the fog-client and the HostnameChanger module, but as it is, unfortunately, I’m pressed to move on to other priorities.

Thanks for being open and honest. Good you were not afronted by my last reply.

I would be happy to make some notes in the wiki (which is still the first place I check) if that is an option. Apparently self-registering an account is disabled?

We work on updating and moving all the contents from the wiki to https://docs.fogproject.org and you are very welcome to help us. Please send me a private message with your github account name and we’ll permit you to the fog-docs repo.

@ngriffith29 With FOG you usually register hosts (at least you need to if you want FOG to rename them) and there you define the hostname it will use after deployment. So it’s just up to you to name the hosts accordingly.

@jtappen From what you wrote it seems like you are on the right track with this - Active Directory Defaults in the FOG settings should be the was to go.

So which way do you actually register your clients?

Our Fog is on versoin 1.5.6

This is not the latest version. I cannot say for sure we have found und fixed in the latest but if we find this to be a bug I need you to update to the very latest version.

@lukebarone Seems it wasn’t fixed in rc-10, tom says it’s fixed in 11 though, follow here:
https://forums.fogproject.org/topic/8558/reboot-host-on-hostname-changes-and-ad-changes-even-if-users-are-logged-in-button-not-saving