420 results found

1. Support self-enrollment using directory service credentials

   Provide for directory service (AD et al) user authentication information to be used for self-enrollment of devices. The authenticated user information should also be written to the device record so we know that user is tied to the enrolled device.

   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…)
   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
   completed  ·  SimpleMDM responded

   Please see our authentication options under enrollments. If you have a particular use case that is not supported by our current implementation, please create a new ticket with specific information so that we may keep track of the request.

2. macOS install VPP apps on device level
   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…)
   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
   completed  ·  SimpleMDM responded

   This option can now be set under Apps > VPP > Settings.

3. tvOS - Managed OS Updates

   With tvOS 12 adding support for managed OS updates (https://simplemdm.com/2018/06/15/apple-mdm-features-ios-12-macos-10-14/), it would be great if the Install Update icon method could be implemented for tvOS devices (like it currently is for iOS devices in the Device Details page)

   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 →
   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. Enable deploying apps via the "Managed Update" Munki manifest functionality

   I want to be able to update apps on machines enrolled in SimpleMDM without installing those apps, through the SimpleMDM Munki Integration, so that I can patch vulnerabilities on certain machines, but without targeting those machines directly.

   This reduces the amount of work I need to do, and if in the future, an employee installs an older, vulnerable version SimpleMDM will update that app, without me installing it on everyone.

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

   Managed Updates has been added as an install type for Munki app assignment groups.

5. Add Notion to shared apps

   https://www.notion.so/help/notion-for-desktop

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

7. iOS 8 Support

   Provide iOS 8 support upon the release of the new operating system with the new features including renaming of devices, blocking the setup of Restrictions and device backup queries.

   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 →
   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. RESTful API to upload/delete apps

   We push new versions of our apps often. It would be helpful to have RESTful API so we could push new versions of apps and delete old versions.

   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…)
   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
   completed  ·  SimpleMDM responded

   http://simplemdm.com/docs/api

9. Enable location history

   The location tracking feature is great, but there needs to be a history feature so that administrators can see where the device has been in the past.

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

10. bulk push VPN account setting to a group device

    add the option for bulk push VPN account setting, such as i have 10 vpn service, and now i have add 10 times for each device. i want to push some VPN service to a group device only 1 time.

    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…)
    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
    completed  ·  SimpleMDM responded

    VPN accounts can now be assigned at the device group level. If the username and password field values are unique for each device, they can be left blank so that the user is prompted for the values. If you would like to add them as an administrator, custom attributes can be used to create username and password values on a per-device basis.

11. Allow remote blocking of specific apps for supervised devices

    As of iOS 9.3, the Apple Configurator 2 supports blocking individual apps by package name. It would be awesome if this would be possible from SimpleMDM.

    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
    completed  ·  SimpleMDM responded

    This feature is available today. Create an app restriction list under Settings > Config and then assign it to groups under the Restrictions tab of group details.

12. Multiple DEP

    Multiple DEP account / configurations.

    I have two classes of devices that we need to manage. One set is very locked down and supervised. The other we don't want to be supervised and just want some basic management. It's a bit painful right now to work around this and we'd love to be able to register sets of devices with different DEP accounts directly on Apple's site.

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

13. Include device vs. user profile and attribute support for custom configuration profiles in API

    Include the status of the "For macOS devices, deploy as a device profile instead of a user profile" and "Enable attribute support" checkboxes for custom configuration profiles in the API. The ability to check the current status (i.e., whether these are true or false), set/change them, and set them when uploading custom config profiles through the API would be useful.

    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 →
    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. Allow Download of Custom Profiles via API

    Allow Download of Custom Profiles via API

    • beneficial for scheduled tasks/audits
    • would complete the custom profile support via API (upload/download)
    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 →
    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 'SetRecoveryLock' and 'VerifyRecoveryLock' commands via Portal and API

    As well as show specific macOS information in the device info as its available, ie 'IsRecoveryLockEnabled'.

    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…)
    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
    completed  ·  SimpleMDM responded

    Find under Profiles > Recovery Lock Password

16. Display Architecture of App in Shared Catalog

    Many apps now offer separate Intel, Apple Silicon & Universal Binary builds. Knowing which version is available in the shared app catalog will be very useful during the architecture transition.

    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
    completed  ·  Anonymous responded

    Architecture for Shared Apps and custom apps that have architecture specified are now indicated within the admin interface with one of the following tags: Intel, Universal, or Apple Silicon.

