424 results found

1. Update/upgrade WhatsApp in Shared Apps for macOS

   The current version has now "WhatsApp (old)" as name and the logo is grey now instead of green. It also suggests downloading the new app. But I prefer to install it from the self-service app (Munki). So can you add/update it?

   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

2. API Request: Ability to upload/change icons for uploaded macOS pkgs.

   Currently in the API, only pkg uploads and changes are supported. However the ability to upload or change icons is unavailable.

   The reason this is important for us is we maintain over a dozen instances and the ability to programatically set icons for our items would drastically reduce the amount of work required for us to configure especially when we're deploying new items.

   If possible, we'd greatly appreciate the following added to the API:
   - Apps -> Create:
   - New optional argument: icon.
   - Sets icon during upload.
   - Apps -> Update:
   - New optional argument: icon.
   - Replaces current icon.
   - Apps -> List All (as well as Retrieve One):
   - List "icon" property.
   - If default/unconfigured, list None/missing
   - If present, URL to icon if applicable

   Currently in the API, only pkg uploads and changes are supported. However the ability to upload or change icons is unavailable.

   The reason this is important for us is we maintain over a dozen instances and the ability to programatically set icons for our items would drastically reduce the amount of work required for us to configure especially when we're deploying new items.

   If possible, we'd greatly appreciate the following added to the API:
   - Apps -> Create:
   - New optional argument: icon.
   - Sets icon during upload.
   - Apps -> Update:
   - New optional argument: icon.
   - Replaces current… more

   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. Add new Microsoft Teams to Shared Catalog

   Microsoft is rolling out an updated Teams experience or Mac, with a new binary that can be installed alongside the Classic teams experience. Please add the standalone installer to the shared catalog alongside the existing Teams (and possibly rename teams to Classic, like MS does?) https://go.microsoft.com/fwlink/?linkid=2249065

   13 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

4. Route SSO-only users to their account-specific SSO

   When our SSO-only users go to a SimpleMDM bookmark in their browser, they get routed to the email/password login page. Since SSO login (via SAML) requires an organization-specific sign-in page, they don't know where to go to sign in.

   A suggestion that I hope would help here would be to route a user whose account is SSO-only to their organization's SAML login page so that they can complete their sign-in flow. This could either be letting them enter their email on the existing login page or having a button on the page for "Log in via SSO" so they could enter their email there.

   Thanks for a great service!

   When our SSO-only users go to a SimpleMDM bookmark in their browser, they get routed to the email/password login page. Since SSO login (via SAML) requires an organization-specific sign-in page, they don't know where to go to sign in.

   A suggestion that I hope would help here would be to route a user whose account is SSO-only to their organization's SAML login page so that they can complete their sign-in flow. This could either be letting them enter their email on the existing login page or having a button on the page for "Log in via SSO" so they could… more

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

5. add the ability to preview Welcome Screens as they are created

   Rather than have to iterate changes to Welcome Screens with real hardware, it would be nice to have a generated preview in-browser as part of Enrollments > {enrollment_name} > Welcome Screen.

   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

6. Add Apple Silicon Dialpad App

   https://www.dialpad.com/download/

   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

7. Notifications for nodes running low on disk space

   Notifications for nodes running low on disk space

   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

