Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About QueBall
QueBall
Here to help
Member since Oct 12, 2017
Oct 24 2017
Community Record
8
Posts
5
Kudos
0
Solutions
Badges
Oct 24 2017
5:17 PM
Yes. Android 8 should make things more generic for all manufacturers. For now this Knox mobile enrollment is restricted to Samsung devices, but it does the job especially when the latest versions of Knox are supported by the MDM in afw device owner mode you can do near zero touch. (Ok, clicking next a few times but that's about it)
... View more
Oct 24 2017
12:54 AM
1 Kudo
Unfortunately Samsung uses the brand Knox for everything they do in the area of mobile device security. Reminds me of the Smurfs. In this case Knox Mobile Enrollment is a distinct system for enrolling devices in a MDM system separate from the concept of the Knox container security API's built into the device. It is separate from Knox container on device, Knox Configure, Knox Premium MDM, and likely a bunch of other stuff branded with the Knox name. Like when my parents tell me their Microsoft isn't working the brand name itself isn't very meaningful unless you know the specific product name you are referring to.
... View more
Oct 24 2017
12:07 AM
3 Kudos
I have our devices successfully registered for Knox mobile enrollment. (A big hurdle here is the reseller or distributor must upload the list of serial numbers you purchased and assign it to your knox customer ID. You have no way of assigning these to your own account without reseller assistance.) This is similar to the Apple device enrollment program (DEP) in many ways. Now I have been testing a variety of MDM solutions and some support this Knox mobile enrollment method to automatically reinstall the MDM software after a device is factory reset. For the systems that fully support it I even have it enrolling the device in device owner mode which is what I want all our devices to be running. This would be a great help for any lost/stolen devices as they are forced to re-enroll in the MDM if anyone does a factory wipe on the device. The best ones will re-enroll without first asking the user to enter credentials. I am not seeing any documentation on what settings could be used for Meraki SM to utilize the Knox mobile enrollment system so I just want to confirm there is no unsupported method anyone can point me to in order to use this method to enroll new or reset devices? I assume the lack of documentation I could find means it's unsupported or my search kung fu ability is failing me. The list of supported MDM solutions that Samsung support sent to me did not include Cisco but that doesn't mean much as even the Samsung Knox premium MDM doesn't support the android for work mode so their own MDM is one of the worst choices for me at the moment. The one I have working best at the moment is Zoho manageengine mobile device manager plus. It's 90% automated. You just need to go into the console after the device has enrolled and booted up the first time to assign it a user profile and it then completes the android for work process. I think I like the Meraki system better for most aspects. Zoho is a little rough around the edges but this knox mobile enrollment feature is pushing me to choose them at the moment.
... View more
Oct 17 2017
6:07 PM
Thank you. Yes it does prevent creating new users. but it also prevent creating sync accounts so it's not very granular. Also the Samsung Tab E has a built in guest account out of the box. You are still able to switch over to the guest and back to the regular profile. BUT They just pushed out Android 7.1.1 update from our carrier. In the previous android 6.0.1 you could not remove or disable the guest account. In the new Android you can remove the Guest and once removed the device owner restriction now prevents you from enabling the guest account again. So a combination of this restriction and the upgrade to Android 7.1.1 and manual removal of guest does prevent additional user profiles. Unfortunately it does appear you must manually remove the guest user on each device.
... View more
Oct 17 2017
9:34 AM
So. No way to restrict this currently I take it.
... View more
Oct 12 2017
12:37 PM
Should not be allowed
... View more
Oct 12 2017
12:12 PM
I am testing Samsung Galaxy Tab E devices on Android 6.0.1 Out of the box a default user profile and a guest user is present. I am enrolling in AFW device owner mode so the tablet does not have containers it's 100% work mode. Problem is the guest account and ability to create new user profiles is not being restricted and so far I have not seen a method to restrict this and remove the guest profile. That means user can simply swipe down from the top, click the user icon and change over to guest and the tablet is basically back in unrestricted mode. They can do anything and all the built in apps that I did not allow are back. So, how to do it? How do you remove and restrict tablet user profiles. We do want the users to be able to have a fair amount of control in general. Changing wifi, managing bluetooth devices. Just do not want a totally unmanaged user profile possible.
... View more
Oct 12 2017
10:01 AM
1 Kudo
You likely want AFW device owner mode. It's kind of in the middle between the personal/work container that is default for byod use and kiosk which is completely locked to single use case. You can restrict to a small list of apps and continue to allow access to various settings while restricting others. I'm doing the same. My only issue is I do not seem to have a restriction or policy to limit adding new user profiles to tablet devices that support multiple users (that I can find). The secondary and guest users end up unmanaged/unrestricted. You must reset to factory defaults and when the wizard gets to the step to add your google account use the keyword afw#meraki https://documentation.meraki.com/SM/Device_Enrollment/Android_Enrollment#Device_Owner_Mode
... View more
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 3 | 17082 | |
| 1 | 17075 | |
| 1 | 4401 |
© 2024 Cisco Systems, Inc.
