Mac Client - Install / Uninstall

Prerequisites

Admin By Request for Mac 5.2 supports the following macOS versions:

  • macOS 14 (Sonoma)

  • macOS 15 (Sequoia)

  • macOS 26.2 (Tahoe)

Installation might work on macOS 11 (Big Sur) through 13 (Ventura), but product development and testing is no longer done on these versions and they are not officially supported.

IMPORTANT

Unless specifically prevented in portal settings, the installation process reverts the user performing the installation to a standard user. Therefore, if performing a manual installation on a standalone Mac, make sure you have an additional admin user configured before starting the install.

This is not an issue for Macs connected to a domain, where a domain admin account will always be available.

Your Tenant License

The installer file downloaded from the portal is unique to your tenant. Depending on the target operating system, it can be an executable file, a package or a script and it is signed with a license that applies only  to installers downloaded from the tenant in which you are currently logged-in. The same license file is applied to each of the operating system client installers: Windows, macOS, Linux and Server.

This is true for free plans as well as paid plans.

When installed on an endpoint, once the endpoint connects successfully, you will see in real time the status of the endpoint in your Inventory, which is also unique to your tenant. You will not see any endpoints installed with files downloaded from other tenants - this is simply not possible.

Admin By Request System Extension

Admin By Request for Mac 5.0 and higher includes an optional system extension to add additional functionality to the client – including intuitive installation of applications and additional admin entries for the auditlog.

To use this functionality, the system extension must be enabled and granted the correct permission.

If using other system extensions or real time scanning solutions like Microsoft Defender, CrowdStrike etc., please be aware that these can potentially conflict with each other. At the time of writing, all known conflicts with the Admin By Request client have been resolved.

Refer to Troubleshoot performance issues for Microsoft Defender for Endpoint on macOS for further details.

Full Disk Access (FDA)

Full Disk Access (FDA) must be enabled for both the adminbyrequest  application and the Admin By Request System Extension.

IMPORTANT

The order of installation tasks matters and it differs depending on manual installation of a single endpoint, or automated installation of multiple endpoints via an MDM such as Jamf or Intune.

On macOS 26.1 and 26.2, the privacy settings picker can fail to list binaries even when they are present. This behavior is fixed in macOS 26.3 and later.

If you are configuring Full Disk Access on macOS 26.1 or 26.2, use drag-and-drop of the required binary as a temporary workaround.

Installing Admin By Request

There are two procedures described - the first covering manual installation of one endpoint at a time and the second for the automated installation of multiple endpoints.

Single endpoint installation (manual)

This procedure describes how to manually install the Mac client on a single endpoint.

Multiple endpoint installation (automated via MDM)

This procedure describes how to install the Admin By Request Mac client on multiple endpoints using an MDM such as Jamf or Intune. The examples here use Jamf but the same Code Requirements can be used with any MDM.

We supply two configuration files to help with allowing the Admin By Request System Extension and enabling Full Disk Access for two apps. One is for Endpoint Privilege Management (EPM) and the other is for Secure Remote Access (SRA).

IMPORTANT

If you used the old config files (AdminByRequest - FDA PPPC_v2.mobileconfig and AdminByRequest - System Extension.mobileconfig), you must delete them before installing the EPM configuration provided here. Do not simply deploy over the top - delete the old files first, then deploy the new files.

This applies to the EPM config, which replaces both the old files. The SRA config is entirely new.

  • Admin By Request - EPM.mobileconfig

    Pre-approves Admin By Request background components and system extension, and grants the core permissions needed for Endpoint Privilege Management (including Full Disk Access).

  • Admin By Request SRA.mobileconfig

    Prepares Secure Remote Access permissions, including Screen Recording, Accessibility, and Automation permissions used during remote session handover.

Expand and copy these files, or you can download both in a zip file here.

If this is the first time using these configuration files, they must be deployed in your MDM scripts before installing Admin By Request.

The user experience on first-time use

