Currently the API has a customconfigurationprofiles endpoint (https://simplemdm.com/docs/api/#custom-configuration-profiles) which can be used to create, modify, and assign/unassign custom profiles. However, there is on way to manage other profile types via the API.

Say I create a FileVault profile in the web app and then want to assign the profile only to specific Macs using the API. There's not a specific group or device I want to manually assign. Instead I only want to assign to specific endpoints programmatically using a config management tool like Chef or Ansible. Since the profile is not "custom" I am unable to.

I am asking regular, non-custom profiles have these actions added to the API.

• Assign to device
• Unassign from device
• Assign device group
• Unassign from device group

Just like is currently possible for custom profiles - https://simplemdm.com/docs/api/#assign-to-device I understand there's complexity with creating these profiles through the API and thus this request does not cover that scope. Thank you!

Currently device search only supports device name, serial number, IMEI, MAC, and phone number.

Scenarios where search doesn't return the results I need:
- When I need to search by a custom attribute. For example, say I want to return all devices where the username attribute is "nathaniel.strauss". I am unable to since those attributes are not exposed in search. This is a common ask - "How many devices does x have?" The same holds true for any custom attribute set from SAML assertion - team, department, etc.
- When the device name (SimpleMDM defined) doesn't match the Device Name (MDM reported). For example, the listed name is "MacBook Air" but the actual on device name is "Arts-Building-$SerialNumber" SimpleMDM is unable to return the device by searching "Arts".
- Enrollment status. Though "Status" is a column in list view it is not searchable.
- Last seen. Slightly more complex. SimpleMDM is unable to return devices not seen (or seen) within a specific time period.

Given the values are already present in the database, I'm asking search either be configurable to allow any device attribute. If it's easier or more reasonable to ask for a smaller solution I would want these attributes prioritized to be searchable. Thank you!

• All custom attributes
• Device name
• Processor arch (Apple silicon v Intel)
• OS version
• Enrollment status
• FDE status
• SIP status
• Secure boot level
• Secure boot external level

When you go to the enrollment area of SimpleMDM and choose the enrollment method, in my case, the SimpleMDM Automated Enrollment using DEP. It will list ALL of the currently sync'd devices from ABM. This is a HUGE list and you cannot sort it or filter it whatsoever. I would like the option to filter by status, color, model, etc. as well as sort them all alphabetically.

An even bigger improvement for this requested feature would be if you add checkboxes to each line item so you can bulk update them to assign to a specific group, etc. This makes it much easier once you turn on and enroll the devices because they will start getting all of your group profiles and set themselves up immediately.

The only alternatives currently without these features is to manually type the last 4-5 digits of every device serial # and set each device pending enrollment to the correct group it should join, OR set the default join group, and enroll specific devices that should belong to that group, then change it and enroll the next batch, etc.

I am trying to load up packages for Adobe Suite on an Feature Restricted License. So no cloud access. The total Suite size is around 28.5 GB. I am not necessarily suggesting allowing for the full suite to be uploaded in one go. I have divided out the installs and the largest install is After Effects at 5.9GB. So if the file size could be adjusted to 6000MB that would be sufficient. Photoshop is 5.5 GB, Premiere is 4.15 GB, Character is 4.08 GB. With the removal of MAC OS server support I am hopeful to transition this to be automated with SimpleMDM.

The Remote Desktop Enable API - https://simplemdm.com/docs/api/#enable-remote-desktop - currently returns an HTTP 400 response if the device the API is called against already has this enabled. The Disable API returns an HTTP 202 error regardless of whether the feature has not been disabled or has been disabled.

I'm not entirely sure I see the value in the Enable API returning an HTTP 400 response when a device already has it enabled. A response that returns a relevant HTTP 20x value makes more sense in this instance because the setting has already been enabled. An HTTP 400 response only makes sense if the request from the API client is genuinely bad, as per the Mozilla developer documentation: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400

Please implement a response code of HTTP 202 in the response to the Remote Desktop Enable API if the setting is already enabled.