SOTI Pulse Logo

Small Internal environment, Wifi Profile and Velocity Package

C
Curtis
Garmin International, Inc.

Having a hard time with the SOTI infobesity.  Too much information.  There is so much I don't need but I can't tell what the minimum steps are.  Hopefully someone can outline best practices for me. 

  • 45 - Zebra TC70 and TC26
  • Profile for changing PEAP username/pw for Wifi - Installed and working
  • Profile Install Velocity package - Install package but can't launch
  • No special permissions, users or groups needed
  • Need Lockdown screen with Velocity and Chrome access to one internal URL

I have created and synced the 2 Profiles to one device.  Wifi works and I have been able to change Wifi username and password.  MobiControl app shows Velocity is installed but I can't launch it.  I only have experience with MobiControl v7 which is very different.  

I need to understand the order of operations, any help would be greatly appreciated.

Thanks

Curtis

setup
4 years ago
Android
ANSWERS
MD
Matt Dermody Diamond Contributor
4 years ago

Devices

The TC70 and TC26 may very well differ in terms of management style. Since the TC70 is limited to Android L you will have to use Device Administrator for management which SOTI called Android+ or Android Classic. The TC26, on the other hand, can support Android Classic if you have it on an older OS (M or N), but it can also support Android Enterprise, and in fact would require Android Enterprise if you upgrade the device to Android O. If you end up in a scenario where you need both Android Classic and Android Enterprise to handle both of the two device types then you will need to use different agents and enrollment strategies for both devices. You will also need to create Profiles that are separately applied to each device type. Android Classic for devices enrolled under Device Administrator and then Android Enterprise - Work Managed for the Device Owner devices. 

WiFi Profiles

Sounds like you have this working but again you may need duplicate profiles, one Android Classic and one Android Enterprise in order for it to apply to both device types depending on how you have them enrolled and managed. 

Package Install

You should be able to create a simple Package containing the Velocity ApK and have the SOTI agent install it on the devices. The Package can be universal but you may again need separate Android Classic and Android Enterprise Profiles each containing a copy of the Package assigned to each device type. 

Lockdown

SOTI has an integrated lockdown configuration available within the Profiles. You can assign this lockdown or kiosk to the devices based on the management type. Meaning you would need an Android Classic Profile containing a lockdown configuration and an Android Enterprise Profile containing a Kiosk configuration in order to apply them to the different device types. Both are configured more or less the same although you may notice some slight differences in behavior. Activity Suppression in the Kiosk mode of AE is the SOTI built lockdown tool whereas the Native option is native to Android Enterprise and will therefore behave differently than the lockdown of the Android Classic devices. This is primarily driven by differences in the device OS versions. Your lockdown profiles will also require you to add an Authentication configuration in which you set a password for exiting the lockdown as an admin. 

Chrome & Velocity Config

This is a little more advanced now and is starting to get beyond what is reasonable to expect from a SOTI support form. Configuring Velocity and Chrome for your business applications is something that you should be working with your device vendor on or the application support team for whatever host application you are trying to connect to. You can use SOTI to certainly push these kinds of configurations but actually building them is outside of the scope of a SOTI support forum. 

Similar Discussions