The MX option you're looking for is 

AppMgr-> DisableApplication

http://techdocs.zebra.com/mx/appmgr/

You'll want to use xpert mode in StageNow to create a profile containing the AppMgr CSP. Don't use the wizard based options that you're initially prompted for. 

Once you figure out how to create a StageNow AppMgr Profile you can feed in the package name of the application that you want to disable, in this case the package name of the Play Store. You can also disable other GMS features this way. 

Then, once you've generated the XML file from StageNow you can distributed it via SOTI and apply it with a post-install mxconfig script. More info:

https://www.soti.net/mc/help/v14.3/en/index.html#console/other/stagenow.html

More info on handling GMS from Darryn Campbell, a Zebra engineer:

http://www.darryncampbell.co.uk/2018/04/17/gms-in-the-enterprise/

He recently had a webinar on a new actively managed feature called GMS restricted from Zebra as well. GMS Restricted is only available on the SD660 / Helios platform devices, which does not include your TC75x. For that reason you'll have to leverage the AppMgr approach outlined above, but its still a neat feature to be aware of. 

http://www.darryncampbell.co.uk/2019/02/28/devtalk-learn-about-gms-restricted/

MobiControl version 14.1.4.1693

Do you need the Play Store for any reason? If not you can disable it with an MX setting. 

Unfortunately, I don't have any such device to do any test to verify the features supported.

From what you described in your post, you seem to have used Android Plus device agent for your Zebra TC75X.  But if you are actually using Android-Enterprise device agent in managed-device mode, don't forget to deploy the Zebra Android-Enterprise plug-in .pcg to get some supported advance features configured.

Have you checked the log tab associated with the device for any warning or error message related to SMS/MMS feature control?  If they are not supported on TC75X, there should be a warning message when the corresponding feature-control profile payload is being deployed to the device.  If the feature is supported but you don't get it, the most probable reason is that your profile configuration cannot be deployed due to configuration conflicts (e,g, maybe one profile enable a feature and enable profile disable a feature) or there is no administrator password set on the device with an authentication profile payload. 

We are using our devices with android+ configurations/profiles only, not any enterprise features at the moment. Haven't come across anything with stagenow or the use of scripts to change settings on Google Play Store. Very new to this, so could be an easy fix just out of grasp.

What would work best is something we can role out in a profile/configuration or a script to hit devices remotely during a maintenance window. I've tried all my best google foo but disabling play store with a command isn't out in the wild from what I can tell.

How can it be disabled with an MX setting? I've gone through StageNow prompts and didn't come across anything, pretty sure it can be referenced by com.android.vending but 70% of our devices are already deployed. Have you come across any scripts that can be run remotely by chance? 

Hello Trevor Costello !

Thank you for requesting an answer from SOTI Support Staff !

Regarding question 1) Starting from 14.1.8 , we have a profile configuration "Managed Google Play" for Android Enterprise devices , where in you can choose how you want your applications should update. There are few options like 

a) Allow user to configure

b)Always update

c)Never Update

d)Update on Wifi only.

You can choose any of them which suits your requirement.

Regarding question 2) I will reproduce this issue and will confirm with my test results. Can you please inform me the agent version on those devices where you are pushing Feature control profile for disabling SMS/MMS  Text messaging.

Thanks !

Thanks for the response!
We are running:

Zebra TC75(X)

Agent 13.6.0 build 1664

With Soti MobiControl Server version 14.1.4.1693

We haven't looked into enterprise yet. It is under consideration though, and is dependent on costs and we've got about 600 sets out in the field and a few hundred more to deploy.

I also identified the issue with the SMS messaging, seems the provider kept claiming they were data only but pushed them further and was able to find out that 60% of the devices are not data only LOL. Will be pushing them to batch those SIMs :D

Hi Trevor, 

Were you able to find a solution in the end to your inquiry?

Took a bit of digging but managed to get it sorted through the use of profiles after all. 

Application Run Control:

   Bundle Identifiers: 

      com.android.vending

      com.android.mms

Stagenow was also effective, but wasn't practical to roll out these changes with so many out in the field.

SOTI support StageNow MX XML. You do not need to manually scan the StageNow barcodes on all the devices, you just deploy the MX XML generated through StageNow as a package with an mxconfig post install script to process the configuration.