Although much of the installation and deployment can be automated via your MDM, there are still several actions required by the user at the endpoint, depending on whether or not the device is enrolled in Secure Remote Access:

  1. From Admin By Request version 5.2, if the endpoint is enrolled in Secure Remote Access (portal setting Settings > Product Enrollment > SECURE REMOTE ACCESS - see Product Enrollment Example 2 for a scope example), an Accessibility Access prompt will appear:

    When this appears, click Open System Settings, go to Privacy & Security > Accessibility and enable Admin By Request SRA:

    This is a first-use, one-time-only prompt raised by the macOS operating system that allows Admin By Request SRA to run on the endpoint.

    NOTE

    • If installing Admin By Request via MDM and the endpoint is enrolled in Secure Remote Access at the time of installation, this prompt will not appear.

    • If the endpoint is not enrolled in Secure Remote Access, this prompt will not appear. However, if the endpoint is enrolled at some point in the future, the prompt will appear the first time a user logs in after enrollment.

  2. When the Screen Recording prompt appears, click Open System Settings:

    In Screen & System Audio Recording, enable Admin By Request:

That completes the requirements for enabling both the Endpoint Privilege Management and Secure Remote Access components of Admin By Request.

NOTE

Secure Remote Access (SRA) prompts on macOS are enrollment-driven. A Mac that is not enrolled in SRA behaves as EPM-only and does not show SRA-specific prompts.

For enrollment behavior details, see Product Enrollment.

Upgrading Admin By Request

You can manually upgrade any client immediately by simply installing the latest version, although upgrading endpoint client software occurs automatically 4 - 8 weeks after versions are released.

Deploying new releases

Admin By Request software updates are deployed using our Auto-Update process. However, when we release a new version we do not deploy it right away to all customers via auto-update. This is simply to mitigate any unforeseen issues.

Our rule-of-thumb for a new release is to activate auto-update within 4 - 8 weeks of release, but this is subject to change, depending on feedback and any potential issues that might arise.

Contact us if you wish to receive the latest version right now. You can also raise a support ticket requesting the latest update.

NOTE

If your Macs are not auto-updating to the latest version of Admin By Request, check the currently installed version on your endpoints. There was an auto-update issue with macOS version 3.2.1 - any Macs running that version of ABR will need to be manually updated.

The problem has been fixed in later versions of Admin By Request for Mac.

For more information

Refer to Synchronizing Clients with the Portal for a description of how endpoint clients communicate with the portal inventory.

Refer to Release Notes (macOS) for details on what is covered in each new release.

Uninstalling Admin By Request

IMPORTANT

If managing macOS endpoints using an MDM (e.g Intune, Jamf, Workspace ONE etc.), a post-uninstall script might be needed to revert at least one user account to admin permissions on each affected endpoint after completing the uninstall steps below.

This will be required only if all accounts have been downgraded to standard users. Check your Mac Settings in the portal (Lockdown > Admin Rights). If setting Revoke admin rights is On and there are no excluded accounts, then all accounts on each managed endpoint will have been downgraded.

Once Admin By Request is removed, the post-uninstall script needs to promote at least one account to admin permissions. Refer to (external) page Script to revoke or grant admin rights to standard users in macOS for an example.

The following procedures describe three ways to uninstall Admin By Request on a Mac:

These procedures are not sequential - pick one or a combination of all three, depending on your requirements.

User rights after installation

When a user logs on, the account is downgraded from Administrator to Standard User unless:

  • You have turned off Revoke Admins Rights in the portal settings (EPM > Settings > Mac Settings > Lockdown > ADMIN RIGHTS).

  • Also under Revoke Admins Rights, the user is in the list of Excluded accounts.

  • The computer is domain-joined and the user is a domain administrator.

Please refer to Supplementary Technical Information for more information.

Tamper Prevention

When a user initiates an administrator session, the user’s role is not actually changed from user to admin. The user is granted all administrator rights, except the right to add, modify or delete user accounts. Therefore, there is no case where the user can create a new account or change their own role and become a permanent administrator.

The user also cannot uninstall Admin By Request, as the only program, to keep the administrator session open forever. Furthermore, all settings, configuration and program files are monitored during administrator sessions. If the user tries to remove or change any of the Admin By Request files, these are restored straight away and the attempted activity is logged.

Mac Performance after Installation

When users are not using Admin By Request, it does not consume resources, except for a brief daily inventory and settings check.

Logging

Client activity and errors are logged in file /var/log/adminbyrequest.log.