415 results found

1. Allow before/after (un)installation script overrides for shared apps

   This would enable one to benefit from shared auto-updating apps while applying useful improvements such as /Applications/Docker.app/Contents/MacOS/Docker --unattended --install-privileged-components.

   5 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

   Submit Rating

2. Add AWS VPN Client to the list of managed applications

   Adding a picture of ducks discussing the idea to improve chances of upvoting.

   Thanks!

   •  

   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  ·  Edit…  ·  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

   Submit Rating

3. Report on profile status - pending, installed, failed

   SimpleMDM currently only surfaces profile assignment in the main profiles UI. To see the status of a specific profile on a device an admin must navigate to a device record. What information isn't readily available is the status of a profile. Even if it's assigned to 100 devices, there's no way to tell how many of those devices the profile successfully installed.

   Specifically asking...
   - Add three columns to the view at /profiles in the UI - installed, pending, failed.
   - In the profiles and custom profiles API endpoints include data about these status as well.

   The major driver behind this feature request is compliance reporting. Although we may have MDM configured to do a certain thing, as a SimpleMDM customer there's no way to tell in a programmatic or at a glance way if that configuration profile was actually delivered. This will become even more important with DDM not making declaration data available locally. I want to know from a compliance standpoint if my endpoints are actually in good standing without having to poll them locally (or in addition to).

   SimpleMDM currently only surfaces profile assignment in the main profiles UI. To see the status of a specific profile on a device an admin must navigate to a device record. What information isn't readily available is the status of a profile. Even if it's assigned to 100 devices, there's no way to tell how many of those devices the profile successfully installed.

   Specifically asking...
   - Add three columns to the view at /profiles in the UI - installed, pending, failed.
   - In the profiles and custom profiles API endpoints include data about these status as well.

   The major driver behind… 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…)
   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

   Submit Rating

4. Include the Enrollment group in Device Details section

   It would be helpful to include the Enrollment group in Device Details section

   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 →
   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

   Submit Rating

5. New notification options

   I'd love for a lot more notification options. Given SimpleMDM's position on the device already, it hopefully shouldn't be too heavy of a lift.

   • New User added
   • User priv changes
   • OS update skipped
   • Device visible (after being offline)

   This is off the top of my head, but I'm sure I could come up with quite a few more given some time.

   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  ·  Edit…  ·  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

   Submit Rating

6. Allow a scheduled rotation of auto-admin passwords

   I'd like to see the ability for SimpleMDM to auto-rotate admin passwords on a specified schedule. Right now that task is only completed by the UI or an API script. The UI clicking is impossible with 1000s of machines and scripting it with an API call takes hours to run. Having an automated schedule inside the UI to auto-rotate every month or so would remove the chore of password rotation.

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

   Submit Rating

7. Enrollment Setting - Unassign Profiles at Re-Enrollment

   We heavily utilize individually assigned profiles for Macs. There are also a few default profiles assigned via group. When a new out-of-box Mac is being enrolled for the first time only those default profiles are installed (around 5). Profiles are installed quickly and reliably. Later on during provisioning our configuration management tool handles installing other required per device profiles.

   However, when a Mac from stock is being re-enrolled to be used by another person, every previously assigned profile is installed at setup assistant. Since in my case those individually assigned profiles are usually per user, team, department, etc. and no longer pertain to the new person using the Mac, the device configuration is functionally incorrect. I'd prefer if on re-enrollment they weren't assigned at all. With a significant number of profiles, there's also no guarantee they will all be installed by the time the user hits the desktop, and since MDM has no concept of priority delivery, oftentimes those individually assigned per device profiles from the last user get installed before the default ones.

   The current workaround is to use a webhook to watch for lock or unenrolled events and use the API to programmatically unassign profiles. I'd prefer not to though. I'm specifically asking for a setting, globally or per enrollment, to unassign every profile except those assigned to a group at re-enrollment.

   We heavily utilize individually assigned profiles for Macs. There are also a few default profiles assigned via group. When a new out-of-box Mac is being enrolled for the first time only those default profiles are installed (around 5). Profiles are installed quickly and reliably. Later on during provisioning our configuration management tool handles installing other required per device profiles.

   However, when a Mac from stock is being re-enrolled to be used by another person, every previously assigned profile is installed at setup assistant. Since in my case those individually assigned profiles are usually per user, team, department, etc. and no… 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 →
   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

   Submit Rating

8. Add a Comments Field to Login/Background Item Management Profile

   Some of the Rule Type values (Team IDs, for example) for the Login and Background Item Management are a bit abstract, and it would be useful to have a comment/description field added to allow an administrator to describe in plain language what a the Rule Type value applies to.

   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 →
   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

   Submit Rating

9. Filtering out data during Device Export

   Have the ability to filter out certain data points when doing a Device Export

   4 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

   Submit Rating

