System Requirements

Windows 7 Enterprise / Ultimate
Windows Server 2008 Standard / Enterprise
Windows Vista Business / Enterprise / Ultimate
Windows Server 2003 Standard / Enterprise
Windows XP Professional

Note: Windows 2000 is supported for agent installs only.
          We do not test on Microsoft Windows Small Business Server edition therefore it is not supported.

All ELM Enterprise Manager 6.5 products include the following software components:

• ELM Server - Centralized data collection, notification, and reporting.
• ELM Web Viewer - Web console with basic functions installed on the ELM Server.
• ELM Console - Main UI for configuring ELM and viewing collected data.
• ELM Advisor - Desktop Notification that runs in Windows Notification area.
• ELM Service Agent - Collects and sends data to the ELM Server.

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.

ELM Server and ELM Console - 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 and/or the ELM Console should have the following:

• Microsoft cabinet.dll v5.0.2195.7000 or later
• MSXML 3.0 SP5 on Windows XP SP2, else KB284151
• .NET Framework 2.0
• Internet Explorer 6.0 or later
• MMC 3.0 or later
• Microsoft Visual C++ 2008 Redistributable Package (x86)

ELM Web Viewer - The ELM Server computer can host an optional ELM web site that's accessible by any browser that supports Java Script and active server pages. This optional feature requires Internet Information Server (IIS) and ASP.NET 2.0 on the ELM Server computer.

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. If an ELM Service Agent is installed using setup, the monitored computer will need the Microsoft cabinet.dll v5.0.2195.7000 or later. 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 Enterprise Manager licenses 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 Supplemental Downloads web page for more details.

http://www.tntsoftware.com/elmsupport/supplementaldownloads.aspx

A database is required for ELM Server installation. It can be on the ELM Server or available via the local network. Refer to the Readme file for detailed information.

Microsoft SQL Server 2008 (or newer)
Microsoft SQL Server 2008 (or newer) Express Edition

Dual Core CPU
2.0GB memory
300MB free disk space (does not include space consumed by SQL Server database files)

ELM Server: 100MB free disk
Service Agent: 50MB free disk
Virtual Agent: 10MB memory for each, on ELM Server Computer

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.

ELM Console and ELM Advisor - During install, the Authenticated Users group will be given DCOM Allow Access permissions in My Computer on the computer running the ELM Console. COM+ server applications will also be created under the DCOM Config branch of Component Services.

Service Agent - If a service account is used by a Service Agent, then it requires Administrative rights on the monitored system.

ELM Web Viewer - Although the Web Viewer is primarily a read-only tool, be aware that users with sufficient permissions can enable or disable ELM objects (such as Agents or Monitor Items), and can delete data from the ELM database. Any security configuration changes made via the ELM Console are also respected by the ELM Web Viewer.

ELM Server - ELM Server 6.5 will recognize the /3GB switch if used with a Windows 32-bit operating system.

ELM Console & ELM Advisor - The ELM Console and ELM Advisor can both be installed during setup. There is now a separate component selection required during setup to install the ELM Advisor.

Service Agent - If NetBIOS over TCP is disabled, a Service Agent installed by the .msi package can be registered to the ELM Server from the Agent by using the fully-qualified domain name or the TCP/IP address of the ELM Server computer in the Agent Register Server Wizard.

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.

Windows 64-bit
ELM 6.5 has been tested on the 64-bit editions of Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, and is supported.

The Auto-add Agents feature is also disabled. In a licensed installation of ELM, devices can send Syslog messages or SNMP traps to the ELM Server computer, and ELM will automatically create an IP Virtual Agent for the device if no Agent is already present. This feature is disabled in evaluation mode; in order for ELM to receive Syslog or SNMP traffic, you must manually create an Agent for each source of traffic.