SOTI Pulse Logo

Impact of Android 11 Scoped Storage Restrictions on Android Agent

Solved
JD
John Doe
Eisen Karl GmbH

Hello @All,

as stated in the article below, there are a few more restrictions with Android 11:

https://discussions.soti.net/articles/impact-of-android-11-scoped-storage-restrictions-on-android-agent

The main one that really hinders our staging process is that you arent able to use mcsetup.ini anymore.

Has anyone gotten the agent Version 15.1.2 on Android 11 to accept mcsetup.ini? Any additional manual step i.e. scanning or putting in the enrollment id is "annoying" in the whole staging process.

Combining Honeywell Enterprise Provisioner or Zebra MX with mcsetup.ini was a nearly 1 step process to enroll and stage a device for us.

Any ideas appreciated. 

scoped storage enrollment
3 years ago
Android
ANSWERS
MD
Matt Dermody Diamond Contributor
3 years ago

I never liked using mcsetup.ini since you have to host it somewhere for the devices to download it from. For Zebra devices I have found that it really isn't that labor intensive having one extra scan into the SOTI agent for the Enrollment ID after having StageNow auto-install and launch the agent. For Honeywell devices you can embed the Enrollment ID into the enrollment process without requiring an mcsetup.ini file or a separate barcode scan. 

Solution
JD
John Doe
3 years ago

Embedding the enrollment id into setting the device owner action never worked for me somehow, but i´ll try it again. Thanks for bringing that up again, could be a possible solution.

For us hosting files on a tiny sftp-server / ftps for zebra made some steps easier :)

JD
John Doe
3 years ago

I now found out that there is a bug in the Honeywell Enterprise Provisioner where its not correctly putting in the arguments for the enrollemt id.

Now it works with the enrollment id or enrollment url.

MB
Marcus Breitenthaler
3 years ago

Are you using the last Honeywell Provisioner Version 1.07.00.0436 ?

It is working as Designed there is no Bug. ;)

When you are entering at the Task "set device owner" must be klicked on "add Provisioning item to list" 

JD
John Doe
3 years ago

After trying again, yes.

the previously used version had the issue.

Similar Discussions