We are using mostly an on premise version of the MDM server, but the Sophos Central is showing the same problem. Don't get any answers from the support desk :-(
Normaly we are enrolling our Samsungs with KME, this is resulting in a device name like "Samsung KME 351231231231234" (the IMEI). But the last couple of months. All (and ONLY) the newer devices like A40, A41 A50, S series are getting devicenames like Samsung KME c9268dd6850d895f. According the Device properties this is the Android-ID and the Build Serial at the same time...Also the IMEI nr or Simcard serial are knowhere to be found in the Device properties.
I also tried the "add device wizard" (scan QR code etc) for an manual erollment of an A40 on my on premise AND in Sophos central server, to rule out if it was an Samsung Knox thing, with the same result.
As an bonus: the Android_ID is not always the same for 1 device. I have seen a user who tried 5x an enrollment, resulting in 5 different names for 1 device!
It would feel logical to think about a Sophos<->Android 10 problem. But the Xcover4s with android 10 is not affected.
Anyone an idea? I feel like I have tried every angle by now.
I think I found my own solution, at least for the KME part. I have not tested how QR enrollment handles with Android Enterprise.
We where stille running on the old Android device administrator mode. “If it ain’t broken, don’t fix it you know..”. But now i’m testing with the Android Enterprise settings en KME enrollement and voila, See screendump same device in Device mode en Android Enterprise fully managed mode.