Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Device Management topic
No spam. Unsubscribe anytime.
Staff report MDM problems on district phones; 0‑touch profile left in place disrupted email setup
Summary
Speakers said the district's mobile device management (MDM) is only partially configured, with a 0‑touch enrollment profile left enabled that blocked adding work email; they deleted a device profile from the portal and plan to collect IMEI/SIM details and reconfigure phones.
During the same session participants turned from cameras to district mobile devices, describing a partially configured mobile‑device management setup and a 0‑touch enrollment profile that had prevented staff from adding work email to a phone.
Speaker 3 said the MDM had been "in limbo for a couple of years" and that a previous test of 0‑touch enrollment by a former staffer ("Dave") had never been turned off, which caused problems when a staff member tried to add a work account. "It never turned it back off...we had to delete it out there because I literally couldn't even add my work email to it," Speaker 3 said.
The participants described a practical troubleshooting sequence: confirming whether the device remained listed in the 0‑touch portal (partner.android.xerot.com/0touch), removing stale profiles, and checking whether carriers such as Verizon retained their own provisioning. They noted an instance where an employee's personal Google and Facebook accounts had to be reset as part of the recovery process. Speakers also discussed dual SIM/eSIM configurations and collecting IMEI numbers; Speaker 1 said they would walk back to the rack to fetch IMEI information and finish setup.
Why it matters: MDM misconfiguration can lock devices, prevent staff from adding critical work accounts and impair district operations. The group reported they had removed the device from the district list so it is no longer managed locally, but cautioned that Verizon profiles might persist and need carrier follow‑up.
Next steps: staff planned to gather IMEI and SIM details, verify portal entries, fully configure the MDM portal and re‑enroll affected phones. No formal policy or legal authority was cited during the discussion.
