--- title: Installation slug: kronpam-agent-reference-guide-3-7-0/installation description: Learn how to install a Windows agent on Windows Server 2016, 2019, 2022, Windows 10, or Windows 11 with this step-by-step guide. Get the setup file from the Windows agent management, ensure .NET Framework 4.7.2 is installed, and follow the necessary steps docTags: createdAt: 2023-06-19T07:44:07.000Z --- , install Windows Agent (supporting Windows Server 2016, 2019, 2022, Windows 10 and 11), you need to have an installation package. Also, on endpoint **.Net framework 4.7.2** should be installed if it does not exist. To get the setup file: :::hint{type="info"} Installation should be done with a user who has local admin rights. ::: :::hint{type="info"} Kron PAM’s kernel driver is not implemented for ARM architecture. So you should not install the agents to ARM architecture is ::: :::hint{type="info"} When the installation is successful, the agent is going to take over credential provider functionality from Windows OS. And other log in options will be disabled. So agent will be the only credential provider for Windows login operations. Loca Accounts are not going to be asked to PAM and their authentication will be done by Windows via agent. AD accounts will be asked to Domain via agent. ::: - Navigate to Windows Agent Management and click the **Add** button. ![](https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/0qMybE-QJfzaLooQTp6ez_image.png "Agent Dashboard") - Click Agent Installation. ::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/KTGH9jZwaO0IYtCIjSgHV_image.png" size="66" width="677" height="242" position="center" caption="Add button details of Agent Dashboard" showCaption="true"} - Download the PS1 file by clicking **here**. An example of the PS1 file is provided below. Copy this file to the endpoint where you want to install the agent. Ensure that port 443 is open between the endpoint and Kron PAM servers. When you execute the PS1 file on the endpoint, it will download the agent, allowing you to proceed with the installation. The PS1 script must be run as an administrator. If script execution is disabled on the system, enable it using the following command: `Set-ExecutionPolicy -ExecutionPolicy Unrestricted` :::hint{type="info"} add-type @" using System.Net; using System.Security.Cryptography.X509Certificates; public class TrustAllCertsPolicy : ICertificatePolicy \{ public bool CheckValidationResult( ServicePoint srvPoint, X509Certificate certificate, WebRequest request, int certificateProblem) \{ return true; } } "@ $AllProtocols = \[System.Net.SecurityProtocolType]'Ssl3,Tls,Tls11,Tls12' \[System.Net.ServicePointManager]\::SecurityProtocol = $AllProtocols \[System.Net.ServicePointManager]\::CertificatePolicy = New-Object TrustAllCertsPolicy Set-Location -Path C:\\ Invoke-WebRequest -Uri "https\://10.20.42.12:443/repo/windows-agent/win\_agent.exe" -OutFile "win\_agent.exe" ::: ::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/EMRVoEBVbWanmSSaKe-hy_image.png" size="64" width="532" height="414" position="center" caption="Creating Registration Token" showCaption="true"} - If a non-expired token is already on the screen, you will see it on the download page. But if you need a new token, you can return to the first screen to reproduce one. Then, go to the next page to download the batch file again with a new token. ::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/QI3uKDAtOy5iuzMaJuPIN_image.png" size="64" width="533" height="497" position="center" showCaption="false"} The agent is installed when you place the ps1 file on the endpoint and run it as a local admin. - Start the installation package and click** License Agreement.** ::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/3vIHrefv3A2xhYslPsz1-_image.png" size="54" width="480" height="300" position="center" caption="Agreement of Agent installation" showCaption="true"} - Click **Next.** ::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/QefmLlxQ2YBT9sucnPMV2_image.png" size="54" width="388" height="300" position="center" caption="Agent installation" showCaption="true"} - Enter the necessary information. Then click** Install.** 1. The registering endpoint is the Kron PAM Server 2. The initial token is a registration token. 3. Super Local Admin is a local admin account for all the endpoints. This account can perform any process on the server. An agent cannot block this account's actions on the endpoint, but every action of this account will be logged. ::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/nN_AW__BZkQPElKutMVdb_image.png" size="64" width="391" height="300" position="center" caption="Agent installation" showCaption="true"} - Installation is successful. ::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/cJkT7ORs6WmcGL_tqdZxZ_image.png" size="58" width="563" height="319" position="center" caption="Compilation of Agent installation" showCaption="true"} :::hint{type="info"} \* During installation, the agent sends the server's IP address, hostname, and OS version to Kron PAM. If the server's IP address changes at any point, the agent updates Kron PAM with the new information. From then on, the updated IP is used throughout Kron PAM, replacing the old one. \* If an agent remains offline beyond a specified time, it is automatically removed from the Agent Dashboard, along with any associated agent-specific rules. The device will then be moved to the "Unassigned Device" group in the device tree without affecting any Kron PAM-related rules. This is a configurable option set in the system configuration manager, using the parameter below (measured in days): win.agent.remove.after.expire.time = 60 \* To install the agent silently on CMD please use the below command line syntax "agent.exe" INITIAL\_TOKEN= "cb6b6d7f-bebb-4463-8a6e-ca58cb168120" REGISTER\_ENDPOINT="https\://10.20.42.12/" ::: Sometimes System administrators need a powerful user who can do anything. In these cases, you need to define the parameter below in the system configuration management page. When a user is defined with the below parameter those users can do anything, and they are not being policed just they are logged. This is called **All Run Right.** :::hint{type="info"} win.agent.all.run.right = Administrator, PamAdmin, SystemAdmin :::