458 results found

1. Add device EID from DeviceInformationResponse.QueryResponses.ServiceSubscriptionProperty command

   Hello,

   as part of eSIM distribution it will be very nice to have EID of the devices accessible via API in device details (adding EID to portal will be also nice).

   Can you please add EID to each device from MDM command (this command is already in use by SimpleMDM for other data) https://developer.apple.com/documentation/devicemanagement/deviceinformationresponse/queryresponses/servicesubscriptionproperty

   Thank you David.

   3 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…)
   completed  ·  0 comments  ·  Delete…  ·  Admin →

2. Dynamic Attribute Groups

   Create dynamic group (Application and/or Device groups) scheme based on device attribute (model, apps installed, OS version, Public IP, last reboot or custom script result) See screenshot for attributes examples.

   •  

   8 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 →
   completed  ·  AdminEric McCann (Admin, SimpleMDM) responded

   Dynamic Groups are now available in the new Groups interface (currently in Preview). Sign up here to have the preview enabled on your account.

3. Add Sublime Merge to shared apps

   There is precedent for this, as an old Intel-only version of SourceTree is in the shared app library.

   3 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…)
   completed  ·  0 comments  ·  Delete…  ·  Admin →

4. Support more API profile query strings

   To get information about a custom profile through the API the only option is to list them all and then filter out the required data.

   https://api.simplemdm.com/#custom-configuration-profiles

   On a SimpleMDM instance with 100+ profiles, requesting a single page of profiles takes a very long time.

   curl https://a.simplemdm.com/api/v1/custom_configuration_profiles?limit=100 \
     -u ${API_KEY}:
   

   Running the above command takes around 20-30 seconds. However, if there were URL parameters available to map to profile attributes - ID, name, identifier, etc. - the API could return only the one or subset of profiles requested, in turn improving performance. It shouldn't take 30 seconds to return data about a single profile.

   I'm asking for a few things here...
   1. Add parameters in order to refine the profiles query. For example, https://a.simplemdm.com/api/v1/custom_configuration_profiles?limit=100&attributes.name=my.amazing.profile&id=4814&attributes.bundle_identifier=com.simplemdm.is.cool Any attribute returned by the API should be queryable. Having wildcard/like, greater than, less than, etc. operators a bonus as well, but not required.
   2. Support the above for both custom and regular profiles.
   3. (Optional) Optimize API performance for profiles lookup in general. Maybe there's a better way to query the database?

   To get information about a custom profile through the API the only option is to list them all and then filter out the required data.

   https://api.simplemdm.com/#custom-configuration-profiles

   On a SimpleMDM instance with 100+ profiles, requesting a single page of profiles takes a very long time.

   curl https://a.simplemdm.com/api/v1/custom_configuration_profiles?limit=100 \
     -u ${API_KEY}:
   

   Running the above command takes around 20-30 seconds. However, if there were URL parameters available to map to profile attributes - ID, name, identifier, etc. - the API could return only the one or subset of profiles requested, in turn improving performance. It shouldn't take 30 seconds to return data about… more

   8 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 →
   completed  ·  AdminEric McCann (Admin, SimpleMDM) responded

   Marking this as completed to give voters their votes back but we will continue working on optimizations. Please feel free to submit new suggestions if there is something more specific you'd like to see.

5. Add Tunnelblick 3.8.8c to the catalog

   Update the Tunnelblick app to the latest release (v3.8.8c)

   3 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…)
   completed  ·  0 comments  ·  Delete…  ·  Admin →