8. Allow devices to be marked as unmanaged

   Another idea to borrow from Jamf Pro. Please consider allowing SimpleMDM customers to mark devices as unmanaged in order to keep them for historical or data purposes without them actively being under management and NOT taking up a license. An unmanaged device would keep the same config, but not have the ability to interact with MDM moving forward. No profile installs, polling for device info, etc. It is a record stuck in time. Devices should be able to move freely between managed/unmanaged through the GUI and API.

   As it today, every device which exists in a SimpleMDM tenant takes up a license. No matter how long ago the device was enrolled, when it last checked in, etc. a license is still consumed. Though I understand the advantage on the PDQ side for billing and revenue purposes, it would be useful as a customer to be able to keep devices within SimpleMDM as unmanaged without having to pay for the corresponding license. As best I can tell, when a device in removed it's data is not also removed. I've tested this by removing a device and re-enrolling it. Immediately after re-enrollment the old data is still present, even before MDM has had a chance to report back. My theory is when a device is removed it's simply tagged/marked as removed, with all other associated data remaining in the database. If that's the case, it's a zero or neglible cost to allow customers to mark devices as unmanaged since the only difference is whether the device is visible and requesting regular MDM actions.

   The only other options are for customers to buy more licenses (probably what PDQ prefers) or run regular cleanup to remove old/stale/retired/archived devices. While MDM is not and should not be an inventory, there are common operational and compliance needs to keep MDM device records around for longer even for devices which aren't being managed. So tl;dr - Allow devices to be marked as managed and unmanaged.

   Another idea to borrow from Jamf Pro. Please consider allowing SimpleMDM customers to mark devices as unmanaged in order to keep them for historical or data purposes without them actively being under management and NOT taking up a license. An unmanaged device would keep the same config, but not have the ability to interact with MDM moving forward. No profile installs, polling for device info, etc. It is a record stuck in time. Devices should be able to move freely between managed/unmanaged through the GUI and API.

   As it today, every device which exists in a SimpleMDM tenant takes up… more

   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…)
   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. Reject enrollments for unsupported macOS versions when using SAML

   I am requesting SimpleMDM add guards for ADE where a macOS device is under 10.15. Copying directly from enrollment authentication config...

   "OSes prior to macOS 10.15 and iOS 13 using Automated Enrollment and all devices enrolled with Apple Configurator do not support SAML authentication and will not be authenticated. Optionally enroll them in a less secure initial device group."

   A helpful setting for sure since it means a device can be dropped into a group with no access to organization profiles, packages, or secrets. However, the device is still allowed to enroll and takes up a license. If that Mac were lost or stolen for example, there's now one less way to stop it from being used.

   My suggestion is to implement one of these options...
   - Fall back to legacy basic (LDAP) auth for pre-10.15 devices when SAML is configured. In this way the old style dialog will appear with no way to ever successfully to auth. A potential attacker or other security risk now has one less way to enroll or use the device. This is configurable in Jamf Pro.
   - Reject the enrollment altogether, denying the opportunity to enroll.

   I am requesting SimpleMDM add guards for ADE where a macOS device is under 10.15. Copying directly from enrollment authentication config...

   "OSes prior to macOS 10.15 and iOS 13 using Automated Enrollment and all devices enrolled with Apple Configurator do not support SAML authentication and will not be authenticated. Optionally enroll them in a less secure initial device group."

   A helpful setting for sure since it means a device can be dropped into a group with no access to organization profiles, packages, or secrets. However, the device is still allowed to enroll and takes up a license. If that Mac… more

   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

10. Sort the Scripts -> Jobs -> History tab by newest to oldest by default

    Right now, the sorting is by name (I think?) which is not useful. It would be great to show the most recently queued jobs in the history first by default.

    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

11. Allow SimpleMDM to release devices in ABM/ASM

    Allow SimpleMDM to release devices without having to sign in to Apple Business Manager. This feature is enabled by default when you add an MDM server in ABM/ASM. You can remove this feature by deselecting the option for any new or existing MDM servers you created.

    But SimpleMDM has not implemented this feature yet. Would be nice to automate the decommissioning process of the devices.

    https://support.apple.com/en-sg/guide/apple-business-manager/axmec4d28461/web

    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

12. Allow entry of Custom Integers for Software Update Delay Fields in Restrictions Payload

    Currently we only have the option to choose from predefined options in the dropdown list as shown below.
    Please add the ability to add a custom ineger up to the maximum allowed by Apple.

    •  

    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

13. Add support for ZIP and XIP as well as DMG

    A fair number of apps are distributed as ZIPs (and one prominent app uses XIPs) instead of DMGs. It would be convenient to be able to upload these as is, instead of having to locally convert them to DMGs first $(unzip App.zip && hdiutil create -format ULMO -o App.dmg -srcfolder App.app)

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

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

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

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

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

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

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