I don't think there is a solution to this, other then Meraki switching this off, or giving us a switch which allows us to disable it.
This is caused by a "privacy" feature of Edge and Chrome. You might have noticed that with some computers this does not happen. Well, those are not running any of these browsers. It would be easy, let us switch that off. If I remember well, for Edge, there is a registry setting. But for Chrome, you have to do it on the GUI. Which means it can be done, but has to be done one by one. It does not scale. Can not be rolled out to thousands of machines.
Some people suggest to pull the MAC address from some other source (Intune, or any other asset tracking db) and rename the computers. This could work..., in certain cases but not all. We use USB-C docking stations, so the MAC belongs to the docking station, not the computer. So practically on the wireless it would work, but not on the wired. (We are using 802.1X on the wireless, so there is a username shown for those, so this issues with wireless is less relevant for us.)
We could block mDNS on the switches. Well, that would solve the issue, but cause some other issues with screen sharing, printer discovery, etc.
We could implement 802.1X on wired and wireless, which would show either username or computer name. This would actually be one of the closest to being able to call it a solution. Still, for the docking stations, in certain situations it shows a name which is not the right one.
I am out of ideas. Anyone?
I find it incredible stupid that there is super nice dashboard and then a _feature_ which would just need to be disabled (vs the lack of it) makes it impossible to identify a client.
Andras
