We operate a fairly large Meraki network, 334 MX's and growing.  We have around 10k workstations, all built using Intune to the same standard/policies.   This issue is very random, and very frustrating.  Some devices appear fine, majority of Windows devices do not.  I have raised a ticket with Meraki, and they confirmed to me that Meraki detects and sees the 3 fields: Mdns_name Netbios_name Dhcp_name The Netbios and the Dhcp fields contain the correct hostname information, but Meraki still uses the Mdns field to populate the client description field.   My argument to Meraki is that if the info is available, then allow us the customer to see it in the GUI.           ... View more

mDNS introduces several security risks so my Cyber Security Team won't allow it. ... View more

Meraki really need to listen to their customers on this issue.  It is a major frustration and causes huge headaches when trying to manage the estate.    We use DHCP on the Meraki MX, i can see the NETBIOS name in the DHCP requests ..... but then Meraki assigns an MDNS name ..... why do that? what is the point!   Come on Meraki ..... listen to your customers! ... View more