Depending on how you set it up, you can get away without touching anything. Here is the process I use:

- Factory Reset GMS Zebra Android Device 

- From the Welcome screen of the Google Setup Wizard scan the StageNow barcode to skip the SUW and launch into StageNow

- Scan StageNow barcode(s) that connects the device to wifi, downloads the agent from SOTIs website, installs the agent and sets it as DO, then launches the agent

- Scan the enrollment ID as a barcode.

All told, its 2-3 successive barcode scans without any manual interaction. 

You will need to switch to Android Enterprise. 

https://discussions.soti.net/thread/zebra-tc56-8-1-0-oem-device-agent/

https://discussions.soti.net/thread/zebra-tc52-mobicontrol-stage-apk/

https://discussions.soti.net/thread/zebra-tc72-device-agent/

https://discussions.soti.net/thread/is-there-a-newer-version-of-mobicontrol-for-use-on-zebra-tc75x-running-the-oreo-os/

To be clear, and If I understand well, Android Enterprise is in reallity a new OS that I need to install on the device ?

I cannot found anywhere an Agent from SOTI compatible with the OS provided by the manufacturer itself ?

If I have ordered 50 devices, it will be a great pleasure to do it one by one, instead of flash a barcode to deploy app and configuration !

Thanks for your lighning !

Understood !

Do you know if apk file can be used in this case ?

I used Android Enterprise as setting (after create account...), the aim is now to deploy with StageNow (with a barcode)

The apk even with this account seem to not work. And StageNow cannot push a doawload from play store.

If I understand well, all was automatised before, and with this Android Enterprise, I have to enter code manually at the start.

I'am tired just to imagine all the click i have to do for all of our scanner.

I just applied what you said just here, and it works perfectly !

Thanks a lot, your help was very appreciated !

Some links to people like me, not very familiar with all of this, hope it can help someone else !

Google apk for soti mobicontrol : https://docs.soti.net/mobicontrolagentdownloads/

scan to skip the wizard (at the bottom of the page) : http://techdocs.zebra.com/stagenow/latest/Profiles/wipedevice/#setupwizardmanualbypass

and stage now, but I think if you read this, this point is already clear !
https://www.zebra.com/us/en/support-downloads/software/utilities/stagenow.html

thanks again Matt !!!

FRom this Topic, The agent installed doesn't allow to take control on the device.
From what I read here and there, I came from the agent, seems the one I use is not the good one.
But, all of Agent I can found cannot be installed from stagenow.

I always have an error during installation.

How are you installing the Agent? You need to use Xpert Mode->Wizard->MDM enrollment instead of just AppMgr based app installation of the APK since the agent needs to be set properly with DO permissions. 

I sent an email to soti support to understand a little more...

I read here and there that apk from soti / zebra was a standard enrollment.
Whatever I choose (even directly from console) the result is the same, cannot perform the installation.
(MotorolaMobiControl1422.apk / ZebraMobiControl1375_1013.apk ...)
An error occurs during the process (process copied in stagenow from one working)

(and I tried also the Expert mode Matt !)

The only one which works is : GoogleMobiControl1376_1004.apk

But this one does not permit me anychange on the device.

I hope Soti's support will release a version that I'am allowed to install, and with I can have the remote control function !

I'am not the only one in this case.


I will try to bypass stagenow and install through afw#mobicontrol , just to see if I can remote my device.

It was so easy to deploy & enroll devices by the past ... pffff
Sorry to disturb !

You are still doing it wrong. The problem is not SOTI. I guarantee that your device is capable of being fully managed and remote controlled with SOTI, you're just not following the proper procedure for Android Enterprise. I strongly suggest that you read up on the differences between Device Administrator and Android Enterprise and Device Owner and how DA is being deprecated by Google over time. This is a larger scale trend beyond just Zebra and SOTI that is beneficial to understand so that you can see how it applies to SOTI.

Zebra devices running Nougat and below are managed in SOTI via the DA mechanism which required an OEM specific Agent (eg. ZebraMobiControl....apk). SOTI, and technically an EMM provider had to create, compile, and maintain these OEM specific agents under DA which was a considerable amount of work. SOTI was one of the best at doing it which is why the Zebra agents support Zebra specific features like MX and install_system_update zips. 

Under AEDO however, there is a move to genericizing the agent so that all devices can use the same agent. This considerably reduces the amount of work and overhead for the EMM providers since they don't have to maintain separate agents for every OEM. There is still a need to provide OEM specific features like MX and Remote Control in the AE era, which is why SOTI is providing separate manufacturer specific plugins that enable those features that need to be installed AFTER the device is enrolled. I'm guessing that is one of the steps that you are missing.

Another piece that you are likely missing is the difference between Profile Owner / Managed Profile and Device Owner / Managed Device. In AE, the exact same device agent is used for either of the two management styles (there was only one option under DA), and it is the enrollment method you use that dictates which management style you end up with. DO based enrollment is really only enabled from the Google Setup Wizard via the QR, NFC, DPC Identifier, or ZTE methods. If you were to install the same agent manually on the device after skipping the SUW you will end up in Profile Owner mode which is definitely limited in what you're able to manage because it is purposefully designed for the BYOD use cases. Zebra gives you one bonus method of using StageNow to install the AE agent and set it as DO but you can't just install it like a regular app. It needs to be installed via the MDM Enrollment StageNow wizard which grants the proper DO permissions to the application. There is no other way around it if you want the device properly enrolled and managed as a Managed Device. 

Thanks Matt to the time passed to try to make me to understand 

I was near to my aim.

All the step describe is good, and it miss just the plugin file ...

I was trying with a wrong one, that why I have so luch difficulties to understand ^^

This help me too, to deploy my *.pcg file.

On a TC56 the pcg files are stored in /data/data/net.soti.mobicontrol.motorola/app_pkg

So, you could attempt a (re)installation of a package named "AppName" with a script:

installpackage "/data/data/net.soti.mobicontrol.motorola/app_pkg/AppName.pcg"

Sorry for all of this, I'am really a noob in this kind of deployment, thanks a lot MATT !