video1.0<iframe src="https://www.loom.com/embed/1b2a4662291640588c6e34db66cb537a" frameborder="0" width="1920" height="1440" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>14401920Loomhttps://www.loom.com14401920https://cdn.loom.com/sessions/thumbnails/1b2a4662291640588c6e34db66cb537a-67538f4f5c9de47d.gif3194.04This Loom demonstrates and discusses MaaS360 for centrally managing UCSB enterprise mobile and Windows devices, using a hub and spoke portal model for delegated administration. It explains device enrollment via Apple Business Manager and Android enrollment programs, then shows core actions like real-time location, wipe versus selective wipe, push notifications, built-in reporting, kiosk mode application control, patch management with deferral up to 30 days and granular test-device rollout, and geofencing enforcement. The session covers administrative questions including hub versus spoke authentication (NetID versus SSO per spoke), iOS Apple ID management, APN certificate renewals, location services limitations, and options for non-DEP iOS enrollment via Apple Configurator. The team indicates POCs typically take 30 days, and setup to test use cases should take about two hours.