Forum Discussion
Device Owner Provisioning
- 2 years ago
Not as far as i know of as the enrollment token/id/url or whatever the MDM expects is pointing to the relvant enrollment rule to be used (because in each MDM you can have several).
Otherwise the MDM doesn't know how to proceed forward with the device (which settings to deploy, is it COPE, fully managed or just BYOD, and so on).
I think you have to remove the { and } inside the enrollment token
Even after removing that I am getting below error, when scanning QR code after Factory reset. Am I using the Checksum in the correct format?
is the SHA256 signature which I need to encode? and I am directly pasting the SHA256 value with " : " in base64encoder and encoding it.
- Moombas2 years agoLevel 4.1: Jelly Bean
I don't know how/where checksum comes from but there are default ones for each MDM i think, so always the same if you use Intune for example (for any user/customer who uses Intune)
Related Content
- 2 years ago
- 12 months ago
- 19 days ago
- 9 months ago