City attorneys still use native mail on some phones. The CIO wants adoption numbers for Workspace ONE Boxer versus native mail to justify Boxer licensing. What should the operator produce?
Select an answer to reveal the explanation.
Short Explanation
Licensing questions are headcount reports, not VDI attach logs. Intelligence can show which phones actually run Boxer versus native mail.
Full Explanation
When the CIO needs Boxer versus native mail adoption to justify licensing for city attorneys, the operator should produce a Workspace ONE Intelligence application-data report that compares those clients. Intelligence application-data reporting is the associate-level path for fleet app adoption evidence across enrolled phones. App Volumes Manager attach counts fail by concept because they measure Windows package attaches on Horizon desktops, not mobile mail-client mix. Horizon Console desktop-pool entitlements describe VDI access, not whether phones run Boxer or native mail. NSX overlay metrics describe network overlays and cannot be relabeled as Boxer adoption. Exam caveat: include both managed Boxer and native clients in the report window so Finance sees residual native use rather than an incomplete success story. Operational check: generate an Intelligence application-data report scoped to attorney devices for the agreed date range, export Boxer versus native counts, attach the file to the licensing ticket, and note users still on native mail for migration coaching. In municipal EUC operations, record the console path and the rejected alternatives in the change ticket so the next on-call technician repeats the same evidence-first workflow for city staff.