Installation from a windows command line
Prerequisites
Ensure you have met the System Requirements needed to install the ESET Inspect Connector successfully.
To install ESET Inspect Connector for ESET Inspect Cloud, you need first deploy the ESET Management Agent and install ESET Endpoint Product. For the ESET Inspect Connector installation for ESET Inspect on-premises version, you need first deploy the ESET Management Agent and install ESET Endpoint Product.
Otherwise, the ESET Inspect Connector will display information that ESET Endpoint Product is required, and your installation will fail if they are not installed.
For the command line installation, follow these steps:
1.Download the installer file ei_connector_nt32_ENU.msi or ei_connector_nt64_ENU.msi, depending on the system.
2.Open the command line and navigate to the downloaded file.
3.You can use the example from below with altered attributes or run with specified in the table of attributes.
You may use several attributes with the installer using the silent mode during installation. The hostname is required:
Attribute |
Description |
Required |
Default value |
|---|---|---|---|
APPDIR |
Used to set directory under which application will be installed |
- |
C:\Program Files(x86)\ESET\ESET Inspect Connector\ for 32-bit OS and C:\Program Files\ESET\ESET Inspect Connector\ for 64-bit |
P_HOSTNAME |
Used to set host, on which ESET Inspect Server is installed |
yes |
"localhost" |
P_PORT |
Used to set the number of the port on which ESET Inspect Server is listening for data from ESET Inspect Connectors |
- |
8093 |
APPDATADIR |
The directory used to store logs and additional output files |
- |
"C:\ProgramData\ESET\Inspect Server\" |
P_PATH_TO_CERT_AUTH |
The absolute path to the Certificate Authority file on the target PC. Currently, URLs are not supported. Mounted remote drives like \\store03 should work. Multiple files can be separated by char ';' |
- |
- |
P_IS_SERVER_ASSISTED |
If you do not have the Certificate Authority present, set this parameter to 1 (P_IS_SERVER_ASSISTED=1) for server-assisted installation. If this parameter is used user does not need to use P_PATH_TO_CERT_AUTH |
- |
- |
P_INSTALL_CANARY_FILES |
If enabled, the installer will generate a canary file and place it in a hidden directory. Setting this value to "0" skips file generation. |
- |
1 |
|
msiexec /i ei_connector_nt32_ENU.msi P_HOSTNAME="192.168.5.21" P_PORT="8093" P_PATH_TO_CERT_AUTH="C:\repo\Component\Products\Inspect Server\Src\test\http_server\certs\ca_store\ca.cert.der" |
|
You need to activate ESET Inspect Connector with an "ESET Inspect" license. To do this, contact your ESET PROTECT Administrator or create a Product Activation task. |
Assign policy
It is necessary to create a Policy to make ESET Inspect Connector communicate with ESET Inspect Server (this is not necessary for ESET Inspect Cloud):
1.In the Settings window, select the product "ESET Inspect Connector"
2.Fill in the Server Address with the ESET Inspect Server IP address.
3.Edit the Certificate Authority by clicking Edit > Add > Open Certificate Authority. Chose the certificate that was used during ESET Inspect Server installation. Click Save.
4.Click Continue.
5.Select the Assign button and select the computer/computers you want the policy to be applied on in the Assign window. Click Finish.
|
The ESET Inspect Connector will be visible in ESET Inspect Web Console immediately after activation and correct policy setting. In a few minutes, you should be able to view the first events sent by connectors. ESET Inspect Connector is writing error logs into the folder: •Windows C:\ProgramData\ESET\Inspect Connector\logs •macOS /Library/Application Support/ESET/eset_eia/logs •Linux /var/log/eset/eei/ If you experience any other issues, follow the instructions on gathering debug data as detailed in Troubleshooting the installation topic. |
