Rename managed mobile devices, so make the label/name of the device editable
marking Noted, since Daniel has replied
Ben Zell commented
Hello, I was directed to this thread to comment on the device naming issues with Android devices in Intune. I am using a device enrollment manager account to enroll a number of shared test Android devices and the resulting names in Intune are very generic and unhelpful in actually identifying the devices. I'd love to be able to rename them in the console, but the device name property field in Intune is disabled. Please consider enhancing the device naming abilities of Intune so that I can find these devices later in the real world if I need to!
Tyler Deffert commented
Be able to change the name of the iOS device from the Intune Console
Nick Buckley commented
We regularly deploy and help our customers adopt Intune, and regularly the ability to rename a device via the Intune console is requested/required by the customer. There's nothing worse than searching for a device to find several thousand results all called iPhone as an example. This is the same for many Windows devices, manufacturers default computer names have no bearing or relevance to serial/asset number (or any other identifier) so this feature is critical. This is especially fundamental, to customers who are moving away from AD on-prem and moving solely to the cloud (AzureAD) with auto-mdm enrolment after AAD Domain Joining (70% of our customer base are on this journey). From testing, it has also been noted that using the rename option in the Company Portal App, does nothing other than change the name/label in the Company Portal. Neither the device nor Intune admin console pick up this change.
Robert Paterson commented
I can get some ipads to display their custom name, some just say iPad. I've tried resetting the iPad s that just displayed iPad when I had actually named them something different. SOMETIMES then new name will catch, not always. There has to be an exact sequence and timing to get the custom name to display in sccm. Something to do with the time it takes sccm to see the device as Preeclared (DEP from Apple) and the time it takes to be able to set it to Afinity or non-affinity and become Enrolled
Lain Robertson commented
There's two separate issues being misrepresented as one in this thread, but it's the nearest match short of creating a new (and likely pointless given the proximity to this thread) suggestion.
1. There's the concept of renaming the actual device.
2. The concept of renaming the device label in the Intune Company Portal and having that match or at least show up and be searchable (and orderable) in the Intune web management interface(and perhaps SCCM though I'm not sure what the view there is like as we've elected to not go down that path).
My vote is going for number 2 as this has no prerequisites such as requiring the aforementioned Supervised profile (from Daniel) for iOS devices.
To answer the question regarding the trade-off of it not being visible in the native information panels, this is entirely acceptable in the context where we're only trying to make managed device management easier, as it's implicitly true that the managed device is going to have the Company Portal and therefore the ability for the user to see the name.
The primary concern for us is the ability to easily have the user identify their device and the support personnel to find a matching entry in the Intune web management interface. This does not need to be implicitly bound to the hardware device name to be realised.
An additional key point to this is that the attribute needs to be searchable from within the Intune web management interface, and the column should ideally be orderable as well.
From an implementation perspective, you could have the label versus the actual device name being handled separately (i.e. two separate rename points of entry), however, you could also weigh up the benefit of consolidating the process by having the existing rename process change the new label as well as the device (notably looking at iOS here) if it's possible to do so, but simply quietly failing that specific component if it's not. This still allows for the simplification of the administration process as well as the standardisation of where the user should be checking (in the Intune Company Portal).
Karl Julson commented
This actually needs to be available for all devices, not just mobile.
Cory Tomlinson commented
Android and Windows Phones are named user_platform_date regardless of device actual name. Why is iOS behavior different? Ideally this display name should be editable since it's not a unique identifier. Either that or just follow the same conventions as the other platforms.
The other problem is that, in a large enough company, you get some users with inappropriate device names. In BYOD we can't force a user to rename their personal device, and I shouldn't have to have "Muthafu**in iPhone" or My iPhone B*tch in my admin console.
Please fix this design flaw as soon as possible.
This also is an issue with off boarding from the way it works in Intune.
When you disable a user, they disappear from Intune. Since with offboarding the first step is to disable a user, you need to search for the device (this is from Intune support). Since half of my devices are called "iPhone" I can't really search by device name.
You don't need to rename the device, you just need a label. Searching for things in Intune sucks so this would make it a bit better.
So in conclusion, there needs to be the ability to rename based on user name, email address, or something else and to have it done automatically.
Also need the ability to show disabled users when searching. Even a check box for "show disabled users" would be nice.
If we can't rename the device, I have a big problem with device group creation.
We have for example about 70 ipad with the name "Ipad" and when I must insert them in one device group I don't know whois the device owner because all device are called "iPad"
Please insert as soon as possible the ability to rename a device
I also have the same issue with inability to rename a mobile. Sure the friendly name is a good user experience, how about the Admin experience? Admins and service admins are the people who deployed the service and consume that data, its used also by the business. There certainly is need for a rename, or varchar input and or a selection to "use" the friendly name if available.
We have template policies, and certainly template dashboards.
I would certainly like to see customizable dashboards.
I would think you could then be able to run a dashboard reporting based on whatever you needed to see.
I also have some hopes to see updates to functionality like reporting, who did what, and when.. Domain administration allows you to see who made a configuration change, and so many aspects of reporting.. I'd assume Azure space could be "set aside" for Intune reporting, in the same way the Software publisher leverages "billable" space in Azure.
Sandy Wood commented
I too would love to have this capability. I can rename the iPhone itself and the name in our Company Portal app as well. It would be nice if the change could be picked up in an inventory of some sort.
renaming the actual iphone works
Jed Mitchell commented
Has there been any updates on getting some type of unique identifier when dealing with device group? I am currently deployment a ton of iPad devices and as mention previously, they are all named "iPad". I read some forums where people said if you used the company portal app and rename the device with the app, that after 8 days Intune will sync for a full inventory and the new name will reflect in Intune, but I found that to be false.
Please add the rename device option
Kyle Townend commented
Example of why this is such a problem....
I've got 9 iPads enrolled currently in my subscription, all are called: "iPad". I've got one Group called "deploy app X" and another group called "deploy app Y". As there's currently no way to drag a device into a group, or even right click device and select "move to group", we have to go into the Group properties and edit the direct membership rules. When searching for devices on the "direct membership rules" page, I just get a list of 9 devices called iPad with NO way to distinguish between them. Even by suffixing the iPads OS given name with the UPN of the enrolled user would be enough.... for example, iPad_john.firstname.lastname@example.org
Johan Nilsson commented
We have the same problem. This is really frustrating and to be honest im really disappointed that such a basic feature is not working.
Chris Mayo commented
This is one of the biggest issues I have with managing devices through Intune. Tying devices to users or finding them when adding them to the list is hard when DEP means most register as "iPad".
Kyle Townend commented
An editable arbitrary ID column would be ideal, so that corporate internal asset tagging can be applied and can track a phone across multiple enrollments if applicable.
Daniel Gerrity (Intune Product Team) commented
Thanks for the input Ernst.
I would be very interested to hear the community's feedback on a new varchar whose purpose would be a display name, guaranteed-unique at enrollment and editable by the admin. Even though other platforms are not reporting this naming issue, building a single column dedicated to unique identification, could simplify tracking devices.
One drawback of creating a non-native OS column, is that this new display name will not be found on the device's native information screens. This could potentially complicate matching a device in physical possession with the display name in the Admin Console.
This could be mitigated if the new display name included some native identifier by default (e.g. serial number), but it would still be a correlation of differently named attributes (Display Name in Intune = Serial Number in iOS, instead of Device Name in Intune = Device Name in iOS.)
Is such a complication a concern?
I agree in the long run that a one-stop column for unique identification could make a lot of sense, but if being able to match the identifier to a physically possessed device is a concern, we would want to meet that concern as well.
Alternatively, since this seems to be confined to iOS, and Supervision could in principle allow Intune to control the native device name, would it be less disruptive to current practices to solve this for supervised devices? This would leave the unsupervised case unsolved.
Are there opinions about these trade-offs?
Just to make things clear...It's not a feature request to change the real iOS system device name. We wish to have just one additional varchar column in the Windows Intune database ( I assume SQL Server) called e.g. "mobileDeviceDisplayName". Having twenty years of programming and database modeling experience, I know this should be relatively easy to implement.