2/16/2024 0 Comments Languard network scanner download![]() The targets can be defined via their Computer name (shown below), Domain name or Organization Unit:įigure 3. Since we’ve selected Custom, we need to click on Add new rule to add our targets. Defining Target rules for GFI LanGuard Agent deployment Next, you can choose between Local domain or Custom to define your target(s):įigure 2. Select Agents Management and the Deploy Agents Let’s see how we can install the GFI LanGuard Agent from the server’s console.įirst open GFI LanGuard and select Agents Management from the Configuration tab:įigure 1. GFI LanGuard Agents communicate with the GFI LanGuard server using TCP port 1070, however this can be configured. During the time of scanning, once a day for a few minutes, the scan process is kept at a low priority to ensure that it does not interfere or impact the host’s performance. Those concerned about system resources will be pleased to know that the GFI LanGuard Agent does not consume any CPU cycles or resources while idle. Once installed, the GFI LanGuard Agents can then be configured via LanGuard’s main server console, giving the administrator full control as to when the Agents will scan the host they are installed on, and communicate their status to the GFI LanGuard server. GFI LanGuard Agents are designed to be deployed on local (network) or remote servers and workstations. If you register the new agent with the LanGuard server its status can be verified in the Dashboard > Overview by clicking on the client machine in the Computer Tree and looking at the Agent Status window. The installation results can be checked in the LANSS_v12_AgentKitLog.csv log. In order for the GFI LanGuard server to be aware of the new agent and register this deployment, now the agent installation needs to be manually triggered from the LanGuard server console.Īny errors during the process will be logged to the %temp%\LANSS_v12_AgentKitLog.csv. ![]() Locate the LanGuard12Agent.msi in the Agent subfolder of the LanGuard server main installation folder, by default C:\Program Files (x86)\GFI\LanGuard 12\Agent.Ĭopy the LanGuard12Agent.msi file to the target machine.įrom a Command Prompt on the target machine run the following command to install the agent manually: LanGuard12agent.msi /qn GFIINSTALLID= /norestart /L*v %temp%\LANSS_v12_AgentKitLog.csvįor example: LanGuard12agent.msi /qn GFIINSTALLID= 1eabbf7e-c0de-45fa-92f8-bab3e29d2f1b /norestart /L*v %temp%\LANSS_v12_AgentKitLog.csvĮnsure the success of the LanGuard operations on the client machine by configuring the required environmental settings and verifying the required network connectivity and security permissions. This process populates the crmiini.xml file with the installation ID. You must deploy at least one agent from the LanGuard console before attempting a manual installation of an agent. Open it and write down the server-specific Installation ID : Locate the crmiini.xml file In the GFI LanGuard server Search Engine installation directory, by default C:\Program Files (x86)\GFI\Languard 12 Agent\crmiini.xml. In special cases or for the troubleshooting purposes it is possible to install the agent manually from the command line. ![]() Target machine(s) should meet a minimum set of system requirements. This article provides information on how to install the LanGuard Agent manually and connect/register the deployed Agent with the LanGuard server. You would like to use your existing automation processes to install the LanGuard agent to the client machines or are troubleshooting the agent failing deployment, or have another special case requiring the agent installation via command prompt outside of LanGuard workflow.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |