iPAD not profiling

[cdannenberg]

iPAD, iPhones and Apple Devices are all being profiled as Apple Devices. There seems no way to distinguish iPads from iPhones.

The profiler condition: DHCP Parameter-Request-List will not work since the values are the same for iPads and iPhones.

The OUI is also the same. How can iPAD's be identified to profile properly and apply authorization rule?

[Jason Kunst]

There are a few ways to determine the type of device

For iOS devices we rely on the web browser user agent string

This can be obtained using Cisco wireless controller device sensor profiling HTTP traffic or the device can be redirected to a guest portal or posture portal

Another way is if the device his iPhone or iPad in its host name

These are the basic and recommended ways to be able to determine the type of iOS device

[cdannenberg]

Thanks Jason,

From what I have seen, the web browser user agent string is the same for iPads and iPhones therefore we can't differentiate between the two.

The hostname is a great, easy fix if we have control over the devices. But we do not.

[Craig Hyps · Accepted solution]

DHCP PRL is useful to distinguish the device as an iOS device which can be iPad, iPhone, or iPad.  As called out, user agent may help but it is correct that misleading user agents can be seen across different endpoints.  In many ways, the iOS devices are the same device--running same code base, but different form factors.  The hostname option is based on default naming so don't necessarily need to be under your control.  If control is the requirement, then recommend explicit auth and DM/MDM/EMM integration!   Profiling is primarily a passive classification independent of explicit auth or agent present.