SkieWhy does the Provision app never provision its own phone, and how do I confirm the right device?
Provisioning makes Skie the owner of a device and locks it down, so doing it to the helper phone would lock out the very device running the app. The app refuses to provision its own phone, and it asks you to confirm the target device before it continues, so the wrong tablet is never set up by accident.
The helper phone is the one in your hand with your sign-in on it. If provisioning ran on it, that phone would become a managed device with its own rules, and you would have lost your setup tool halfway through a rollout. So the Provision app never provisions the phone it is running on. It only works on another device it has paired with.
The second protection is the confirmation. On a desk full of identical tablets, the wrong one is easy to pick up. Before committing, the app shows details of the device it found, such as its model, and asks you to confirm it is the one you meant. Read it against the tablet in front of you. If it is not the one, stop and re-pair.
Mistakes matter because one token binds one device to one student. Provisioning the wrong tablet means the right student's token is spent on the wrong device, and you will need to start a new run. Taking a few seconds to confirm costs less than a reset.
A habit that helps is to number the tablets with a sticker, or to line them up in order and provision left to right. Match the sticker to the student in the dashboard as you go, so the device list is already correct on day one.
Practical tip: provision one device at a time rather than powering on a stack, so only one reset device is on the network. See the Provision app and the enrolment token.
- The helper phone is never managed by its own app
- You confirm the target device before the run
- A wrong device wastes a one-time token
- Label tablets before you start