Could he have entered incorrect device passcode over a period of time, and based on your passcode policy the device reset itself?
Looks like what KB50107292 explains, but in this case, triggered by a revoked certificate?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Moderator: Moved to Workspace ONE Discussions
Could he have entered incorrect device passcode over a period of time, and based on your passcode policy the device reset itself?
Yes, it would be possible, I'm now trying to reproduce it on my test device, for comparing logs and see if it's same behavior.
thanks!
You are right, after consulting with user and review policies, that was the root cause.
Thanks a lot!