Installation|
<< Click to Display Table of Contents >> Navigation: Technical Guide >
|
Introduction
This is a simplified presentation of ELM system requirements and should provide enough details for most ELM installations. Please check the web-based version of this document for recent updates and additional details:
https://firemtsoftware.com/support-resources/system-requirements/
Contents
*System Requirements
*Security
*Notes
*Database Design
*Elevated Privileges
*Restrictions on Evaluation Version
*Getting ELM Support
*Contact Us
System Requirements
ELM 8.0 Components
There is one product line in the ELM 8.0 family of solutions:
*ELM Enterprise Manager
All ELM Enterprise Manager 8.0 products include the following software components:
*ELM Server Centralized data collection, notification, and reporting.
*ELM Console UI for configuring, monitoring, and viewing of collected data.
*ELM Service Agent Collects and sends data to the ELM Server.
*ELM Toolkit Displays agent configuration; reads diagnostic data; generates test events; verifies checksums.
The ELM Enterprise Manager 8.0 product has the following additional software dependency unless a different database instance is specified in the installer:
*MS SQL Express Installed for new ELM Servers to provide SQL databases.
Minimum Hardware Requirements
Use the Windows operating system requirements as a benchmark for ELM Manager 8.0 minimum hardware requirements. Add to this:
*ELM Server 1 GB free disk
*Service Agent 50MB free disk
*Virtual Agent 20MB memory for each, on ELM Server computer
Note: These disk requirements do not include space for databases, collected .evt(x) files, or ELM Service Agent cache files.
Operating System
Any of the ELM Enterprise Manager 8.0 components can be installed on any of the operating systems below:
*Windows Server 2012 R2 or later
*Windows 10 or later
Database
The ELM Server requires two databases, primary and failover, and can authenticate using Windows Integrated (recommended) or SQL Authentication. The databases can be on the ELM Server or available via the local network, and can be a combination of any of the following:
*Microsoft SQL Server 2016 or later Enterprise, Standard, and Express
Required Software
A typical ELM installation includes one ELM Server, one or two ELM Consoles, and one ELM Agent for each monitored system. We recommend monitoring Windows systems with ELM Service Agents, and non-Windows systems with ELM IP Virtual Agents.
A common scenario is to install the ELM Server and ELM Console on a Windows Server in a datacenter or server room, and then use the ELM Console via remote desktop. A variation on this is to install the ELM Console on an administrator's workstation and connect it to the ELM Server in the datacenter. Whichever you prefer, computers hosting the ELM Server, ELM Agent, and/or the ELM Console should have the following:
*.NET Framework 4.6 Installed during setup
Service Agent - Service Agents run as a service on the monitored Windows computer and connect to the ELM Server when they need to transfer data. They can be installed by "pushing" them from the ELM Console, or by running the ELM setup package on the monitored computer. Some Monitor Items require the Remote Registry Service be started.
Virtual Agent and IP Virtual Agent - These two types of Agents run as part of the ELM Server service, so they have the same software requirements as the ELM Server. Allow 10MB of memory for every Virtual Agent. Virtual Agents require the Remote Registry Service be started on monitored systems.
Conditionally Required Software
The ELM Manager products have a wide variety of features and capabilities. Depending on your needs, certain software components are required for an ELM feature to function. Please see the TNT Software web site for more details:
https://firemtsoftware.com/support-resources/system-requirements/
Security
For proper functioning, the ELM installation requires solid name resolution and specific rights to gather data, notify administrators, and present results. Below are security requirements for different ELM components.
ELM Server - The ELM Server service account requires Administrative rights on the ELM Server and on all systems monitored by a Virtual Agent. Disabling User Account Control (UAC) is not required.
Service Agent - If a service account is used by a Service Agent, then it requires Administrative rights on the monitored system. Disabling User Account Control (UAC) is not required.
Notes
Miscellaneous notes for ELM components.
Service Agent - If NetBIOS over TCP is disabled, a Service Agent installed by the installation package can be registered to the ELM Server from the Agent by using the fully qualified domain name or the IP address of the ELM Server computer in the ELM Toolkit (Agent | Registration page).
Virtual Agent - Virtual Agents run in the ELM Server process and use RPC to gather data from Windows systems. They are not visible as separate processes.
IP Virtual Agent – An IP Virtual Agent can be assigned to any system or device on your network that has an IP address. IP Virtual Agents run in the ELM Server process, and do not appear as separate processes.
The ELM application performs administrative tasks, and therefore requires elevated privileges for all services. These are:
*ELM Enterprise Manager Server service or ELM Management Server
*ELM Service Agent
Most ELM UI components do not require elevated privileges. These are:
*ELM Toolkit
*ELM Management Console. The ELM Console does require read/write access to the installation directory, which on some systems does require elevated privileges.
Restrictions on Evaluation Version
The evaluation version is fully functional for a limited time in all aspects.