How to restrict users from enrolling more than one device in Afaria

[Former Member]

Hi,

How to restrict users from enrolling more than one devices or how to  configure Afaria such that we can make a policy for  user enrollment restriction..So users cannot enroll as much devices they can

Conditions

• for first time enrollment ,first device ,automatic enrollment(without afaria administrator intervention)
• when the user tries to enroll second device ,enrollment should  fail for that user account

[Former Member · Accepted solution]

Hello Karthik,

Thank you for reaching out to SAP Community Network.

As per your request, Afaria is the Mobile Device Management process where the number of devices come into picture but not the number of users, same user can enroll multiple device.This would make us the user-friendly and manage the users count much more easier.

Once the device is lost or the employee leaves the organization, it would be easier to control the devices registered under his user id by removing MDM_Under_Control for all his enrolled devices. As you already know, Afaria came up with BYOD(Bring Your Own Device) to enroll there personal devices under corporate workspace along with his corporate devices.

Hope this clears your queries.

Kind Regards,
Sushmitha

[jtaylor]

Hi Karthik,

There are a few options to do this, but both require custom development on the customer side. For any built-in feature, that would be a feature request, which should be submitted through IdeasPlace.

Custom development options:

• Scheduled runs of a custom developed API program which would scan for duplicated users and disallow/delete one of the devices, and possibly also send a warning to the user that only one enrollment is allowed (via the API or email). This would allow enrollment of the device initially, but would also solve the problem of not having multiples enrolled.
• Custom enrollment portal which will only allow one device to be enrolled. This could prevent multiple enrollments if all users use the custom enrollment portal. There are guides available on SCN on how to create your own custom enrollment portal/self service portal using the Afaria API.
• (most tricky/dangerous option) Custom triggers on inserts into A_EUSSP_CODE or A_CLIENT, which checks if the user had another device enrolled and then removes a critical record if so. This is a dangerous option because triggers can cause unwanted locks and dependancies which can negatively impact the operation of Afaria. Additionally, any triggers created may work well with a current version of Afaria, but future upgrades may cause unexpected problems with the triggers as functionality may be added/removed or operations changed in an unexpected way to you..

[Former Member]

Hi Sushmitha,

Thanks very much for replying..My question is answered

Thanks and Regards

Karthik

[jtaylor]

Hi Karthik,

If you find that your question is answered, please mark it as so for the benefit of the community, so that when someone has the same question, they may find the answered one more readily. Thanks!