Jump to content

ESMC computer name mismatch (hostname vs FQDN)


veehexx
 Share

Recommended Posts

We upgraded to ESMC a few months ago and used domain connected windows machines as the first wave of migration. Seems to work fine.

We use the ADSync server task, which imports all objects in FQDN format - windows and mac.

We have recently added our mac devices to the new ESMC console. These machines are added to AD. The ADSync import shows them as FQDN. However when a mac reports, it remains stuck in the Lost & Found group with just their hostname.

We have another server task that should rename synced computer names using the Rename Based on: 'Computer FQDN'. also tried the 'computer name' option but that doesnt seem to work either.

It appears ESMC doesn't rename mac clients and considers hostname and FQDN as two separate machines.

A side problem which might be related is if we rename a machine, the old name remains visable in ESMC so with the above issue we could end up with potentially 4 eset objects for 1 machine. I've not looked into this issue yet so could be something i've not done.

how can we resolve this?

Link to comment
Share on other sites

  • ESET Staff

Hello,

If you inspect details for those mac machines, what is reported as their FQDN? Is there the correct FQDN name? As the "rename computers" task, should correctly change the name of the device, and then the AD sync task with collision handling set to move, should fix the duplicates issues. However, it looks that the FQDN is not correctly reported from the mac devices. Maybe @MartinK might be able to provide more insights into this. 

Link to comment
Share on other sites

  • ESET Staff

Since ESET Management Agent 7.0 was release, hostname and FQDN is fetched using mechanisms similar to command line call:

sysctl kern.hostname

so it has to contain FQDN in order to show it in ESMC. Please check what returns this command on problematic devices, it is cruticla it reports FQDN, so that it can be reported to ESMC and used for renaming or pairing devices synchronized from domain.

Link to comment
Share on other sites

both ESMC and 'sysctl kern.hostname' show hostname format only - neither have FQDN set.

the way you've both responded, i guess we need to change something on the mac side so it uses FQDN as hostname?

Link to comment
Share on other sites

  • ESET Staff
9 hours ago, veehexx said:

both ESMC and 'sysctl kern.hostname' show hostname format only - neither have FQDN set.

the way you've both responded, i guess we need to change something on the mac side so it uses FQDN as hostname?

Yes please verify that hostname of macOS machine is correctly set. Otherwise AGENT won't be able to report FQDN name to ESMC, and thus ESMC won't be able to pair device with FQDN entries in domain.

Recently we were solving similar issue as support ticket, and customer used command:

sudo scutil --set HostName devicename.example.com

to correctly set FQDN name on macOS device.

Link to comment
Share on other sites

 

14 hours ago, MartinK said:

Yes please verify that hostname of macOS machine is correctly set. Otherwise AGENT won't be able to report FQDN name to ESMC, and thus ESMC won't be able to pair device with FQDN entries in domain.

Recently we were solving similar issue as support ticket, and customer used command:


sudo scutil --set HostName devicename.example.com

to correctly set FQDN name on macOS device.

that's got it! once set and waited for the Rename Computer server task to run, ESMC now works as expected.

Thanks for the info. We just need to push the name change out to our existing macs via jamf.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...