Start a conversation

Installing GFI LanGuard Agent Manually via Command Prompt

Overview

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. 

This article provides information on how to install the LanGuard Agent manually and connect/register the deployed Agent with the LanGuard server.

Prerequisites

Target machine(s) should meet a minimum set of system requirements

 

Solution

In special cases or for the troubleshooting purposes it is possible to install the agent manually from the command line.

  1. 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. Open it and write down the server-specific Installation ID
    mceclip0.png

    You must deploy at least one agent from the LanGuard console before attempting a manual installation of an agent. This process populates the crmiini.xml file with the installation ID.

  2. 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.

  3. Copy the LanGuard12Agent.msi file to the target machine.

  4. From a Command Prompt on the target machine run the following command to install the agent manually:

    LanGuard12agent.msi /qn GFIINSTALLID="[Installation ID from Crmiini.xml]" /norestart /L*v %temp%\LANSS_v12_AgentKitLog.csv

    For example:

    LanGuard12agent.msi /qn GFIINSTALLID="1eabbf7e-c0de-45fa-92f8-bab3e29d2f1b" /norestart /L*v %temp%\LANSS_v12_AgentKitLog.csv
  5. Ensure 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.

  6. 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.

Any errors during the process will be logged to the %temp%\LANSS_v12_AgentKitLog.csv.

 

Testing

The installation results can be checked in the LANSS_v12_AgentKitLog.csv log. 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.

Choose files or drag and drop files
Was this article helpful?
Yes
No
  1. Priyanka Bhotika

  2. Posted
  3. Updated

Comments