10. Add the Homebrew package to shared Apps

    Homebrew is now distributed as a pkg: https://github.com/Homebrew/brew/releases/tag/4.1.13

    I'm distributing this but it would be nice if it was automatically updated for me :D

    5 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

    Submit Rating

11. Implement "force password change when the user authenticates"

    As per https://support.apple.com/en-ca/guide/deployment/dep4d6a472a/web, Apple has an API for forcing a user password change. This is useful when updating password policy - passwords that met the old policy but no longer meet the new policy are not evaluated and forced to change. This setting, however, would make it so.

    6 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

    Submit Rating

12. Auto-admin password complexity settings

    For the auto-admin password generation done by SimpleMDM, it'd be preferable to be able to manage the level of password complexity when the password is generated. Environments can have different password policy rules that all accounts, including MDM generated, need to abide by. The Dude abides.

    Password storage apps like 1Password and Keeper offer, at minimum, password length, use of numbers, and use of special characters. See attached.

    •  

    •  

    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 →
    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

    Submit Rating

13. Nested Custom Attributes

    Description: It would be extremely useful to have the ability to nest custom attributes in SimpleMDM. This feature would allow administrators to create custom attributes that reference or depend on other custom attributes, enabling dynamic and interconnected data management.

    Use Case: For instance, suppose an organization has a custom attribute called "munkimanifestdepartement" that is a dropdown value in the DEP (Device Enrollment Program) welcome screen. The organization also wants to create another custom attribute called "munkimanifest" that includes the department value selected in "munkimanifestdepartement" along with additional static text. By nesting the custom attribute "munkimanifestdepartement" within the "munkimanifest" attribute, the organization can automatically generate the munki manifest value based on the selected department.

    Benefits:
    1. Automation: Nesting custom attributes would automate the process of generating complex values by dynamically incorporating data from other attributes.
    2. Data Consistency: By linking attributes together, administrators can ensure that related data remains consistent and up to date.
    3. Simplified Management: Instead of manually updating multiple attributes, nested custom attributes would allow for easier management and maintenance of interconnected data.

    Implementation: The addition of a feature to nest custom attributes in SimpleMDM could be achieved by introducing a syntax or placeholder system that references other custom attributes within the attribute value. Administrators could use placeholders or variables to dynamically include the value of other attributes when defining the value of a custom attribute.

    Overall, the ability to nest custom attributes in SimpleMDM would enhance data management capabilities by enabling automation, ensuring data consistency, and simplifying attribute management.

    Description: It would be extremely useful to have the ability to nest custom attributes in SimpleMDM. This feature would allow administrators to create custom attributes that reference or depend on other custom attributes, enabling dynamic and interconnected data management.

    Use Case: For instance, suppose an organization has a custom attribute called "munkimanifestdepartement" that is a dropdown value in the DEP (Device Enrollment Program) welcome screen. The organization also wants to create another custom attribute called "munkimanifest" that includes the department value selected in "munkimanifestdepartement" along with additional static text. By nesting the custom attribute "munki… more

    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  ·  Edit…  ·  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

    Submit Rating

14. Regex Rules for Custom Attribute Validation

    Description: It would be highly beneficial to have the ability to use regular expressions (regex) to validate user-defined custom attributes in SimpleMDM. This feature would allow administrators to set specific rules and patterns that user inputs must adhere to, ensuring data accuracy and consistency.

    Use Case: For example, suppose an organization has a custom attribute for employee IDs. By implementing regex rules, the administrator can define that the employee ID must follow a specific format, such as a combination of letters and numbers. Any user input that does not match the defined regex pattern would be flagged as invalid, preventing incorrect or inconsistent data from being entered.

    Benefits:
    1. Data Accuracy: Regex rules will help enforce consistent data entry by ensuring that user inputs meet the specified patterns or formats.
    2. Prevent Errors: By validating user inputs against regex rules, potential errors or typos can be caught and corrected before they cause issues downstream.
    3. Customization: Administrators can tailor regex rules to match their organization's specific requirements, enabling greater flexibility and control over data validation.

    Implementation: The addition of a regex rule field within the custom attribute settings would allow administrators to define the pattern that user inputs must match. SimpleMDM could then validate the input against the regex rule and provide immediate feedback if the input is invalid.

    Overall, the inclusion of regex rules for custom attribute validation would enhance the data integrity and usability of SimpleMDM, providing administrators with greater control over user or admin inputs.

    Description: It would be highly beneficial to have the ability to use regular expressions (regex) to validate user-defined custom attributes in SimpleMDM. This feature would allow administrators to set specific rules and patterns that user inputs must adhere to, ensuring data accuracy and consistency.

    Use Case: For example, suppose an organization has a custom attribute for employee IDs. By implementing regex rules, the administrator can define that the employee ID must follow a specific format, such as a combination of letters and numbers. Any user input that does not match the defined regex pattern would be flagged as invalid, preventing… more

    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  ·  Edit…  ·  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

    Submit Rating

