Windows Client - Install / Uninstall

Prerequisites

Admin By Request supports all current Windows versions, including:

  • Windows 11

  • Windows 10

  • Windows Server (with Desktop Experience only)

If installing individually on client endpoints, you will need administrator privileges on every workstation that executes the installation client.

If installing via Intune, you need to be able to create Intune packages.

You'll also need valid credentials to access your Admin By Request online portal at Admin By Request Portal.

There are additional prerequisites when working with Admin By Request for Windows 8.4 and Secure Remote Access - refer to Unattended Access Prerequisites and Remote Support Prerequisites for more information.

Support for Windows 7 computers

Admin By Request version 7.4 is the last version to officially  support Windows 7 (Pro and Enterprise only). If you need to use this version, login to the portal and visit our Download Archive.

While newer versions of Admin By Request should still function on the Windows 7 operating system, they are not tested for compatibility, so we cannot guarantee stability.

If you experience issues with Admin By Request on Windows 7, we would likely still perform basic troubleshooting, but may be unable to resolve problems specific to the operating system.

See also the Windows FAQ.

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 other endpoints installed with files downloaded from other tenants - this is simply not possible.

Installing Admin By Request

There are three installation methods covered here:

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

Upgrading Admin By Request

As the installer is a standard MSI file, upgrading is automatically detected.

If you deploy a newer version of the Admin By Request Windows client, msiexec.exe will automatically perform an uninstall of the old version and an install of the new version.

Deploying new releases

Admin By Request software updates are deployed by 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 issues that arise after beta testing.

Our rule-of-thumb is to activate auto-update of new releases 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.

Refer to the Download Archive for previous versions of Admin By Request.

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 (Windows) for details on what is covered in each new release.

Uninstalling Admin By Request

There are several uninstallation methods described in this section, for both single endpoints (i.e. attended, one at a time) and multiple endpoints (unattended, scripted ).

NOTE:

These methods are not sequential - pick one or more, depending on requirements.

Single endpoint uninstall
Multiple endpoints uninstall

Any one of the following commands when used in a script might work more reliably than the others, depending on device management software, endpoint configuration and other installed applications. Generally, the third method (using PowerShell) is the most reliable and should work if the others do not.

NOTE:

Code lines in the following procedures might wrap, especially if viewing in PDF format.

When copying, make sure there are no line breaks and replace place holders such as \\REMOTECOMPUTERNAME and \\path\to\ABR\MSI with the correct information for your environment.

User rights after installation

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

  • You have turned off Revoke Admins Rights in the portal settings (EPM > Settings > Windows 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.

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.

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.