# Installing and Uninstalling EUM Agent

## System Requirements

### On-premise Setup

| Number of RBM Monitors | OS | Processor | Memory | Hard Disk |
|---|---|---|---|---|
| 1 to 5 | Windows / Linux | 4 Core / 2.4 GHz and above | 8 GB RAM | 40 GB & above |
| 6 to 20 | Windows / Linux | 8 Core / 2.4 GHz and above | 16 GB RAM | 75 GB & above |

### Cloud VM Setup

| Number of RBM Monitors | Processor | Hard Disk | AWS recommended instance type | Azure recommended instance size |
|---|---|---|---|---|
| 1 to 5 | 4 Core / 2.4 GHz and above | 40 GB & above | **Type:** m-series xlarge (Eg: m5.xlarge)<br>**vCPU:** 4<br>**Memory:** 16 GB<br>**Processor:** 2.4 GHZ | **Size:** D-series D4 size (Eg: D4as_v3)<br>**vCPU:** 4<br>**Memory:** 16 GB<br>**Processor:** 2.4 GHZ |
| 6 to 20 | 8 Core / 2.4 GHz and above | 75 GB & above | **Type:** m-series 2xlarge (Eg: m5.2xlarge)<br>**vCPU:** 8<br>**Memory:** 32 GB<br>**Processor:** 2.4 GHZ | **Size:** D-series D8 size (Eg: D8as_v3)<br>**vCPU:** 8<br>**Memory:** 32 GB<br>**Processor:** 2.4 GHZ |

**Note:**

- We strongly recommend assigning a dedicated machine for the EUM Agent for production purposes.
- A maximum of 20 EUM Agents are allowed per Applications Manager instance.
- For configuring other EUM Monitors other than RBM monitors, the system configuration given for 1 to 5 RBM monitors will be sufficient.
- **For RBM Monitors:**
  - RBM monitor with Edge playback is supported only on the Windows EUM agent.
  - The recommendations are based on five steps per monitor. The configuration will vary depending on the load.
  - The performance of the monitor is influenced by the following factors:
    - The number of steps added in the monitor
    - The polling interval of the monitor
    - The time taken for the page to load
- **For ISP Latency Monitor**, EUM Agent must be started with elevated privileges (administrator or root user) to capture the traceroute data of the monitor.

## Installing EUM Agent

