Submit a ticketCall us

Training Class Getting Started with SolarWinds Backup - February 28

This course offers customers an introduction to SolarWinds Backup, focusing on configuring the backup technology, taking backups, data restoration and data security. It is a great primer and will get you up to speed quickly on SolarWinds Backup.
Register for class.

Home > Success Center > Log & Event Manager (LEM) > Set up Officescan syslog messages with LEM

Set up Officescan syslog messages with LEM

Table of contents
Created by Ezgi Muderrisoglu, last modified by Tim Rush on Oct 21, 2017

Views: 1,380 Votes: 0 Revisions: 5


This article provides information on how to set up Officescan application sending syslog to LEM.


  • all LEM versions
  • Officescan version 11


Note:The TrendMicro Officescan connector is available under the agent, but under the 'manager' connectors.
Open LEM console > Manage > Nodes > click on the Gear icon of the machine agent where it installed, and then click Connectors.


A. Confirm the syslog sending:

  1. Confirm that the Officescan is configured correctly to send log data to Windows Application log by opening this log from within Windows Event Viewer. If Trend events do not appear in the Windows log,  LEM connectors cannot get them.

B. Confirm the integration of the Windows server and LEM:

  1. Install LEM agent on the Windows server that is hosting the Trend Micro anti-virus. Be sure to install the agent with runas-admin for the install, which give the agent permission to send events to LEM..
  2. Once the Windows server is added/integrated with LEM, the server name should appear on the list of Nodes on your LEM console. 

C. Set up the Connector:

  1. Select the node with this server name. 
  2. Click on the gear icon.
  3. Click on connectors.
  4. For this node, the Officescan connector appears on the list.
  5. Once you have located the Officescan connector, configure the details accordingly with the same location where the syslogs are being sent to (will will be the Application log).



Last modified