Submit a ticketCall us

AnnouncementsWeb Help Desk Integrations eCourse

Looking to reduce response times? Sign up for our eCourse to learn how integrating Web Help Desk with Dameware Remote Support, Network Configuration Manager, Network Performance Monitor, and Server & Application Monitor can improve communication efficiencies.

Register here.

Home > Success Center > Log & Event Manager (LEM) > Using Multiple LEM Appliances on a Single Console

Using Multiple LEM Appliances on a Single Console

Table of contents

Adding a LEM appliance to an existing one that will collect logs for different duties and be able to browse through OPS Center and Monitor to view all events from one web interface is possible.

Add more managers from Manage > Appliance.

Users can access and manage all LEM features from a single console. The primary appliance is where the web application is loaded and where the other appliances are connected to.

  • Data in OPS Center and Monitor will show from all appliances.
  • Searches in nDepth will search across all appliances.
  • Build functions will manage an individual appliance only.
  • Manage functions will manage an individual appliance only.


  • Known issues

There could be more issues when using the multiple appliance functionality of LEM as this is not a common configuration and has not been tested extensively. For example, issues with running nDepth searches across appliances may come up. More known issues may be viewed from Release notes.

  • Versions

You need to be running the same versions of LEM across all your appliances.

  • Scale

The real-time view of the primary console does not scale ultimately. This means that your real-time views are unable to keep up with the aggressive number of events that you would if you had several LEM appliance hook ups.

  • Data

Data is encrypted as it is with a single console so long as HTTPS is used. It is the exact connection, you just have one primary appliance where the application is downloaded from.

  • Networking

A primary console uses the same ports and the same bandwidth as a single console. The receiving side has to multiply that by the number of appliances they are connecting to.


Each virtual appliance has to have a license for the number of nodes it will be managing.  All in all, you are licensing the number of nodes. If you deploy multiple appliances, each individual has to have a license.

Last modified