Hello Robert - Could you please rephrase your question? Please let us know what do you mean by "enroll a couple users in apple's iOS beta service"?

Regards,

Technical Support

Hello Robert - Please let us know if the issue is now resolved. Else, could you please rephrase your question, and we will be able to assist you with.

Regards,

SOTI Technical Support

https://beta.apple.com/sp/betaprogram/

I would like to confirm, if you wish to enroll iOS devices with beta iOS onto MobiControl?

In general, any valid profile configuration file (with default file extension .mobileconfig) can be deployed to an enrolled device with "custom profile" configuration in an iOS profile in MobiControl.

However, regarding using MobiControl for device with beta iOS firmware,  this is likely not recommended.  MobiControl, like most of the other top MDM/EMM solutions on the market, provides same-day support for production version of iOS for the last few major version releases.    Beta firmware from https://beta.apple.com/sp/betaprogram/ likely have problems and are primarily for developers to debug problems, and for bold end-users to try out new but possibly unstable features on their personal devices.  For enterprise using MDM/EMM solution for security and manageability reasons, does it make sense to risk losing control or compromising system integrity by using beta firmware on production device?  If any problem arises on your production devices,  you are likely on your own and will not receive any support from an MDM/EMM vendor.

We wouldn't roll a beta iOS out to our 4000 devices.  This is for a small group of 10 people to try the OS prior to it's full release.  This way we can proactively know what our users may experience.

These are corporately provided devices, if problems arise, we factory reset them or have them replaced.  

I'm just uncertain, as to my limited training, how to get the UI package onto soti to deploy to these users.

From previous experience with iOS9.3, iOS10.0, iOS11.0 and iOS12.0 releases, the MDM related functions in Apple's production firmware got stable only AFTER the first 3 or 4 minor patches.  So, our corporate/governmental customers in Hong Kong were strongly advised to remind their end users to upgrade their firmware only after x.0.4 or later is available.    Apple's recent addition of new restriction to postpone firmware upgrade prompt for a maximum of 90 days has made the process less reliant on end-user self-discipline not to choose firmware upgrade too soon. 

So, I reckon your so-called "PROACTIVE test on user experience" needs not get started BEFORE the first production release  (i.e. x.0.0) is out officially, and thus there is no point trying things out too soon with  pre-production firmware from https://beta.apple.com/sp/betaprogram/.  Anyway, it is you who make the call for your own corporate devices.  Just be prepared that you are on your own if anything serious goes wrong.  Don't scream for help if your device gets totally out of control or cannot get re-enrolled/re-deployed after factory reset, or other problems of similar severity.

Thanks Raymond, for the explanation. I totally agree with you. Even our in-house developers will be working on these newer versions of iOS and we have to follow all the testing protocols before we could attest the product to work with the new iOS.