That would be fantastic.  The test PC i am working with has not updated in the dashboard since setting the flags in the browsers 3 days ago.  So the good news is that seems to stop the problem.  Bad news is nothing is replacing the bad entry.    I do know that installing Bonjour will update the name correctly, but it hasn't seen an update since 2015 and Windows complains about the unsigned DLLs.  Not something i want our users dealing with.  I have tried forcing DNSCache to broadcast with restarts, DHCP renewals, and reboots, but either it isn't working, or Meraki is ignoring it.    My next thought is to just disable mDNS company wide and let Meraki use NETBIOS.  I assume some action will be needed to update using that too though, possibly removing the client from the dashboard to let it redetect? ... View more

I just wanted to point out that the PowerShell command here does not provide a complete list.  It only shows one PID per unique "Local Address".  So if you have 2 different applications using the same port on 0.0.0.0, only one will show with this command.     It is not as clean, but netstat will get you everything.  There is probably some parsing that could be done to ONLY display the port you want, but i haven't taken the time.   Examples run on the same system at the same time:     Get-NetUDPEndpoint -LocalPort 5353 | Select-Object LocalAddress,LocalPort,OwningProcess,@{ Name="ProcessName"; Expression={((Get-Process -Id $_.OwningProcess).Name )} }   LocalAddress LocalPort OwningProcess ProcessName ------------ --------- ------------- ----------- :: 5353 2340 svchost 0.0.0.0 5353 2340 svchost   ------VS------ netstat -nabqp UDP   Active Connections Proto   Local Address   Foreign Address   State <SNIP> UDP 0.0.0.0:5353 *:* [chrome.exe] UDP 0.0.0.0:5353 *:* Dnscache [svchost.exe] UDP 0.0.0.0:5353 *:* [chrome.exe] UDP 0.0.0.0:5353 *:* [msedge.exe] UDP 0.0.0.0:5353 *:* [msedge.exe] <SNIP>   ... View more

We recently starting digging into this issue on out network.  My colleague called Meraki support about it and did not make any progress.    I can confirm that it is definitely a browser issue.  Hosts that worked fine immediately updated to the GUID style name after just opening a browser.  Repeated visits to WebRTC update the name on the dashboard each time.   The mitigation using the flag in the browser seems to have worked, but my question is how do we go about restoring the name in the dashboard?  Is it just a matter of time before either the built in mDNS overwrites the GUID entry? Or is there a way to force it?   My request for Meraki regarding this would be to allow customers to change the order of the services that pull the names to suit their specific needs.  ... View more