# Device names changed to GUID **URL:** \ **Category:** adam:ONE®\ **Created:** [December 17, 2024, 8:07pm UTC](https://support.adamnet.works/t/device-names-changed-to-guid/1336 "2024-12-17T20:07:25Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![jwol1](https://support.adamnet.works/letter_avatar_proxy/v4/letter/j/77aa72/32.png) [@jwol1](https://support.adamnet.works/u/jwol1)\ **Post date:** [December 17, 2024, 8:07pm UTC](https://support.adamnet.works/t/device-names-changed-to-guid/1336/1 "2024-12-17T20:07:25Z")
I have a large amount of devices that have had their device name changed to a GUID, this is no good. ![Screenshot 2024-12-17 135658](https://support.adamnet.works/uploads/default/original/1X/250e70312827ca3a4a9000c82bd17e606535bec9.png) ---
**Author:** ![atw](https://support.adamnet.works/user_avatar/support.adamnet.works/atw/32/233_2.png) [@atw](https://support.adamnet.works/u/atw)\ **Post date:** [December 17, 2024, 8:08pm UTC](https://support.adamnet.works/t/device-names-changed-to-guid/1336/2 "2024-12-17T20:08:55Z")
@jwol1 could you please run the command `adamone-issue` and send the output file to support@adamnet.works along with a link to this forum thread. ---
**Author:** ![jwol1](https://support.adamnet.works/letter_avatar_proxy/v4/letter/j/77aa72/32.png) [@jwol1](https://support.adamnet.works/u/jwol1)\ **Post date:** [December 17, 2024, 8:27pm UTC](https://support.adamnet.works/t/device-names-changed-to-guid/1336/3 "2024-12-17T20:27:30Z")
I am getting 50x Error. Loads for a few minutes than times out. ---
**Author:** ![atw](https://support.adamnet.works/user_avatar/support.adamnet.works/atw/32/233_2.png) [@atw](https://support.adamnet.works/u/atw)\ **Post date:** [December 18, 2024, 2:59am UTC](https://support.adamnet.works/t/device-names-changed-to-guid/1336/4 "2024-12-18T02:59:26Z")
Are you able to run it from an SSH console prompt? ---
**Author:** ![David\_Hofer](https://support.adamnet.works/user_avatar/support.adamnet.works/david_hofer/32/575_2.png) [@David\_Hofer](https://support.adamnet.works/u/David_Hofer)\ **Post date:** [December 20, 2024, 12:03am UTC](https://support.adamnet.works/t/device-names-changed-to-guid/1336/5 "2024-12-20T00:03:00Z")
I’m seeing this too … ---
**Author:** ![David\_Hofer](https://support.adamnet.works/user_avatar/support.adamnet.works/david_hofer/32/575_2.png) [@David\_Hofer](https://support.adamnet.works/u/David_Hofer)\ **Post date:** [December 20, 2024, 12:03am UTC](https://support.adamnet.works/t/device-names-changed-to-guid/1336/6 "2024-12-20T00:03:47Z")
Version 4.14.0-1 | 14.0-CURRENT ---
**Author:** ![BrightSpark](https://support.adamnet.works/letter_avatar_proxy/v4/letter/b/8edcca/32.png) [@BrightSpark](https://support.adamnet.works/u/BrightSpark)\ **Post date:** [March 1, 2025, 2:02pm UTC](https://support.adamnet.works/t/device-names-changed-to-guid/1336/7 "2025-03-01T14:02:42Z")
@atw Is there any progress on a fix for this issue? It’s makng a complete mess of device lists. I hope it’s a priority for adam:ONE. I’m seeing it on 4.14.1-1 | 15.0-CURRENT You can delete devices but it repopulates again, so doesn’t seem any workaround administrators can make. ---
**Author:** ![BrightSpark](https://support.adamnet.works/letter_avatar_proxy/v4/letter/b/8edcca/32.png) [@BrightSpark](https://support.adamnet.works/u/BrightSpark)\ **Post date:** [April 8, 2025, 6:01pm UTC](https://support.adamnet.works/t/device-names-changed-to-guid/1336/8 "2025-04-08T18:01:40Z")
@atw Any update please? Still seeing the issue. ---
**Author:** ![atw](https://support.adamnet.works/user_avatar/support.adamnet.works/atw/32/233_2.png) [@atw](https://support.adamnet.works/u/atw)\ **Post date:** [April 8, 2025, 7:39pm UTC](https://support.adamnet.works/t/device-names-changed-to-guid/1336/9 "2025-04-08T19:39:26Z")
@BrightSpark it seems that the mDNS function in anmuscle is not working correctly so what I would suggest is adding `disable-sd` to your `anmuscle.conf` configuration file, restart anmuscle and see if that resolves it for you. ---
**Author:** ![BrightSpark](https://support.adamnet.works/letter_avatar_proxy/v4/letter/b/8edcca/32.png) [@BrightSpark](https://support.adamnet.works/u/BrightSpark)\ **Post date:** [April 9, 2025, 9:41am UTC](https://support.adamnet.works/t/device-names-changed-to-guid/1336/10 "2025-04-09T09:41:16Z")
Thanks @atw . Have followed your advice. No change visible in the device list, but have manually deleted GUID type entries to clean up the list somewhat. Just have to hope they don’t re-occur I guess. What do we lose by “disable-sd” (sorry not familiar with the command). Does lack of mDNS mean new device discovery is problematic? Is a fix to whatever underlying issue is causing this being worked on? I presume I’ll need to remove “disable-sd” at that point to restore mDNS? Any more background/general clues on this would be appreciated. I’m sure other users would also appreciate clarity. Thanks! ---
**Author:** ![atw](https://support.adamnet.works/user_avatar/support.adamnet.works/atw/32/233_2.png) [@atw](https://support.adamnet.works/u/atw)\ **Post date:** [April 9, 2025, 1:01pm UTC](https://support.adamnet.works/t/device-names-changed-to-guid/1336/11 "2025-04-09T13:01:20Z")
Yes it won’t automatically clear existing naming issues, but it should prevent that from happening again. For some clarification, the “disable-sd” should disable the use of mDNS for naming and device discovery. It still uses ARP, Netbios, and DHCP leases. But I can’t speak to whether mDNS will be fixed. It might have to be removed altogether.