Create Agent Live Installer - Windows/Linux/macOS
This type of Agent deployment is useful when the remote and local deployment options do not work in your environment. In such cases, you can distribute the Agent Live Installer via email and let the user deploy it. You can also run the Agent Live Installer from removable media (a USB flash drive, for example).
|
Important • The client machine needs to have an internet connection to download the Agent installation package. • Make sure that the client machine has an internet connection and can connect to the ESET PROTECT Server. |
In the Quick Links section of the menu bar, click Other Deployment Options. In the Deploy Agent window, click Create installer button under Create Agent Live Installer. The Agent Live installers window will open.
Package creation
Deselect the check box Participate in product improvement program if you do not agree to send crash reports and telemetry data to ESET. If the check box is left selected, telemetry data and crash reports will be sent to ESET. Certificate - A Peer Certificate and ESET PROTECT Certification Authority is chosen automatically based on the available certificates. If you want to use a different certificate than the one automatically selected, click the ESET PROTECT Certificate description to select from a list of available certificates. If you want to use a Custom certificate, click the radio button and upload a .pfx certificate file. See Custom certificates with ESET PROTECT for further details. Enter a Certificate passphrase if needed. For example, if you have specified the passphrase during the installation of ESET PROTECT, or if you are using a custom certificate with a passphrase. Otherwise, leave the Certificate passphrase field blank.
Configuration - In this section, you can customize the following settings for the Agent Live installer package: 1.Optionally, you can change the Name and enter a Description for your package installer. 2.Click Select tags to assign tags. 3.Agent configuration (optional) - Use this option if you want to apply a configuration policy to the ESET Management Agent. Click Select and choose from the list of available policies. 4.Server hostname (optional) - Type the ESET PROTECT Server hostname or IP address. If necessary, you can specify the Port number (default is 2222). 5.Parent group (optional) - Select the Parent group where the computer will be placed after installation. You can select an existing static group or create a new static group to which the device will be assigned after the installer is deployed. 6.Select the check box Enable HTTP Proxy settings and specify the Proxy settings (Host, Port, Username and Password) to download the installer via Proxy and set ESET Management Agent connection to Proxy to enable communication forwarding between ESET Management Agent and ESET PROTECT Server. Read more about Proxy here.
Enable Use direct connection if HTTP proxy is not available if you want to allow this fallback option. 7.Click Finish to generate links for Windows, Linux and macOS Agent installer files.
8.Click Download under the installer file(s) that you want to download and save the zip file. Unzip the file on the client computer where you want to deploy ESET Management Agent and run PROTECTAgentInstaller.bat (Windows) or PROTECTAgentInstaller.sh script (Linux and macOS) to run the installer. For instructions on how to deploy the ESET Management Agent on a client using the Agent Live Installer, see our KB article.
|
Deployment from custom remote location
To deploy the Agent from a location other than the ESET repository, modify the install script to specify the new URL where the Agent package is located. You can also use the IP address of the new package. Find and modify following lines: Windows:
|
Deployment from local shared folder
To deploy the ESET Management Agent using Agent Live Installer from your local shared folder without the ESET Repository Download Server, follow these steps:
|
1.Edit the PROTECTAgentInstaller.bat file. 2.Copy the .msi agent installer to a local directory used by the PROTECTAgentInstaller.bat file by adding a command copy /y \\server\share\agent_x64.msi %installDirectory% before line set url=%installDirectory%\agent_x64.msi and a command copy /y \\server\share\agent_x86.msi %installDirectory% before line set url=%installDirectory%\agent_x86.msi and change lines set url=%installDirectory%\agent_x64.msi and set url=%installDirectory%\agent_x86.msi to point to the correct local download files. The original file looks like:
See the updated file below. Use your own URL (local shared folder), but do not change the %installDirectory%:
3.Replace the line: " echo.packageLocation = DownloadUsingHTTPProxy^("!url!", "!http_proxy_hostname!", "!http_proxy_port!", "!http_proxy_username!", "!http_proxy_password!"^) "
with: echo.packageLocation = "!url!"
4.Save the file. |
macOS:
1.Open the PROTECTAgentInstaller.sh script in a text editor. 2.Delete lines: 62-69 and 73-86.
3.Replace the lines highlighted below with the path to your local installer (Use your own local shared folder path): local_dmg= "/path_to_local_agent/agent_macos_x86_64.dmg"
4.Save the file. |
Linux:
1.Open the PROTECTAgentInstaller.sh script in a text editor. 2.Delete lines: 32 and 33:
3.Insert the following line with the paths to your local installer.
4.Replace lines 36 - 54 with the path to your local x86_64 installer. See the highlighted area in the image. Use your own URL (local shared folder), instead of the one shown below.
5.Delete lines 49 - 70.
6.Save the file. |