6. Report on Rapid Security Response versions

   Apple is adding a new update type to macOS called Rapid Security Responses. These updates change the build version, but not the OS version reported. Instead, the new ProductVersionExtra (sw_vers) and SupplementalOSVersionExtra (MDM query) keys are returned to denote a specific supplemental version only when a RSR is installed. If no RSR is installed the key is not present. Similarly, when using MDM query (simulated with /usr/libexec/mdmclient QueryDeviceInformation) BuildVersion is unchanged, but SupplementalBuildVersion has the correct RSR build.

   $ sw_vers
   ProductName: macOS
   ProductVersion: 13.3
   ProductVersionExtra: (a)
   BuildVersion: 22E7752300f
   

   $ /usr/libexec/mdmclient QueryDeviceInformation
   {
     BuildVersion = 22E5230e;
     OSVersion = "13.3";
     SupplementalBuildVersion = 22E7752300f;
     SupplementalOSVersionExtra = "(a)";
   };
   

   https://support.apple.com/guide/deployment/rapid-security-responses-dep93ff7ea78/web

   Please update SimpleMDM to report on installed RSR version and build when present.

   Apple is adding a new update type to macOS called Rapid Security Responses. These updates change the build version, but not the OS version reported. Instead, the new ProductVersionExtra (sw_vers) and SupplementalOSVersionExtra (MDM query) keys are returned to denote a specific supplemental version only when a RSR is installed. If no RSR is installed the key is not present. Similarly, when using MDM query (simulated with /usr/libexec/mdmclient QueryDeviceInformation) BuildVersion is unchanged, but SupplementalBuildVersion has the correct RSR build.

   $ sw_vers
   ProductName: macOS
   ProductVersion: 13.3
   ProductVersionExtra: (a)
   BuildVersion: 22E7752300f
   

   $ /usr/libexec/mdmclient QueryDeviceInformation
   {
     BuildVersion = 22E5230e;
     OSVersion = "13.3";

   … more
   8 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…)
   completed  ·  0 comments  ·  Delete…  ·  Admin →

7. Update Tunnelblick to the latest release

   Update the Tunnelblick app to the latest release (v3.8.8b)

   3 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…)
   completed  ·  0 comments  ·  Delete…  ·  Admin →

8. Support for Munki installer_type "nopkg"

   Munki has a pkginfo key for the installer type "nopkg". In a self-hosted Munki environment, this allows pkginfo files to be added to a repository that do not have an associated .pkg or .dmg file. You can read the Munki Project docs on the feature here: https://github.com/munki/munki/wiki/nopkgs

   This has a variety of uses, because it allows Munki to be used as a general script execution tool. An admin can use any of Munki's installation conditions (package receipt, installs array, installcheck_script, or OnDemand) to then run a pre or postinstall script embedded in the pkginfo.

   One example of how this is used is the venerable PrinterGenerator tool, which generates nopkg-style pkginfo files to enable printers to be installed and uninstalled via Managed Software Center.

   https://github.com/kevinmcox/PrinterGenerator

   Combined with Custom Attributes, nopkg support has the potential to greatly expand on the script execution capabilities offered to a SimpleMDM admin well beyond the current Scripts/Jobs feature.

   Munki has a pkginfo key for the installer type "nopkg". In a self-hosted Munki environment, this allows pkginfo files to be added to a repository that do not have an associated .pkg or .dmg file. You can read the Munki Project docs on the feature here: https://github.com/munki/munki/wiki/nopkgs

   This has a variety of uses, because it allows Munki to be used as a general script execution tool. An admin can use any of Munki's installation conditions (package receipt, installs array, installcheck_script, or OnDemand) to then run a pre or postinstall script embedded in the pkginfo.

   One example of how this is… more

   26 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…)
   completed  ·  0 comments  ·  Delete…  ·  Admin →

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

   24 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 →
   completed  ·  AdminEric McCann (Admin, SimpleMDM) responded

   This functionality is now available with Dynamic Groups (currently in Preview). This update also adds a Groups tab to the Device Details, Profile Details, and App Details pages to easily view/manage object assignments. Sign up here to have the preview enabled on your account.

10. Support macOS 14 Software Update Enforcement

    macOS 14 adds some sort of software update enforcement capability. While the UI is unknown the MDM parts have been outlined here: https://developer.apple.com/documentation/devicemanagement/softwareupdateenforcementspecific?changes=latest_minor&language=objc

    Please support this ASAP so we can test the UI and functionality.

    1 vote

    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…)
    completed  ·  0 comments  ·  Delete…  ·  Admin →

11. I'd love to see tags implemented as a device organizational tool.

    Right now we have groups. But device groups is only one way to view your fleet. I'd love if I could also assign tags to devices. Ideally multiple tags. This way I could have tags for things like "remote" or "customer service" or "need2retire". Then I could use a tag or combination of tags to isolate a special group of devices.

    Thanks

    10 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 →
    completed  ·  AdminEric McCann (Admin, SimpleMDM) responded

    While not specifically tags, this functionality is now achievable with Dynamic Groups (currently in Preview). Sign up here to have the preview enabled on your account.

12. ability to allow admin to decide if end user can or cannot control their date and time zone settings

    For some users, we want to allow them to control time zone while for others we want to lock it down. It'd be nice to have the option.

    1 vote

    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 →
    completed  ·  AdminEric McCann (Admin, SimpleMDM) responded

    This is available using the "Force automatic time and date" option in the Restrictions profile.

