Good Morning All,
Thank you for all your responses and sorry for the delay, I have been busy enrolling more devices.
The devices tripping over does not seem to be network based as far as I can tell, we have three separate networks. Even having 1 device connected on each network will trip if we enrol them all simultaneously.
Some days we only have 1 device enrolling and we still encounter issues with the downloading of apps. It is faster but the biggest issue seems to be a playstore issue which is that they feel the need to finish unpacking and installing each app before downloading the next, would be much faster if it could move to downloading the next app quicker.
The reason for having such a large amount of devices on one user is that before I joined the account our company actually used a third party to create the Zero-Touch, the way this was setup was to enrol all devices to this one user, as far as I am aware there is no way to automatically create new users for each Zero Touch enrolled device without a lot more user intervention being required. We currently manage all devices using device names that are assigned to the devices, this creates no difficulty in locating the devices.
Again as for the number of devices being enrolled it currently can go from 100+ a day to just 1 a day. Even when doing just one device on a 100mbps leased line connection we are finding massive issues,
Kind Regards.
------------------------------
Michael Hogeling
------------------------------
Original Message:
Sent: Tue May 18, 2021 02:12 PM
From: Matt Shaver
Subject: Bulk Enrollment on Android Enterprise
The number of devices enrolled to a single user will not impact the amount of time it takes a device to enroll nor would it have any bearing over the speed for app installs.
9 times out of 10 these issues are related network bandwidth, but you shouldn't have to re-enroll any devices to solve these issues.
Bulk enrollment is a fairly broad term.
If it is simply being used to describe enrolling a lot of devices at once, Mitch's advice could work to relieve some traffic.
If you are finding the issue is occurring when using a specific device enrollment program, sometimes bottlenecks can happen as this is all cloud service syncs.
If you are enrolling something low, like 5-10 devices at once, and your network seems fine, and should be able to handle large amounts of traffic, I would open a support case so we can dig in to your specific use case.
------------------------------
Matt Shaver
System Architect
IBM
mshaver@us.ibm.com
Original Message:
Sent: Tue May 18, 2021 12:03 PM
From: Eamonn O'Mahony
Subject: Bulk Enrollment on Android Enterprise
Hi Michael
I have spent some time looking at your portal and one thing strikes me.
We recommend that as much as possible, devices be enrolled to an individual, given that Support has found that both location tracking and app inventory can be difficult to retrieve where large numbers of devices are enrolled to one account.
Ideally speaking you would not go over say 30 devices per MaaS360 user, it seems this is far exceeded in certain cases.
If you would like to verify this you can re-enroll several devices to individual MaaS360 user accounts and test the app update and inventory update procedure.
Best
------------------------------
Eamonn O'Mahony
Technical Client Success Manager
IBM Security
Dublin, Ireland
Original Message:
Sent: Thu May 13, 2021 06:14 AM
From: Michael Hogeling
Subject: Bulk Enrollment on Android Enterprise
Hi has anybody else got the issue where bulk enrolment is majorly stunted due to getting device enrolment errors whilst enrolling multiple devices along with the issue that once they install the app installations takes forever regardless of download speeds.
I was just wondering how you setup your devices and if you have any ways to tackle these issues,
------------------------------
Michael Hogeling
------------------------------