FileWave Alliance

The Official Community Forum
  • Page:
  • 1

TOPIC: IOS Client Naming

IOS Client Naming 15 Jan 2016 16:05 #2042

  • Robert Rhyne
  • Robert Rhyne's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 25
  • Karma: 2
  • Thank you received: 0
During the webinar about FW 10 improvements, y'all mentioned an improved push of FW Client Names to IOS devices. I asked if that meant we'd be able to upload a file to map ser# to client name and the response was yes. I'm not finding how to manage that...

IOS Client Naming 19 Jan 2016 19:30 #2045

  • Robert Rhyne
  • Robert Rhyne's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 25
  • Karma: 2
  • Thank you received: 0
Have I overlooked something new or was this not correct?

IOS Client Naming 05 Feb 2016 13:01 #2177

  • Derek Deckard
  • Derek Deckard's Avatar
  • Offline
  • FileWave Staff
  • FileWave Staff
  • Posts: 33
  • Thank you received: 6
Hello Robert,

I don't believe you have overlooked something. I think there may have been some confusion with your question. Here is the improvement to syncing the FileWave Client name to the Device name during DEP enrollment.

iOS Device name is changed to the FileWave Client Name for DEP Devices during enrollment

The way this worked in the past was the FileWave Client would be named based off the settings you chose in the DEP Profile but the device's name would remain iPad. Now the device is renamed to match the FileWave Client during the DEP enrollment process. You can then send a Restriction Profile to the device locking the name so Users can not change it.

I believe what you are asking is for a way to upload a text file for iOS devices in Clients, New Client, Text File. This is not possible because of how the iOS devices communicate with the MDM.

Please let me know if I have misunderstood and we can discuss it further.

Regards,
Derek

IOS Client Naming 27 May 2016 12:59 #2311

  • Justin Neitzey
  • Justin Neitzey's Avatar
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 20
  • Thank you received: 0
Teachers are increasingly asking for devices to be named 1-25 so they can AirDrop things to iPads. Under the current DEP naming conventions, there is no auto increment naming feature. Do you all recommend just naming devices manually? I'm able to do that since I scan everything into a spreadsheet and can see the serial numbers.

IOS Client Naming 27 May 2016 13:12 #2312

  • Robert Rhyne
  • Robert Rhyne's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 25
  • Karma: 2
  • Thank you received: 0
My greatest need in naming is for either the Client Name or the Device Name to be something meaningful so it can be used in queries and smart groups. So, what I'm doing right now is to use a macro created with Keyboard Maestro to grab my spreadsheet data and write a new Filewave Client Name. It works pretty well...the last time I ran it, I did about 900 in about an hour or so.

That solves my problem for searches as I set up queries and smart groups largely based on FW Client Name. Then, I send a request to teachers to rename their Device Name to the same name as my Filewave Client Name. Most comply and most even type it in correctly... :P

IOS Client Naming 27 May 2016 13:31 #2313

  • Robert Rhyne
  • Robert Rhyne's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 25
  • Karma: 2
  • Thank you received: 0
and, in reaction to Derek's post above about the limitations of naming due to device communications with the MDM, I can understand how that limits pushing a name of choice to the device name.

but, I don't understand why we can't have a text file that maps serial number (unchangeable) to Filewave Client Name (which doesn't get pushed to the device and is internal only). and, if the MDM still inhibits that, then it would be of some help to be able to upload a file that batch maps current FW Client Name and changes it to a new FW Client Name.

IOS Client Naming 30 May 2016 15:08 #2319

  • Pierre-Nicolas Rigal
  • Pierre-Nicolas Rigal's Avatar
  • Offline
  • Administrator
  • Administrator
  • Posts: 81
  • Karma: 12
  • Thank you received: 30
Actually both situations are possible (renaming internal FileWave name, and pushing, for supervised devices, the name change) - it's just a matter of priority / implementation.

Now that FileWave 11.0 has a unique database, it's a bit easier for us to implement this kind of features, this is why is was always postponed. I added a link to this topic to out feature ticket.

As a general note: we sometimes answer this kind of requests with a script you would be able to run (I'd not be surprised if a script doing what you need is not already in our support script repository). It's great because it can be done quickly and it helps you moving forward, but on the other hand it's not ideal:
- our answer should not be a script, but something integrated in the product
- if you are happy with the script, you won't complain and ask for the feature. So the priority will be lower and the feature will never be done.
- we're likely not aware of all scripts outside ; and we may break the script because we change some internals.

I'd suggest, as we said during Alliance conference, to make sure support / sales knows this is an important issue for you. Not that we don't talk internally or that the alliance forum is not the right place to discuss features, but as we have a limited number of things we can do (unfortunately), having most of our feature request coming from the same channel makes it easier for us - a quicker for you to get it done.
  • Page:
  • 1