With admins having to move profiles to MDM in 10.16, it would be great to be able to edit the Simple created PayloadIdentifier for these profiles to match existing values.

A warning dialog box to explain the issues this may create would be sufficient (and welcome) to help admins know the risks with editing the value.

Allow certain profiles to only be deployed to certain versions of macOS.
I would like to be able to deploy certain profiles ONLY if the current macOS version is 10.16 or above. The MDM spec reports the OS version so using this as criteria for profile deployment would be a big enhancement going forward.

Possibility of showing last reported IP of a device in management console under Network which would help confirm that devices out in the field are matching the DHCP reservation assignments.

Massive market potential in the K-12 space if support for pulling over classes/users from Apple School Manager was implemented. Your competitors (Airwatch, etc.) do this quite well. We deploy 100's of iPads to classrooms and really like the ability for each cart to have 20 iPads with the user accounts for those classrooms synced from ASM. This would be a game-changer and a feature that is non-existent right now. There is a growing market in the K-12 space looking for this, make it happen!

Please provide a feature to send e-mail notifications to SimpleMDM Administrators on new device enrollments (and/or other things that pop up in the notifications inbox within SimpleMDM).

Currently the media catalog only allows epub and pdf documents. It would be great to have the ability to upload videos directy to the iPad media catalog. Our use cases are for how to setup things that the iPad is specifically used for. We have other methods but this would be quite helpful so that users do not have to rely on a network connection if they are without one.

iOS allows default changes for mail and browser, could these be set via device profile?

First priority: the administrator account should be optional. I install my admin account via a signed package, and go out of my way to disable the simplemdm-created account.

If that's not possible, at least allow me to set the UID of the user to something <500 so it's more invisible to users.

SimpleMDM should support ALL features and settings from Apple Profile Manager.

If it did, it would be possible to move from something Apple only delivers as a kind of "proof of concept" to a system that seems to more pointed towards the future. At the moment SimpleMDM lacks too many profile settings.

I would like to be able to preset a passcode and/ or change the passcode on a device.

For OpenVPN I need to download 3-4 config files to the app on Ipads or Iphone. For now it's only possible to deploy the files throug apple configurator 2 once the device is managed. I'd like to be able to send the config files from simple mdm per user. In the case of OpenVPN that would allow to configure a vpn remotely with out needing to deal with custom profiles that don't work properly most of the time.

In Device>Accounts>Add account Google is an option. It would be fantastic if Office 365 was an option as well. I'd love a streamlined way to deploy Office 365 credentials to apps such as Outlook, Excel, and Word at the same time, especially on iOS where users may not be familiar with app passwords.

When revealing passwords (such as Firmware Password), display numbers and letters in different colors. With the current font it's, for example, really hard to separate lower case L from the number one. Attaching a screenshot on how 1Password does this.

I need to be able to see a pending command queue, especially for offline devices. For example, let's say I have a lost/stolen iPad. The device was online yesterday, so I enable lost mode on that device. Since it's not currently online, that command is queued in the background until it's online again, but there is no indication whatsoever that the command is queued up.

Hi. will be able to also use IMEI number when i search for a unit in the tool.

Br

Rachid

Document the expected namespaces for the Logging API. This would allow for better planning / implementation of log ingestion / grok’ing.

Similar to /devices/ allow searching for dep devices by "attributes": {"serial_number"}, or "relationships": {"device": {"data": { "type": "id" {$id}}}}.

Or possibly add a relationship on the device record to its DEP device entry.