466 results found

1. Report on installed certificates

   I'd like to see SimpleMDM report on installed certificates for all device types. A common feature in other MDMs, CertificateListCommand (https://developer.apple.com/documentation/devicemanagement/certificatelistcommand) has been around since iOS 4 and macOS 10.7 (!).

   While we have other tools to report on certificates (like osquery), it's useful to have MDM as a data source as well since oftentimes installed certificates originate via profiles. Knowing certificate health within the same product has benefits, and could allow for more advanced certificate management directly in SimpleMDM.

   Important fields...
   - Certificate name
   - CA/issued by
   - Expiration
   - Current validity status
   - If possible, whether the certificate is "managed" (installed) by a MDM profile.

   And, of course, please make sure certificate data is available via the API, preferably using the existing devices endpoint.

   I'd like to see SimpleMDM report on installed certificates for all device types. A common feature in other MDMs, CertificateListCommand (https://developer.apple.com/documentation/devicemanagement/certificatelistcommand) has been around since iOS 4 and macOS 10.7 (!).

   While we have other tools to report on certificates (like osquery), it's useful to have MDM as a data source as well since oftentimes installed certificates originate via profiles. Knowing certificate health within the same product has benefits, and could allow for more advanced certificate management directly in SimpleMDM.

   Important fields...
   - Certificate name
   - CA/issued by
   - Expiration
   - Current validity status
   - If possible, whether… more

   20 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. 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

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Add Office 365 as an account provider

   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.

   20 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Extend the devices - list profiles API method to return ALL profiles that a device is assigned

   The list profiles method in the devices API endpoint only returns profiles that are directly assigned to the device; it would be very helpful to the data returned included all profiles assigned to that device, including profiles assigned through groups, etc, along with an attribute that identifies how the profile is assigned.

   •  

   20 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. iOS 14 Home screen layout profile update - Searchable VPP text filter & widgets

   iOS 14 Home screen layout profile update - Searchable VPP text filter when selecting apps & configurable widgets

   19 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Location for macOS

   Similar to how you push an app for iOS location, it would be nice to have a headless macOS app that did the same thing. Or perhaps a menu item of some sort.

   19 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Custom Attributes - Drop-down list with options

   We are using few Custom Attributes that can have only some options (like kiosk app). Having drop-down list with options will be really nice.

   Then it will allow us to set possible Attributes and help desk will just choice from drop-down list.

   Thanks David

   18 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   4 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Support choosing which webhook events to subscribe to per endpoint

   https://api.simplemdm.com/#webhooks

   The current webhook events are as follows...

   device.changed_group
   device.enrolled
   device.unenrolled
   device.lock.enabled
   abm.device.added

   Whenever any of these events occurs, the webhook endpoint is pinged. However, processing these can get particularly noisy, especially in large environments and (hopefully) as SimpleMDM adds more supported events.

   I am asking to add support for selecting which events are subscribed to per webhook endpoint. This way only events needed for a particular workflow are sent and the webhook receiver requires less work to filter out unneeded data.

   The UI could look like other SimpleMDM settings with checkboxes for each event, where by default all are selected.

   https://api.simplemdm.com/#webhooks

   The current webhook events are as follows...

   device.changed_group
   device.enrolled
   device.unenrolled
   device.lock.enabled
   abm.device.added

   Whenever any of these events occurs, the webhook endpoint is pinged. However, processing these can get particularly noisy, especially in large environments and (hopefully) as SimpleMDM adds more supported events.

   I am asking to add support for selecting which events are subscribed to per webhook endpoint. This way only events needed for a particular workflow are sent and the webhook receiver requires less work to filter out unneeded data.

   The UI could look like other SimpleMDM settings with checkboxes for each event, where by default all are… more

   •  

   18 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Custom Attributes - select data type

   Allow for the Custom Attribute to have a data type; ie; string, integer, Boolean, password/hidden, date etc

   18 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Add directory services integration (LDAP/Active Directory)

    For enterprise, integration with directory services is essential. I need to be able to target machines and devices for actions and reporting based on an assigned active directory user and/or the user's groups.

    This should include enrollment, targeting for policies, targeting for package deployment, etc.

    I see there might be some initial work being done in the Configs -> Providers menu, but as is, it is not enough to configure LDAP.

    •  

    17 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Enforce matching name and device_name fields

    Note: Due to formatting, not including the _ underscore in device name. Everything was italics.

    SimpleMDM has two name values for each device - "name" and "device name". "name" is the value used in the device list (https://a.simplemdm.com/admin/devices) and the header of a device record. "device name" is the actual hostname set locally. If the hostname changes on device, it will change in SimpleMDM on next inventory refresh. Similarly, "device name" can be edited manually in SimpleMDM and a MDM command will be issued to update it on device.

    What if "device name" changes at any point though? "name" does not update along with it. In fact, there's no way to change the "name" field at all through the web app GUI. It must be done through the API. Considering device management should be stateful, odds are this identifying name will change at some point in the future. Even more importantly, only "name" - not "device name" - is searchable from the device list.

    This disconnect between "name" and "device name" is doesn't make a whole lot of sense from a design perspective, and forces admins to use the API if they want to ensure the values match.

    I am proposing a new setting which enforces matching "name" and "device name". With the setting enabled, whenever "device name" changes, "name" updates automatically as well.

    Note: Due to formatting, not including the _ underscore in device name. Everything was italics.

    SimpleMDM has two name values for each device - "name" and "device name". "name" is the value used in the device list (https://a.simplemdm.com/admin/devices) and the header of a device record. "device name" is the actual hostname set locally. If the hostname changes on device, it will change in SimpleMDM on next inventory refresh. Similarly, "device name" can be edited manually in SimpleMDM and a MDM command will be issued to update it on device.

    What if "device name" changes at any point… more

    17 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. search devices by custom attributes or notes field information

    I would like to look up who is using the iPad. We have generally put the name in the notes field and are looking into doing a custom attribute. Neither are searchable in the current device algorithm. Can we please get something for that added?

    17 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    3 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Organize Custom Apps the same as Shared Apps

    Custom apps should behave the same way as Shared apps - allowing multiple versions to be uploaded and to have those versions displayed in a drop-down under a single app name under Assignment.

    Ideally SimpleMDM’s logic for displaying the custom app would follow what’s already in place for shared apps (which is great btw) specifically:
    • only 1 instance of the app is displayed in the Catalog by bundle ID or..?
    • the ability to select a specific version of the app in the assignment group

    17 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Assign profiles to multiple groups from the Profiles Action menu

    There's no easy way to assign a single profile to multiple groups at once. Instead, I have to go to the Groups view and click on each group I want to add the profile to, click the profile tab, click Assign Profile, find the Profile I want to add, then click the Assign button. Doing that for each group is tedious.

    Instead, I suggest the Profiles view have an option in the Action button to be able to add whichever Profiles are selected to add to Groups. I imagine the resulting view would be a list of groups with a checkboxes to select which groups to add to.

    There's no easy way to assign a single profile to multiple groups at once. Instead, I have to go to the Groups view and click on each group I want to add the profile to, click the profile tab, click Assign Profile, find the Profile I want to add, then click the Assign button. Doing that for each group is tedious.

    Instead, I suggest the Profiles view have an option in the Action button to be able to add whichever Profiles are selected to add to Groups. I imagine the resulting view would be a list of groups with a… more

    17 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Support network users

    MDM protocol has an extension called "Network User Authentication" allowing MDM to manage network users in corporate or educational environment.

    This is linked to what is sometime called shared devices or lab devices.

    Main idea is to be able to target settings to users and not devices directly.

    This mean users are provided by a central directory service (at this time it's LDAP like AD, OD or even custom LDAP, but don't forget that macOS might support something else too).

    So MDM need to be able to sync with any kind of directory services and receive "UserAuthenticate" messages from managed macOS devices.

    With this supported by the MDM, we can manage a bunch of devices in the exact same way and customize interaction based on who's behind it in real time, and we can restrict those managed settings to the targeted user environment.

    Simple example, all employees has preference pane restriction except help desk. Or all users are forbidden to add custom mail account except VIPs.

    This also help to be more efficient in IT management. All devices work the same. Your's is dead? Take anyone and work just right now. Don't wait an hour for an automated install.

    MDM protocol has an extension called "Network User Authentication" allowing MDM to manage network users in corporate or educational environment.

    This is linked to what is sometime called shared devices or lab devices.

    Main idea is to be able to target settings to users and not devices directly.

    This mean users are provided by a central directory service (at this time it's LDAP like AD, OD or even custom LDAP, but don't forget that macOS might support something else too).

    So MDM need to be able to sync with any kind of directory services and receive "UserAuthenticate" messages from managed… more

    17 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Support "Non-Removable" flag on deployed iOS Store Apps

    As noted here on the SimpleMDM blog, an option was added to iOS starting in 14.x where individual apps can be marked as "non-removable" by the administrator when being deployed.

    https://simplemdm.com/blog/mdm-ios-14-macos-11-big-sur/
    https://it-training.apple.com/tutorials/deployment/dm195

    "To prevent a user from uninstalling a managed app, mark the app as nonremovable when you assign the managed app to a user or device. Depending on your MDM solution, you might need to deselect a Removable attribute or set a nonremovable attribute. With your MDM solution, you may also be able to set this attribute on apps that are already installed on a device."

    I feel it would be a valuable feature to implement this flag so that users can still have the ability to add and remove their own apps on their managed device (which would otherwise not be possible via a restriction profile block), but are prevented from removing apps deployed by policy (Such as security apps, or authentication apps required by the company)

    As noted here on the SimpleMDM blog, an option was added to iOS starting in 14.x where individual apps can be marked as "non-removable" by the administrator when being deployed.

    https://simplemdm.com/blog/mdm-ios-14-macos-11-big-sur/
    https://it-training.apple.com/tutorials/deployment/dm195

    "To prevent a user from uninstalling a managed app, mark the app as nonremovable when you assign the managed app to a user or device. Depending on your MDM solution, you might need to deselect a Removable attribute or set a nonremovable attribute. With your MDM solution, you may also be able to set this attribute on apps that are already installed on a device."

    I feel it… more

    16 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Allow setting scope values when uploading a new Custom Configuration Profile via API

    When using the SimpleMDM portal to upload a new custom configuration profile, you are able to define a scope for the profile - targeted OS, min/max OS version, and Mac architecture.

    It would be useful to be able to define these values via the Create (POST) custom_configuration_profiles API [https://api.simplemdm.com/#create-4].

    16 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Store more information for deleted devices

    Deleted devices have very little paper trail to them shown in the web console. If we have the ability to store the custom attributes, notes and who deleted the device with the deleted devices, that would be a huge help in understanding why a specific machine was deleted without searching through other sources.

    15 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Add option to flag device as stolen - alternate default group and email alerted when a specific SN enrolls

    In a scenario when a device is stolen we can flag it as stolen in the SimpleMDM interface and have email alerts be sent to the SimpleMDM Admin's when that SN registers with the service. Additionally, it would be handy to have a separate default group for devices flagged as stolen so if the OS is reinstalled and the device re-enrolls it doesn't end up in the company's default group.

    15 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. 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 API would also be able to map users to defined roles to keep permissions low - this would apply both at creation time and updating existing admin accounts to use a different role than they currently are assigned.

    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… more

    15 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close