To start [end user monitoring](https://www.manageengine.com/products/applications_manager/end-user-monitoring.html) from multiple locations, you have to install the EUM agents in the respective locations. The agents can be installed in both Windows and Linux systems. Please note that the EUM agents will work only if the central Applications Manager server is running.

**Note:** Edge-based EUM Agents can be installed only on Windows Server with Microsoft Edge (versions 17 & above) Support.

### Windows

Follow the steps given below to install the EUM agent in Windows systems.

1. Download the [EUM Agent (.exe)](https://www.manageengine.com/products/applications_manager/eum-agent-download.html) file for Windows.
2. Execute the downloaded file. The installshield wizard will open up. Click **Next** to continue. Read the license agreement and click the **Yes** button.
3. Select the **language** in which you wish to install EUM Agent and click **Next**.
4. Specify the details of your Applications Manager installation such as host, port, and EUM API Key (which is available under *Settings → REST API → End User Monitoring*). Click **Next** to proceed.
5. Provide the location where the EUM agent should be installed in your machine. Click Browse to provide a different location of installation. Click **Next**.
6. Specify the name of the folder to be placed in Program Folder. The default is ManageEngine End User Monitoring Agent. Click **Next**.
7. If you want to install EUM as a service, select the "Install End User Monitoring Agent as Service" option and click **Next**. Please note that you need to have administrative privileges to install the EUM agent as a service.

   **Note:** [Click here](https://pitstop.manageengine.com/portal/en/kb/articles/how-to-change-service-user-account-for-eum-agent) to learn about the prerequisites to perform Chrome and Edge playback in an EUM Agent running in service mode.

8. The current settings will be displayed in the next screen. If you need to make any changes, click **Back**, or else click **Next** to continue with the installation. Once you click **Next**, the setup will start copying the jar files necessary for the EUM agent.
9. In the final step of the installation wizard, there are options available to *View the Read me file* and to *Launch the End User Monitoring Agent Now*. Select these options if required. Click **Finish** to complete the installation process.

### Linux

Follow the steps given below to install the EUM agent in Linux systems.

1. Download the [EUM Agent (.bin)](https://www.manageengine.com/products/applications_manager/eum-agent-download.html) file for Linux. Assign executable permission to the downloaded file using the command **_chmod a+x EUM_Agent_64bit.bin_**.
2. Execute the downloaded file. The Installation Wizard is displayed. Click **Next** to continue. Read the license agreement, accept the terms of the license agreement and click **Next**.
3. Select the **language** in which you wish to install EUM Agent and click **Next**.
4. Provide the **location** where the EUM agent should be installed in your machine. Click **Next**.
5. Current Settings will be displayed in the next screen. If you need to make changes, click **Previous**, else click **Install** to install the EUM Agent.
6. Specify the details of your Applications Manager installation such as host, port, and EUM API Key (which is available under *Settings → REST API → End User Monitoring*). Click **Next** to proceed.
7. Click **Finish** to complete the installation process.
8. Once installed, start the EUM agent by navigating to the **_&lt;EUM_Agent_Home&gt;_** directory and run **_sh StartServer.sh_**. For background execution, use **_sh StartServer.sh -d_** in the same directory.

**Note:**

- You can also install the EUM agent via **command line**. Just type in the following command in the command prompt: **_./EUM_Agent_64bit.bin -console_**. Execution of this command will take you through the installation process.
- Real Browser Monitor (RBM) via Firefox and Chrome browsers are supported in Linux.
- Users need Administrative privileges to install and run the agent in both the Windows and Linux OS.

### Limitations

- We recommend that you do not have more than one installation of the EUM agent in a machine as this causes malfunctioning in agent data collection in certain cases.
- Maximum allowed EUM Agents per Applications Manager instance is 20.

## Uninstalling EUM Agent

### In Windows

1. If the EUM agent is running, you should stop the agent before uninstalling it. You can stop the agent using any of these options:
   1. Use the *Start menu->All Programs->ManageEngine End User Monitoring Agent->Stop Server* option.
   2. From the command prompt, go to **_&lt;EUMAgent Home&gt;_** folder and execute the command **_StopServer.bat -force_**.
2. Use the *Start menu->All Programs->ManageEngine End User Monitoring Agent->Uninstall* option. The installshield wizard will be displayed. Follow the instructions shown on screen to uninstall the agent.
3. You can uninstall the agent using the **Control Panel → Add/Remove Programs** option as well.

### In Linux

1. From the command line, go to the *&lt;EUMAgent Home&gt;* directory and execute the below commands:

   **_sh StopServer.sh_**  
   **_sh StopServer.sh -force_**

2. Exit out of the command prompt and close all the files and folders opened in the *&lt;EUMAgent Home&gt;* directory.
3. Execute the command **_./Uninstall_** from the *&lt;EUMAgent&gt;/Uninstall* directory and follow the process. If there is no GUI or if you are uninstalling from a remote server, execute the command **_./Uninstall -console_** from the *&lt;EUMAgent&gt;/Uninstall* directory and follow the process.

## End User Monitoring Agent Settings

When you start the End User Monitoring agent, the EUM web client will be automatically launched. The web client can be accessed at the URL *http://localhost:9999* where *localhost* is the host system where the EUM agent is installed and *9999* is the port number where the EUM agent is running. [Refer here](https://pitstop.manageengine.com/portal/en/kb/articles/how-to-access-agent-settings-page#Accessing_EUM_Agent_Settings_page) for finding the EUM Agent port.

Upon accessing the EUM agent, you will be prompted with the EUM login page. Login using EUM API Key, which is available under **Settings → REST API → End User Monitoring**. To learn how to change Applications Manager hostname, port number and other proxy settings, [refer here](https://pitstop.manageengine.com/portal/en/kb/articles/faqs-related-eum#How_to_Change_Applications_Manager_hostname_and_port_in_EUM_Agent_for_login).

After successful login, you will be redirected to the **Agent Settings** page. Here you can modify the necessary EUM agent settings by clicking the **Edit** button and updating the settings. These changes will take effect only when you restart the agent.

### Server Settings

The Server settings specified here are used to establish a successful connection with the Applications Manager instance:

- **Server Host:** Hostname of your Applications Manager instance.
- **Server SSL Port:** Provide SSL port of your Applications Manager instance. The port configurations can be viewed in **AMServer.Properties** file located under *&lt;Applications Manager Home&gt;\conf\* directory.
- **EUM API Key:** API key for user authentication, which is available under **Settings → REST API → End User Monitoring**.
- **Polling Interval:** Polling Interval in minutes.
- **Allow multiple agents with the same host name:** This option should be enabled when a user’s network has multiple servers with the same hostname and the user needs to deploy an Agent on each one. Click [here](https://pitstop.manageengine.com/portal/kb/articles/allow-multiple-agents-with-same-hostname-a-setting-in-eumagent) to learn more.

**Note:** You have to restart the EUM agent for the any changes in Server settings to take effect.

### Proxy Settings

The Proxy settings specified here are used to establish a successful connection with the Applications Manager instance:

- **Auto-detect proxy settings for this network** - EUM Agent automatically detects the proxy settings to be used.
- **No proxy** - EUM Agent connects without a proxy.
- **Use system proxy settings** – EUM Agent uses the proxy settings defined in your system settings.
- **Automatic proxy configuration URL** – EUM agent uses the proxy settings defined in the PAC file.
- **Manual proxy configuration:**
- **Proxy Host & Proxy Port:** Enter the value of the proxy host & port on which the proxy connection will run.
- **Username & Password:** Enter the username & password for authorization.
- **No Proxy:** Give the domain names for which the manual proxy configurations should not be applied. The following rules are applicable:
  - Use semicolons (;) to separate entries.
  - The host may be any of the following types:
    - A complete host name (e.g. www.test.com)
    - A domain name. Domain names must begin with a dot (e.g. ".test.com")
    - An IP-address (e.g. "&lt;ip_address_1&gt;")
    - An IP-subnet, specified as an IP-address and a netmask separated by a "/" (e.g. "&lt;ip_address_1&gt;/255.255.255.192"). A 0 bit in the netmask means that bit won't be used in the comparison (i.e. the addresses are AND'ed with the netmask before comparison).

**Note:** You have to restart the EUM agent for the any changes in Proxy settings to take effect. If you have chosen any one of the following options: No proxy, Use system proxy settings or Automatic proxy configuration URL; the EUM agent will automatically detect proxy settings to be used while connecting to Applications Manager.

### WebDriver Settings

WebDriver specified here will be used to perform playback during each data collection.

- **Microsoft Edge WebDriver Path:** Complete filepath of the Microsoft Edge WebDriver downloaded and extracted on the server where this End User Monitoring Agent is installed. If the WebDriver is installed under *C:\Windows\SysWOW64\* then the provide the path as *C:\Windows\SysWOW64\msedgedriver.exe*.

  [Click here](https://pitstop.manageengine.com/portal/en/kb/articles/rbm-enabling-the-playback-using-microsoft-edge-browser) to find the steps to configure WebDriver for Microsoft Edge (versions 17 & above).

- **Google Chrome WebDriver Path:** Complete file path of the Google Chrome WebDriver downloaded and extracted on the server where this End User Monitoring Agent is installed.

  Sample driver path:

  **For Windows:** *C:\Windows\chromedriver.exe*

  **For Linux:** */home/test/chromedriver*

  [Click here](https://pitstop.manageengine.com/portal/en/kb/articles/rbm-enabling-the-playback-using-google-chrome-browser) to find the steps to configure WebDriver for Google Chrome (versions 65 & above).

**Note:**

- Playback using Microsoft Edge WebDriver is supported only in the End User Monitoring Agent installed on Windows Server with Microsoft Edge (versions 17 & above) Support.
- Playback using Google Chrome WebDriver is supported only in the End User Monitoring Agent installed on Server with Google Chrome (versions 65 & above) support.
- It is recommended to use the latest versions of Chrome and Edge browsers for playback.