15. Devices API - Create - Extend method to include optional params for DEP device ID and device name

    When creating a device using the Devices API create method (https://api.simplemdm.com/#devices), there are only two parameters that can be passed to it, 'name' and 'group_id'.

    It would be very helpful, especially for devices that are expected to go through automated device enrolment, if we could pass a DEP device ID parameter to it so that a DEP device that is not yet enrolled will automatically be assigned to the nominated device group.
    If the DEP device id parameter is assigned, then the response probably shouldn't include an enrolment URL, as this param should indicate the device is expected to automatically enrol.

    Additionally, it would be helpful if we could also pass a device name parameter to the create method so that when the device does enrol through automated enrolment, the device name will be assigned to it.

    These same params should also be extended to the update method.

    When creating a device using the Devices API create method (https://api.simplemdm.com/#devices), there are only two parameters that can be passed to it, 'name' and 'group_id'.

    It would be very helpful, especially for devices that are expected to go through automated device enrolment, if we could pass a DEP device ID parameter to it so that a DEP device that is not yet enrolled will automatically be assigned to the nominated device group.
    If the DEP device id parameter is assigned, then the response probably shouldn't include an enrolment URL, as this param should indicate the device is expected… more

    •  

    6 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

    Submit Rating

16. Device Groups API - add methods

    The Device Groups API does not have the following methods:
    create, update, remove/delete, it would be very helpful if this endpoint could have those methods added, along with various options such as:

    create: parameters "name" (required), "lock_screen_message" (optional), and "track_device_location" (optional, default False)

    update: parameters "name" (optional), "lock_screen_message" (optional), and "track_device_location" (optional)

    delete: parameters: "device_group_id"

    Also, the clone method does not currently take any parameters that would allow device group settings to be configured, it would be helpful if the clone method was updated to allow the use of these parameters:

    "name" (required), "lock_screen_message" (optional), and "track_device_location" (optional, default False)

    25 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

    Submit Rating

17. Add blackmagic Resolve

    Add DaVinci aka BlackMagic Resolve

    https://homebysix.github.io/autopkg-dupe-tracker/timsutton-recipes/Blackmagic/DaVinciResolve18.munki.recipe.html

    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  ·  Edit…  ·  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

    Submit Rating

18. Add username field to `device.enrolled` webhook event

    The goal is to have a username field in the device.enrolled webhook event.

    This field would be populated using the the custom attribute defined in the "Username custom attribute" setting in the Automated Enrollment Authentication section.

    In our use case, a user will be prompted to auth using Okta during Automated Device Enrollment (ADE). The username that is returned by Okta would be part of the webhook event payload. We use the username and device serial number to help with automating other internal processes to help determine which user is assigned to which device.

    This could be covered by https://suggestions.simplemdm.com/forums/204404-suggestions/suggestions/46831099-control-webhook-data, but I wanted to call this out more specifically.

    The goal is to have a username field in the device.enrolled webhook event.

    This field would be populated using the the custom attribute defined in the "Username custom attribute" setting in the Automated Enrollment Authentication section.

    In our use case, a user will be prompted to auth using Okta during Automated Device Enrollment (ADE). The username that is returned by Okta would be part of the webhook event payload. We use the username and device serial number to help with automating other internal processes to help determine which user is assigned to which device.

    This could be covered by https://suggestions.simplemdm.com/forums/204404-suggestions/suggestions/46831099-control-webhook-data… more

    6 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

    Submit Rating

19. More granularity on the SimpleMDM menu bar icon...

    So, we've just rolled out Nudge and have used the SimpleMDM agent to do so. And now I'm being grumbled at about the Managed Software Centre Icon taking up valuable menu bar space...

    I appreciate I can kill it via the UI - but it's a bit all or nothing, and when we start adding apps to self-service, the menu bar app seems as good a place as any to direct our end users.

    So - can we set icon visibility per assignment group?

    I think what I'm basically saying is if all apps are managed, and there's no self-service then hiding the menu bar icon totally makes sense, but allowing it to appear when you DO have self-service items makes sense (to me)

    So, we've just rolled out Nudge and have used the SimpleMDM agent to do so. And now I'm being grumbled at about the Managed Software Centre Icon taking up valuable menu bar space...

    I appreciate I can kill it via the UI - but it's a bit all or nothing, and when we start adding apps to self-service, the menu bar app seems as good a place as any to direct our end users.

    So - can we set icon visibility per assignment group?

    I think what I'm basically saying is if all apps are managed, and there's no self-service… more

    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 →
    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

    Submit Rating

20. Record administrator logins in Logs

    Currently, there is no visibility in the logs when an admin session is started from a login. We'd like to see log in and log out for at least "local" SimpleMDM accounts if not IdP initiated sessions as well, populated into the admin namespace. It would be helpful if the logs contained the account email, IP address they are logging in from, and the usual timestamp / "At" value. A user agent value would be a bonus but it's understandable if that's not available.

    25 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

    Submit Rating