Installation of the login agent on Windows (GINA), macOS, or Linux

Supported platforms

For users to protect their machines with MFA and reset passwords from their Windows, macOS, or Linux login screens, admins have to deploy the login agent on the users’ machines.

Windows Servers	Windows Clients	macOS Clients	Linux Clients
Windows Server 2022	Windows 11	macOS 14 Sonoma	Ubuntu-16.x-20.04.4
Windows Server 2019	Windows 10	macOS 13 Ventura	Fedora - 27.x-31.x
Windows Server 2016	Windows 8.1	macOS 12 Monterey	CentOS - 7.X
Windows Server 2012 R2	Windows 8	macOS 11 Big Sur
Windows Server 2012	Windows 7	macOS 10.13 High Sierra
Windows Server 2008 R2	Windows Vista	macOS 10.12 Sierra
Windows Server 2008		OS X 10.11 El Capitan
		OS X 10.10 Yosemite

Note:

HTTPS needs to be enabled in the Access URL to install the Login Agent on remote machines. Learn how to enable HTTPS in ADSelfService Plus.

While the ADSelfService Plus login agent has been officially tested to be compliant with the three Linux distributions mentioned, it may support other Linux distributions as well. Please contact the support team (support@adselfserviceplus.com) to check if the Linux distribution used in your organization is supported.

Please treat the Installation Key like a password. It is sensitive information and must not be shared. Please regenerate a new Installation Key using the link in the product GUI if the current Installation Key is compromised.
If a new Installation Key is regenerated, copy the command with the new Installation Key from the product admin portal and update the Installation Command field with the new command for all new installations done via GPO, SCCM, Endpoint Central or other third-party installation applications.
The generation of a new Installation Key will not affect the existing installations of the Login Agent on installed machines.

Before you begin:

The ADSelfService Plus SSL certificate should be trusted in the Keychain Access app on macOS. This is mandatory for machines running macOS 13 (Ventura) and above.

To do this:

Open the Keychain Access app on a Mac that's running macOS 13 (Ventura) or later.
Download and include ADSelfService Plus' CA certificate under the Certificates tab.
Expand the trust section of the certificate and mark When using the certificate to Always Trust.

Different methods to deploy the Login Agent:

The login agent can be deployed on users' machines in one of the following ways:

A. From the ADSelfService Plus admin console

The ADSelfService Plus admin portal is a simple and effective way to install the login agent on Windows, macOS and Linux machines.

Installation Steps:

In the ADSelfService Plus web portal, go to Configuration > Administrative Tools > GINA/Mac/Linux (Ctrl+Alt+Del) > GINA/Mac/Linux installation.

Click New Installation.
Select a domain and then the computers on which you want to install the login agent.
Click Install.

Note: ADSelfService Plus now supports three different methods of Windows login agent installation to enhance the success rate. The three methods are:

Remcom.
PAExec.
WMI.

When Remcom fails, PAExec is tried, and if that fails, WMI is implemented.

Click here for detailed information on installing and customizing the Login Agent through the ADSelfService Plus Admin Portal.

B. Manual installation

1. Using the Installation Wizard

Clicking on Manual Installation Steps (GINA/MAC/Linux) opens up the Manual Installation Steps pop-up.

Manual installation

2. Using the Command Line Interface (CLI)

a. Windows Login Agent CLI installation

When the login agent is installed manually using the MSI package on computers running Windows Vista and later operating systems with User Account Control (UAC) enabled, it may not function properly. In such cases, you can install the login agent manually through the Command Prompt, as shown here.

b. Mac Login Agent CLI installation

Use the command under Mac Login Agent CLI installation View Parameters when you are silently installing the Login Agent via the terminal or via any 3rd party endpoint management tools like Endpoint Central.
Ensure that the installer file and the script file (both of which can be found in the product <Installation_Directory>/bin folder) are copied to the respective folder before executing the CLI command.
Script file: installLinuxAgent.sh
Installer file:
32-bit machines: ADSSPLinuxClient.tar.gz
64-bit machines: ADSSPLinuxClient64.tar.gz

C. Via GPO

Follow the steps in this Login Agent installation guide to install the GINA Login Agent on Windows machines, using GPO.

D. Via SCCM

Follow the steps in this Login Agent installation guide to install the GINA Login Agent using SCCM.

E. Via Endpoint Central

Follow the steps in this Login Agent installation guide to install the Login Agent using Endpoint Central.

Note: The installation of the login agent via GPO and SCCM deployment methods is only applicable for Windows client software.

Related Products

Help Document