Or some way to manage a large app catalog (e.g. folders, tags, groups, etc...)

Add a button to force all devices to check in. If a device cannot check in after this, then flag it.
This will help identify issues with the installed profile or check in issues.

Show a list of locked devices or show more status on the main screen.
Group, model, status, last seen only on device screen. More data can be shown on the general devices screen.

Create an ‘admin notes’ field for each config setting in the console. This will allow basic change logs for any configuration changes.

Under iOS you can add a card account to the device. But under a macOS device yo can not. This would be a good addition.

In Europe its critical to record information about employees. It would be great if we could setup a MDM group were we can add our employees iOS devices and in this group we don't see the device location (already possible) and also disable the "Apps" tab, which can contain very personal information about installed apps.

Current provider uses VPNSubType com.sonicwall.SonicWALL-SSLVPN.vpnplugin which does not work with version 5+ of the macOS SonicWALL Mobile Connect.app.

New VPNSubType is com.sonicwall.SonicWALL-Mobile-Connect

We can already see UAMDM status (https://suggestions.simplemdm.com/forums/204404-suggestions/suggestions/33088666-uamdm-status) - but as we roll out to more machines it would be useful to have a report or column view or other way to work out which machines are enrolled but have not been approved by the user.

I appreciate we could write a lookup against the API to query this status - but that doesn't really scale when we hit 1000s of machines

Thanks :)

It would be excellent to have the ability to push VPN profiles as both user and device channel (similar to custom configuration profiles).

We are running iPads as Kiosks and only want to push updates to them overnight when users will not be effected, Ideally this would include all config changes but most importantly these:

- Non VPP App Updates (enterprise apps)
- iOS updates
- Other Configuration changes

As an MSP we manage several SimpleMDM accounts. It would be very helpful to receive and pay a single bill for all of these accounts.

Within the wireless settings, put in an option to allow for connecting to open networks. Would be good for public wireless connections that may need to go thru an acceptance screen or a proxy filter to allow connection. Currently it is only feasible thru a profile manager .config file custom attribute import. Would be nice to have this directly available in wireless security options.

Ability to set power schedules on devices. This would be for devices set up as kiosks to cycle power based on a time frame to provide a more environmentally friendly setup while providing device longevity. A must for kiosks, considering kiosk mode is an option.

The main table view should function like a true dashboard that has sortable and customizable options for the columns. It is too limited now and requires many clicks to drill down to see data like OS version etc. just way too much clicking to get basic info

Once an app binary has been uploaded and deployed to devices via MDM it can be hard to find which particular build is actually deployed to the world.

If you may happen to have binaries that share the same BundleID, CFBundleVersion, and CFBundleVersionShortString there is no way to tell which app is actually uploaded. If we could see an md5 checksum or sha1 or sha256 it wold be a nice and easy way to know with confidence which binary was uploaded.

I'd like multiple API keys able to be generated in the UI that have scoped permissions, for example, one API key restricted to only being able to hit the device endpoint, or one API key only being able to access Users.

With this feature, it would reduce the threat of the API key being compromised as it's potential scope would be limited.

Add a detailed EventLog in the MDM.

It would be nice to know if commands/messages were successfully sent to a device.

It would be great if the password of the local administrator account created during the DEP enrolment was unique to that device.

The password could be shown in the device information together with the EFI password and FileVault recovery key.