13. Manage Munki pkginfo settings via API

    Add API Endpoints to enable management of the pkginfo settings for an app via the API. This would allow us to manage keys as part of our automation process

    1 vote

    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 →
    completed  ·  AdminEric McCann (Admin, SimpleMDM) responded

    This is available: https://api.simplemdm.com/#update-munki-pkg-info

14. Respect local time zone of iOS devices when applying a software update window

    Currently, the software update window is a singular entity, which means some units in Europe would be updating in the middle of the day for units in the USA. Implementing a method to either auto-detect local time of the units or specify a time zone in the profile would help solve this.

    1 vote

    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…)
    completed  ·  0 comments  ·  Delete…  ·  Admin →

15. Update multiple custom attributes via API

    Currently only one custom attribute can be updated per API call either for a single device or device group.

    https://api.simplemdm.com/#set-value-for-device
    https://api.simplemdm.com/#set-value-for-group

    Say I want to set multiple custom attributes within a single workflow. I need to make as many API calls as there are attributes to update. In my recent work that's four calls which could've been one. This also simplifies developing with the API - don't have to iterate through values along with grokking associated return statuses.

    I'm requesting the functionality to update multiple custom attributes with one API call.

    PUT https://a.simplemdm.com/api/v1/devices/{DEVICE_ID}/custom_attribute_values

    Remove attribute name from endpoint URL and move to the request body. Multiple attributes can then be defined for devices or groups. Something like...

    {
    "username": "tobias.funke",
    "role": "therapist",
    "team": "natural good-time family band solution",
    "department": "musical theater"
    }

    Thank you for considering!

    Currently only one custom attribute can be updated per API call either for a single device or device group.

    https://api.simplemdm.com/#set-value-for-device
    https://api.simplemdm.com/#set-value-for-group

    Say I want to set multiple custom attributes within a single workflow. I need to make as many API calls as there are attributes to update. In my recent work that's four calls which could've been one. This also simplifies developing with the API - don't have to iterate through values along with grokking associated return statuses.

    I'm requesting the functionality to update multiple custom attributes with one API call.

    PUT https://a.simplemdm.com/api/v1/devices/{DEVICE_ID}/custom_attribute_values

    Remove attribute name from endpoint URL and… more

    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…)
    completed  ·  0 comments  ·  Delete…  ·  Admin →

16. API support for enabling/disabling Bluetooth of an iOS device

    I have an automated process to configure enrolled devices using SimpleMDM API, and recently there is a need to enable/disable Bluetooth depending on the device groups, which is currently not available for the API.
    I understand that I can use the restrictions profile to prevent supervised devices from changing Bluetooth settings, and I can enable/disable BT from the Devices page, but it would be great if SimpleMDM can add this ability to the API, so I can integrate it into my automated process.

    3 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 →
    completed  ·  AdminEric McCann (Admin, SimpleMDM) responded

    This is now supported: https://api.simplemdm.com/#enable-bluetooth

17. Add "Run Script" option to Actions menu

    A “Run Script” option in the Actions menu on both individual devices and any selected devices from a listing would be very helpful. Ideally, clicking it would pop you into the create job UI and pre-populate the “Run on” field with either that one device or any selected devices. This would speed up creating script jobs especially for multiple machines.

    2 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…)
    completed  ·  0 comments  ·  Delete…  ·  Admin →

18. Support RemovableSystemExtensions for System Extension policies

    In Monterey Apple added the RemovableSystemExtensions key to com.apple.system-extension-policy which is required to enable scripted uninstalls of system extensions.

    9 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 →
    completed  ·  AdminEric McCann (Admin, SimpleMDM) responded

    A "Removable" checkbox option has been added to the System Extensions profile UI to mark each extension as removable (or not). Default state is not removable.

19. Add Enrollment Date to API

    The enrollment date would be handy to pull via the API

    7 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 →
    completed  ·  AdminEric McCann (Admin, SimpleMDM) responded

    Enrollment date has been added to the Device Details page and to the Devices API.

20. Add a Log tab to the device detail view

    When viewing the Device Details, having a Log tab to have just the log entires for that device readily available would be great. Currently I have to copy the SN, click on the Logs view, paste the serial number and then if I want more device details I have to go back to the device detail.

    Having a log view of just that devices activity in the device detail would keep all the device details in one location.

    9 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…)
    completed  ·  0 comments  ·  Delete…  ·  Admin →