Suggestions
Have a great idea that you’d like to see added to our service? Perhaps there’s an existing feature that you’d like to have extended or modified? Share it here!
460 results found
-
Add Support for Munki Conditionals to SimpleMDM's Munki Implementation
Munki includes the ability to set "conditionals" for items in specific manifests to provide granular controls over the installation or appearance of items.
For example, if I have a multi-site organization, I can set a conditional on a NOPKG item that installs a printer so that the printer install NOPKG only shows up if the device user is connecting to Munki from a specific subnet. This allows me to refine the view of available self-service printers so that, for example, the printers available at Site A only show up if the user's local IP address matches the subnet at Site…
10 votes -
Add TeamViewer QuickSupport and SplashTop SOS tools to the Shared Application catalog for Munki-based installation.
Just requests for common user-driven support/screen sharing applications:
TeamViewer QuickSupport
SplashTop SOS3 votes -
Make logging more detailed for MDM commands
While I appreciate how detailed SimpleMDM logs can be, especially with raw responses from MDM, sometimes they need to provide more detail. For example, when sending an OS update command the log only contains...
"Log Details
Full ID E7B0DBE9-A7C1-4EC8-8CB8-BFA4AB990C59
Created At 2023-08-17 3:34 PM
Namespace device
Type os.update.idle
Level info
Device redacted
UDID F405AA51-FF04-4B71-900F-9C09F0515398
Serial Number redactedMetadata
{
"update_version": "13.5.1"
}
"With OS updates in particular, it's useful to know what mode was used as well. 'downloadonly', 'notifyonly', 'installasap', or 'forceupdate' are all options, but there's no associated data. For some basic commands like…
9 votes -
Improve API docs with examples for each endpoint
SimpleMDM's API documentation (https://api.simplemdm.com/) is inconsistent in what information is included per endpoint. For example, https://api.simplemdm.com/#custom-configuration-profiles shows the response body for a GET call, but the POST (create) section has no usage information. It's up to the user to intuit from other endpoints the format in which those arguments should be.
https://api.simplemdm.com/#custom-attributes shows how to set a value for a device, but not create a new custom attribute globally.
We (the customer) end up making assumptions about API formats which are usually true, but only able to confirm through guessing. It would help to ensure the official docs…
10 votes -
Make the `app_usage_data` portion of Munki optional
Having just confirmed with Eric and others in the Slack channel that SimpleMDM's Munki instance doesn't make use of the
app_usage_datafeature in Munki - would it be possible to create a toggle to turn it off?Additionally there are some global regions where tracking this kind of stuff falls foul of local privacy laws...
...and it's upset my privacy focused end users.
Thanks in advance
11 votes -
Customize Self Service Kiosk
I want to be able to change text and icon for the kiosk
https://kb.filewave.com/attachments/16?open=true
Doesn't have to be this complete but simple changes so it says <company name> software kiosk
6 votes -
Add description as argument for creating/updating custom configuration profiles
When modifying custom configuration profiles in the web UI, there's an optional field for "Description (Optional description presented to the end user.)", which isn't exposed via the API.
1 vote -
Add support for additional com.apple.MCX keys in FileVault profile type
The current FileVault profile builder in the admin GUI only has options included in com.apple.MCX.FileVault2, the escrow payload, and dontAllowFDEDisable. Please add support for dontAllowFDEEnable and DestroyFVKeyOnStandby from com.apple.MCX as well.
Apple docs here: https://developer.apple.com/documentation/devicemanagement/fdefilevaultoptions
6 votes -
Support SCIM provisioning and de-provisioning for admin accounts
SCIM (System for Cross-domain Identity Management) is a REST/JSON protocol defined in RFC 7644 that allows identity providers to direct service providers to make account create, update, and delete actions. It is generally used to pre-provision access for new accounts and de-provision access for accounts that no longer require it.
Please add support for SimpleMDM to work with the SCIM protocol for administrator accounts. A minimum implementation for our purposes would be to create administrator accounts using SCIM at the default permission level, and have the delete function revoke access on the given account. In a perfect world, the SCIM…
15 votes -
iPhone parts and service history information
Please add information about whether the device has been repaired and equipped with genuine parts to the device information API.
Please refer to the URL below.
https://support.apple.com/en-us/HT212878Thanks
3 votes -
Allow setting device naming schemes per enrollment
We use the device naming template under Settings -> General. This works great for our macOS and iOS devices that come in through manual enrollment and ADE as our template contains the serial number attribute, but fails when User Enrolled devices are named because that attribute isn't available. It would be useful to allow us to set a different device naming scheme per enrollment, or at least to set a backup or some sort of logic should one of the attributes be null.
20 votes -
Individual Device Profile Exclusion
Add an Action in Device Details > Profiles that allows you to exclude a profile from an individual device.
3 votes -
Add Microsoft OneDrive universal app to shared catalog
You currently only have the Intel version available.
1 vote -
Scope profiles to build version
With the advent of RSRs, the OS version is no longer a definitive identifier of what OS rev a system is on. The OS build numbers would be a more consistent way to identify target OSes.
Historically, macOS minor builds have followed an pattern of
[Major OS number][A...Z minor build][Patch Number] moniker.Now with RSRs, the build numbers are a bit more complicated but the values still go up and each build number is larger than the last based on the pattern above.
13.3.1 22E261
13.3.1 RSR 22E772610a
13.4.0 22F66
13.4.1 22F82
13.4.1 RSR 22F770820bI propose that Build numbers…
5 votes -
Prepopulate Job Name Field for New Jobs
When creating a new job please auto populate the Job Name with something unique rather than leaving it blank. For example, something related to the current timescriptnameSerialNumber would be useful.
The admin should be able to edit this prepopulated name if they so wish.
5 votes -
API device profile install status
In webUI you can see the profile install status, but in API you can only see "assigned" and no visibility of whether it installed or not. This is useful information, particularly in my case when assigning a SCEP profile where the CA is in corporate network. The profile install frequently fails due to devices being off LAN.
This could be an install status when querying device/profiles or an installed profile list when querying devices, which we'd compare to assigned profiles.6 votes -
Include "less than macOS version" and "greater than macOS version" for profile scoping
It would be very helpful to be able to define "less than" and "greater than" macOS version when scoping profiles. For example, I would prefer to specify "less than macOS 12" for a profile to apply to all versions of macOS 11. As it is, I have to update the maximum OS version every time a new dot release comes out.
7 votes -
Control Webhook data
Webhooks are very limited in what they provide without triggering another API call to pull in more information. The ability to control the payload within the webhook endpoint creation screen would be a huge help in interfacing with other programs. The ability to add static data to the payload (like we can already do to the header) or be able to add dynamic data through attribute support.
7 votes -
Expand Webhook triggers
If we had the ability to choose which webhook events to subscribe per endpoint (https://suggestions.simplemdm.com/forums/204404-suggestions/suggestions/46289557-support-choosing-which-webhook-events-to-subscribe), the addition of more triggers would be valuable in automating and validating workflows.
Here are some of the possible triggers:
abm.device.removed
profile.added
profile.updated
profile.removed
application.added
application.updated
application.removed
script.added
script.updated
script.removed
script.job.run6 votes -
Expand '\n' as carriage return in script output
When running scripts via the SimpleMDM web interface, the log/history of a script run shows as a single line.
It would be convenient to be able to see multi-line output within the web interface (instead of having to copy and paste the log output into a text document and then doing a find & replace of '\n' characters in order to be able to read it).
1 vote
- Don't see your idea?