That would be a nice feature. Sign me up! ... View more

Unfortunately Meraki makes use of UUID version 4 which generates a random UUID... ... View more

I modified / pasted the code here -> https://pastebin.com/iU2ssCVD   It looks like pasting to pastebin changes the formatting somewhat. If you're unsure of anything let me know.   The script is written in Powershell so some adaptation would be required if not using Windows.   Just noticed a mistake here: function api_get($key, $url) { $headers = New-Object "System.Collections.Generic.Dictionary[[String],[String]]" $headers.Add("X-Cisco-Meraki-API-Key", "$apikey")   Just replace ($key, $url) with ($apikey, $url) it'll likely still work without this change   ... View more

Happy to, I'll just need to add comments / remove specific info to us and will figure out where to share it 🙂   ... View more

We only have a workaround which is to run an API based script that looks for UUIDs and matches the IP with the hostname in DHCP then updates the Description in Meraki for that client.   Meraki were quite firm that unless you manually set your clients (>1000 for us) it'll be in the UUID format...   Doesn't hurt to try though!   ... View more

Hey, this is the response I received back for my support case: The development team got back and indicated that the clients names were supposedly superseded by mDNS names if they are not manually assigned a name.  For your clients that appearing as UUID/GUIDs, have you manually assigned names to them? If not, then it is expected. Cisco Meraki Technical Support   ^ This isn't good news, looks like i'll be needing to write an API/Script to manually update GUIDs and monitor for host name changes 😞 ... View more

FYI when submitting a case for this:   Thank you for contacting Cisco Meraki Support. This problem has been reported. The development team is actively working on it. I will update you as soon as possible after the development update.   ... View more