SkieWhat if the enrolment token fails, expires or has to be recreated?
Create a new token from the dashboard and provision again. Tokens work once, so a token that failed or was already used will not work a second time. Check why the first run failed, usually an added Google account, a missing model profile or no free seat, then run the new command on a clean device.
A token can fail for reasons that are not about the token. The common ones are a Google account added during setup, a device model with no profile yet, a group that has no policy or app list, an organisation with no free seat, or provisioning that has been frozen. The Provision app shows the failure reason on screen, and on the laptop route the terminal prints the error.
Because a token works once, you do not reuse it. Go back to the dashboard, open the student, and start a fresh provisioning run. That creates a new token for the same student and group. You do not need to delete the student or rebuild the group.
Before you run the new command, reset the device if the first attempt got far enough to install anything or add an account. A half-finished attempt on a device that still has a Google account will fail again. If a different app already owns the device, see that entry.
If a token is no longer needed, for example the student left before the device was provisioned, simply do not use it, and start a new run for the next student. Skie does not publish how long an unused token stays valid, so make a fresh one on the day you provision.
Practical tip: when you handle many devices, fix the cause first and the token second. A new token on an unfixed device just fails again. See what a token is and the readiness gate.
- Create a new token, never reuse one
- Fix the cause before retrying
- Reset the device if the attempt got partway
- No need to recreate the student or group