Deploying a Windows Logon Agent

The Passly Windows logon Agent offers companies the ability to add strong multi-factor authentication to Microsoft’s Windows client and server operating systems. It provides a simple and consistent logon experience no matter if they logon at the local desktop or through a terminal session. And it offers identity assurance by requiring users to provide their Passly 2FA Passcode during the logon process.

Note: This agent is installed on a per machine basis. 

Note: This agent requires that the Passly username and the Windows username must be matching.

Supported Operating Systems

  • Windows 8
  • Windows 8.1
  • Windows 10
  • Server 2012
  • Server 2012r2
  • Server 2016

Note: This agent does not support x86 versions of Windows. 


To configure a Windows Logon agent please follow these steps

First create a Policy for this agent.

  1. Log into your tenant https://(your company).my.Passly.com
  2. Select Policy Manager.
  3. Select the Add icon (small green + sign in the bottom right corner). 
  4. Name the Policy
    Example: Windows Logon Agent.
    Set your Policy Elements & Actions.
    Note: This policy must not allow for simple passwords. Require 2FA must be used.
    mceclip0.png
  5. When you have your policy completed select Save changes.
    policy2.PNG

 

 

  1. Select Auth Manager.
  2. Select the Add icon (small green + sign in the bottom right corner). 
  3. Select Windows Logon.
    1.PNG
  4. Configure the agent.
    Select Agent is enabled.
    Select the policy you created in Step 4.
  5. Select Windows Logon Configuration.
    mceclip0.png
    Note: 'Enforce 2FA on RDP Only' is not supported on versions of Windows earlier than Windows 8 and Windows Server 2012.
    Note: It is recommend that you set an Override Password for all installs.
    Note: You will need to manually create the Passly Override Group in Active Directory (Windows security group for stand alone machines).
    Note: Enabling "Allow Offline Access" will allow the admit to setup the ability for the user to login with no internet connection. This setting must be enabled, as well the user needs to login once before the machine is taken offline. The maximum number of days is an arbitrary decision made by the admin deploying the agent.
    mceclip1.png
  6.  
  7. Select Add Agent.
    3.PNG
  8. Select the Agent from the agent list in Auth Manager.
  9. Select Download Installer.
    4.PNG
  10. Copy the installer AAWinLogonCP.msi file to the target x64 Windows Server/Desktop/Workstation.
    Note: The installer must be on the local machine and not run from a shared drive like Lancache.
  11. Run the MSI AAWinLogonCP.msi
    Note: If installing on a DC or where there might be excessive UAC style controls enabled you can run the MSI from an elevated command.
  12. Select Run if prompted.
    5.PNG
  13. Select Next.
    6.PNG
  14. Accept the Terms of Use. Select Next.
    7.PNG

  15. Logon Agent configuration. Set the following.
    Home Realm: (This your tenant (your company).my.Passly.com)
    Note: If you are installing a Sub-Organisation's agent you will need to use the sub-Org URL,
    For example my tenant is kaseya.my.passly.com and client org is acme. I use acme-kaseya.passly.com for my Acme agent Home Realm. 
    ID: (This will be provided on the agent information screen where you downloaded the agent).
    Key: (This will be provided on the agent information screen where you downloaded the agent).

    8.PNG
  16. Select Next.
  17. Select Install.
    9.PNG
  18. Select Finish.
    10.PNG

 

Test the agent

  1. Lock the desktop. Enter the user's Windows Password.
  2. You should receive a Push notification automatically.
    Note: PUSH is only possible if the machine has an active internet connection. 
    Note: If the PUSH fails you will receive an 2FA prompt for the passcode. Open the Authenticator app. Tap your username. This will provide you with your one time password.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Contact us