17. Add Scripts and Script Jobs to API

    Feature Request: Add Scripts and Script Jobs to API

    Currently the "Scripts" and "Script Jobs" functionality is only supported when using the SimpleMDM web console via a browser.

    • Scripts: https://a.simplemdm.com/admin/scripts
    • Script Jobs: https://a.simplemdm.com/admin/script_jobs

    With the goal to support custom advanced automation for our machine provisioning processes and integration with other configuration management systems, we need the ability to:

    Requirements:

    • Create/Update (Upload) and Delete Scripts
      • Support multipart/form-data by default (similar to other SimpleMDM APIs)
    • List and Get Scripts, including:
      • Script ID
      • Script name
      • Full script contents
      • Created/Updated timestamps
    • Create Script Jobs
    • List Script Jobs
    • Get Job Status
    • Get Job Log / Results / Output

    Desirable bells & whistles premium options:

    • Query / Filter Script Jobs via Script Jobs List API. Available Filters might include:
      • Script Name
      • Script ID
      • Target ID(s) (Device ID(s), Device Group ID(s), Assignment Group ID(s))
      • Target Type(s) (Devices, Device Groups, Assignment Groups)
      • Created Timestamp
      • Updated/Modified Timestamp
      • Script Status (Pending, Completed, Failed)
    • Support Base64 encoding for Script Content when Creating/Updating scripts
    • API endpoint to get "raw" (application/octet-stream? Base64 encoded text/plain?) output of the script stdout/stderr Something like: GET https://a.simplemdm.com/api/v1/job/response/{job_id}
      • Currently the web console embeds the Script output as a JSON-escaped field in the "Metadata.job_response" field

    Why we need this functionality:

    We use SimpleMDM in addition to SaltProject for fleet management. Most of our fleet configuration is driven by Salt, however having the ability to use the native macOS MDM for management and automation will greatly benefit our ability to serve our users. The combination of Scripts (with Attribute Support!) and Jobs could be a game changer --if-- we could programatically interact with it. Some scenarios where this is valuable:

    • Initial Device Provisioning: When a new Device is enrolled in SimpleMDM, we want to take additional actions via the "device_enrolled" webhook event with a Script Job to do just-in-time provisioning.
    • Device Status Change Events: We already pull all SimpleMDM logs via API. We want to take advantage of

    Example scenarios:

    1. Upload A Bash Shell Script

    Request (POST)
    curl https://a.simplemdm.com/api/v1/scripts/ \
    -F "[email protected];filename=myscript.sh" \
    -F attributesupport=true \
    -u {APIKEY}:

    2.1. Execute myscript.sh against a single device

    Request (POST):
    curl https://a.simplemdm.com/api/v1/jobs/ \
    -d scriptname=myscript.sh \
    -d target={deviceid} \
    -d target_type=device

    Response:
    HTTP/1.1 200
    {
    "data": {
    "type": "job",
    "id": "abcde123456",
    "attributes": {
    "scriptname": "myscript.sh",
    "created": "2022-03-03T01:23:45Z",
    "createdby": "[email protected]",
    "target_type": "device",
    "target": "device-id-xxxx1234",
    "status": {
    "pending": 1,
    "completed": 0,
    "failed": 0
    },
    "devices": [
    {
    "id": "device-id-xxxx1234",
    "status": "pending"
    }
    ]
    }
    }
    }

    2.2. Execute myscript.sh against a device group

    Request (POST)
    curl https://a.simplemdm.com/api/v1/jobs/ \
    -d scriptname=myscript.sh \
    -d target={devicegroupid} \
    -d targettype=device_group

    1. Get Job Status:

    Request:
    curl https://a.simplemdm.com/api/v1/job/{JOB_ID} \
    -u {API_KEY}

    Response:
    HTTP/1.1 200
    {
    "data": {
    "type": "job",
    "id": "abcde123456",
    "attributes": {
    "scriptname": "myscript.sh",
    "created": "2022-03-03T01:23:45Z",
    "createdby": "[email protected]",
    "targettype": "device",
    "target": "device-id-xxxx1234",
    "status: {
    "pending": 0,
    "completed": 1,
    "failed": 0
    },
    "devices": [
    {
    "id": "device-id-xxxx1234",
    "status": "completed",
    "logid": "wxyz0987"
    }
    ]
    }
    }
    }

    1. Get Job Output

    Request:

    curl https://a.simplemdm.com/api/v1/job/log/{LOG_ID} \
    -u {API_KEY}

    Response:

    {
    "data": {
    "type": "log",
    "id": "ec481e3a74a44f588f95bab03f9b76e5",
    // ... standard job attributes?
    "metadata": {
    "name": "myscript.sh",
    "job_status": "0",
    "stdout": "<<Base64 Encoded stdout>>",
    "stderr": "<<Base64 Encoded stderr>>"
    }
    }
    }

    Feature Request: Add Scripts and Script Jobs to API

    Currently the "Scripts" and "Script Jobs" functionality is only supported when using the SimpleMDM web console via a browser.

    • Scripts: https://a.simplemdm.com/admin/scripts
    • Script Jobs: https://a.simplemdm.com/admin/script_jobs

    With the goal to support custom advanced automation for our machine provisioning processes and integration with other configuration management systems, we need the ability to:

    Requirements:

    • Create/Update (Upload) and Delete Scripts
      • Support multipart/form-data by default (similar to other SimpleMDM APIs)
    • List and Get Scripts, including:
      • Script ID
      • Script name
      • Full script contents
      • Created/Updated timestamps
    • Create Script Jobs
    • List Script Jobs
    • Get Job Status
    • Get Job Log /… 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
    completed  ·  Anonymous responded

    This has been implemented. Please see our documentation for more information:

    • Scripts API: https://simplemdm.com/docs/api/#scripts
    • Script Jobs API: https://simplemdm.com/docs/api/#script-jobs

    
    

    If there are additions/changes you would like to see, please submit a new suggestion. Also, thank you for the very detailed description!

18. Manage Non-Custom Profiles via API

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

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

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

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

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

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

    Say I create a FileVault profile in the web app and then want to assign the profile only to specific Macs using the API. There's not a specific group or device I want to manually assign. Instead I only want to assign to specific endpoints programmatically using a config management tool like Chef or Ansible. Since the profile is not "custom" I am unable… 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
    completed  ·  AdminEric McCann (Admin, SimpleMDM) responded

    This has been added! Documentation is available here: https://api.simplemdm.com/#profiles

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

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