Are you specifically using mxconfig and not xmlconfig or mxxmlconfig? They are different.

Assuming you are using the right script, do you have the Zebra AE plugin installed on the devices? 

Hi Matt, 

I'm using mxconfig and have the plugin installed. 

It appears that you leveraged an enrollment method that may have left a large number of the system applications disabled by default. I can't say for certain, but this could contribute to unexpected behavior out of the devices as there may be other applications and service dependencies needed to perform functions like administering MX that are disabled on your devices right now. You may want to consider re-enrolling the devices using StageNow so that the system apps can remain enabled by default after enrollment. 

https://discussions.soti.net/thread/bluetooth-not-working-when-in-managed-device-mode/

I'm mentioning this because I manage numerous SD660 Zebra devices like the TC77 (eg. TC72, TC52, MC9300, TC8300, VC8300) in MobiControl and they all still support mxconfig. Zebra has marked it for deprecation and may eventually remove support for it in favor of OEMConfig but for the time being it should still be possible to leverage. 

Hi Matt, 

Since I posted the question for the Bluetooth issue there has been an update to the Stage Programmer application where it now leaves all system apps enabled. 

The issue I have is that the devices have already been shipped out to customers that are unfortunately in another country! 

I'll raise a ticket with Soti Support to see if they can help me.  

Hello Josh, 

Thank you for requesting a response from SOTI Support Staff.

As I believe you have created a case with Technical Support, the best scenario for obtaining the feature you need would be to submit a Feature Request with your Technical Support Specialist at SOTI VIA your case.

Otherwise, you may have limited options as your devices are already in the field.  Nonetheless, other options that I can suggest include; 

1. Enrolling future devices as Android plus as the feature to manage phone calls is available as a profile in that enrollment method. See the picture below.

2. Test and use an Application Run Control Policy with your devices in a sandbox environment to see if that can provide the results you require

3. Or to use a  script such as the manual blacklist script to restrict your phone application.  However, be careful as this method may have diverse effects as the phone application may be a system application and therefore required for accessing other applications such as Contacts.  Again I suggest you test this in a sandbox environment before deploying to devices in production.

manualblacklist on

manualblacklist add <application_bundleID>

apply manualblacklist

Hope this helps some,