Topics created by dpullin

@dpullin said in FOG service invalid host:

The issue seems to be when the name in FOG UI doesn’t match the hostname of the machine (because I changed it in the UI after the fact) - this has started to crop up on other machines due to user error (techs giving machines the wrong names before sending them out the door) - then we try to fix it by changing the name in the UI, then it gives the “invalid host” error as described above.

I can’t seem to replicate the issue as described using the following steps - please verify if you do things a different way:

Check fog.log to see communication works fine Make sure AD credentials are set and correct for the test host in the FOG web UI Change Host Name in FOG web UI Wait for machine to reboot Check hostname (Windows GUI as well as CMD -> hostname) and fog.log (see below). ------------------------------------------------------------------------------ --------------------------------HostnameChanger------------------------------- ------------------------------------------------------------------------------ 4/16/2022 7:06:09 AM Client-Info Client Version: 0.12.0 4/16/2022 7:06:09 AM Client-Info Client OS: Windows 4/16/2022 7:06:09 AM Client-Info Server Version: 1.5.9.139 4/16/2022 7:06:09 AM Middleware::Response Success 4/16/2022 7:06:09 AM HostnameChanger Checking Hostname 4/16/2022 7:06:09 AM HostnameChanger Renaming host to Newhostname 4/16/2022 7:06:09 AM HostnameChanger Renaming host inside existing domain binding 4/16/2022 7:06:09 AM HostnameChanger Success, code = 0 4/16/2022 7:06:09 AM Power Creating shutdown command in 60 seconds 4/16/2022 7:06:09 AM Bus Emmiting message on channel: Power ------------------------------------------------------------------------------

Works fine in my test setup. Do you use plugins or other special things in your FOG setup? Other than that I con only imagine is has to do with the wireless MAC you seem to be using. Is this the primary MAC?