No, we're working on enhancements that will provide easier solutions here. The 10 device limit is something we imposed (it can be removed) because Google limits the number of devices to a single Play account can be logged in to 10. This means that if there are 11 devices with the same Google account active in a 24 hour period trying to access Play services, one of them will be automatically logged out.
Currently each user in the portal gets associated with one Google account, we're working on enhancements that will support extending this number, as well as support for "device accounts" in which each individual device can have it's own unique Google account.
------------------------------
Matt Shaver
System Architect
IBM
mshaver@us.ibm.com------------------------------
Original Message:
Sent: Fri February 14, 2020 12:47 PM
From: Noureddine LAAREJ
Subject: Maas360+Knox Enrollment DO
Hi Matt,
OK but there will always be a limit of 10 devices?
Noureddine
------------------------------
Noureddine LAAREJ
Original Message:
Sent: Mon January 27, 2020 11:50 AM
From: Matt Shaver
Subject: Maas360+Knox Enrollment DO
If there is a KNOX mobile enrollment profile and the device is not already activated, absolutely. One potential solution that is easily configurable would be to create a "stolen device" profile in the KME setup portal. Include a JSON with some generic user enrollment credentials so that the devices marked with the profile automatically enroll in MaaS360 after the app is downloaded. In that case you'd be able to see the device in the portal and take direct actions.
------------------------------
Matt Shaver
System Architect
IBM
mshaver@us.ibm.com
Original Message:
Sent: Mon January 27, 2020 11:31 AM
From: Amy Burt
Subject: Maas360+Knox Enrollment DO
If the phone is also registered to Samsung KNOX – will it try to force MaaS360 setup in this scenario?
Original Message------
I don't have the full scope of the planned restrictions available, but we're looking at a scenario where the device has downloaded the MaaS360 agent, but has not yet gone through the enrollment process, so there wouldn't be any record of the device in the portal, nor could portal actions be taken. The app will have a process built in whereby it would enforce a policy that removes device functionality before it is enrolled, then lift those restrictions once enrollment is complete.
------------------------------
Matt Shaver
System Architect
IBM
mshaver@us.ibm.com
------------------------------