Capability to prevent the user from running a specific application defined by admin in the admin interface.
A log should be sent to the server when the user tries to start the application.

Add support for screen sharing and remote control of the device. Minimum either iOS or Android must be supported

Currently Sophos Mobile Control already works with Zarafa Mailservers (Exchange alternative) but is not officially supported. This product is quite widespread an a support would extend our possibilities to promote the solution.

I think the current functionality of the reporting is not enough - not so informative, not be able to scheduled. One of partners that are about to start SaaS with SMC is trying to extract data from the SMC database directly. But the schema of the DB is not open to public.
If the reporting interface like Sophos Enterprise Console is provided, user can easily　create his own report as he like.

Sophos Mobile Control should deliver support of the NitroDesk Touchdown client. This includes:
- Configuration of the client
- remote partial wipe
- ....

This would move the data protection level on Android phones on the same level as on iOS.

Please make it possible to install SMC on a Linux machine. Several customers do not feel comfortable with security software running on a Windows machine. Some even have policies to not allow Windows machines in their DMZ, so a Linux version would be highly appreciated.

If on a smartphone/tablet the roaming/data threshold is passed, block further data traffic through SMC until a “new period of roaming” is starting.

Adding Apps to the blacklist/whitelist is currently not very handy. It would be nice to be able to add Apps to the list using the “Show installed software” feature. It would only require checkboxes in front of the Apps and 2 buttons (Blacklist/Whitelist) and would make the definition of the lists much easier.

Push out or remove policies based on the device GEO location. This feature will require constant communication of the location with the server

Implement a new method for SMC licensing, which removes to know the URL before purchasing. The URL will be needed at the time of installation, the license will be enabled by entering a license key (similar to SMSec licensing)
Without any license key, the system is in an evaluation mode with 5 users and 45 days

MSFC ( MicroSoft Failover Cluster ) should be supported since a failover configuration is required in an enterprise sevice

Provide access to files published from the SMC server from within the SMC client

Currently iOS Applications can only be removed by manually accessing every device and removing each application separately. It should be possible to create "Remove Application" tasks in a Task Bundle so an administrator could remove an application with fewer clicks from any device.

Control of the monthly used data traffic is very important for our customer. With Android we can define a watermark and if the traffic goes beyond that, the user gets a notification. Will be very useful has it for IOS devices and a lot of our customer ask for it.

When a device gets non-compliant today we have the chance to send a "lockdown" profile. Could be useful if it is compliant again to have the possibility to have an automatic remediation that delete the "lockdown" profile.

Instead of whitelisting/blacklisting specific apps, why not be able to allow/block certain categories of apps instead? So that you are able to block games but allow productivity apps. Trojanized and malicious apps could be blacklisted as default.

Currently it is possible to define the outgoing proxy server directly inside the database. But it is not officially supported to use this settings.

Especially larger accounts only may access the internet via an proxy and need to make use of the proxy functionality. So we should officially support this setting and/or make it available via the Configuration Wizard.

Silent (un-)installations of apps on Samsung SAFE devices is possible according to http://www.samsung.com/us/article/samsung-for-enterprise

SMC 3.0 supports SAFE-APIs.

That's a really good instument to enforce Black-/Whitelists.