Hi Milan,
Introducing a new state in addition to current 5 states we do have seems to
be the best way to handle this. And also we do require introducing a new
screen for the EMM server app which displays current dis-enrollment
requests to EMM Admins as well.
Thanks
On Wed, Jul 8, 2015 at 11:28 A
Hi all,
+1 for the idea.
Considering a BYOD dis-enrollment scenario, when an user sends a
dis-enrollment request to the system, are we going to change the device
state to a particular state (since we are already maintaining the device
life cycle) or introduce a new mechanism to support this proce
Hi All,
Given below is the proposed workflows for the $subject.
*Enrollment*
*BYOD*
Login -> License Agreement -> Enter critical operation PIN -> Registration
*COPE*
Login -> Registration
*Dis-Enrollment*
*BYOD -*
[image: Inline image 2]
*COPE - *
*There will be no dis-enroll option for
