SIEM, Log Management, Security, Compliance, Server Monitoring and Uptime Monitoring Software

Agent-Based Event Log Management with Corner Bowl Server Manager

May 21st, 2022

In this article I am going to show you how use Corner Bowl Server Manager's Agent to:

  • Consolidate Event Log Entries to a Log Database.
  • Backup Event Log Files to a remote location.

Table of Contents

How to Configure our Agent-Based Event Log Management Templates

Our Event Log Consolidation (Application, Security, System) (Agent) Template requests Event Log Entries then saves them to the Log Database used by Reports such as Success and Failed Logons.

Event Log Consolidation Template Properties View
Event Log Consolidation Template Properties View

Our Event Log File Backup (Agent) Template requests Event Logs are backed up then uploaded to the Management Server for remote storage. Backed up Event Log Files are compressed then optionally encrypted using FIPS compliant AES.

Event Log File Backup Template Properties View
Event Log File Backup Template Properties View

Both of these templates are flagged within their corresponding properties views as Agent-Based Templates. For detailed information on each template, see the in-application help file.

To configure a template as an Agent-Based Template

  • From the Explorer View, right click on a supported template type then click Template Properties. The Template Properties View displays.
  • From the Template Properties View, select the Agent Template Tab
  • Use the Enabled check box to flag the template as an Agent-Based Template.
  • Use the Trigger check box to trigger actions when assigned hosts do not connect within the configured time span.
  • Use the On Host Not Connecting drop-down to assign the actions to fire when assigned hosts do not connect within the configured time span.
Agent-Based-Template-Properties Tab
Agent-Based-Template-Properties Tab

How to Install the Agent on Windows Servers

Next, we need to install the agent on each target host. If the service is running with Domain Administrator credentials and both WMI and Windows Shares technologies are available, the installation is automatic, otherwise you can manually install the agent on each machine.

To manually install the client agent

    From the Menu Bar, select Help | Contents then search for Agent-Based Monitoring. Review the help file for detailed information.

To automatically install the client agent

The first step in this process is to add our servers to the software.

Before we trigger the agent installation, I am going to show you how to monitor the installation within the software. Notice the Service Output Tab in the lower left corner. If we drag and drop this tab to the center of the screen we can see the output in the document view pane. This view displays verbose agent installation output so we can see exactly what is happening.

Now that we have added a host to manage, we need to assign a single agent-based template to the host. Once assigned the software will attempt to install the agent on the remote host within one minute.

To assign a template to a host

  • From the Explorer View, use drag-drop to assign the template or
  • Right click on a template then select Template Properties. Use the Template Properties View to assign the hosts to the template.

If we watch the Service Output, we see the following messages indicating the agent has been successfully installed:

AgentInstallerService: Agent is not installed.  Host: Northbowl
AgentInstallerService: Uploading installation file...  Source: C:\Program Files\Corner Bowl\Server Manager 2022\ServerManagerAgentInstaller.exe  Destination: \\Northbowl\C$\WINDOWS\TEMP\ServerManagerAgentInstaller.exe  Host: Northbowl
AgentInstallerService: Remote executing...  File: \\Northbowl\C$\WINDOWS\TEMP\ServerManagerAgentInstaller.exe  Host: Northbowl
If you see an Access Denied error, you can either update the Service credentials to logon as a domain administrator or attempt to impersonate the connection. To impersonate the connection, from the Explorer View, find the host throwing the error, then right click on the host and select Host Properties. The Host Properties View displays. From the Host Properties View, select the Windows Logon As Tab then assign administrator credentials.

Once installed, the agent will connect once every minute. Notice, in the screenshot below, we see three different connection sessions defined by the entries below:

Session [39] - Connected.
Session [39] - WinAuthProtocol: Authenticated \anonymous.
AgentInstallerService: Remote executing...  File: \\Northbowl\C$\WINDOWS\TEMP\ServerManagerAgentInstaller.exe  Host: Northbowl
Agent Server Object(anonymous): IP:  Client Version:  Server Version:
Agent Server Object: Session started.  Remote IP:  Host: Northbowl  Local FQDN: NorthBowl  Local Hostname: NORTHBOWL  Local IP Address:  Session Count: 1
Agent Server Object(anonymous): Client requesting templates...  Host: Northbowl
Session [39] - The connection was terminated by the remote end point.
Agent Installation Messages
Agent Installation Messages

Once connected, we can see some information about the client in the Dashboard. To view the Dashboard:

  • From the Explorer View, click on the Dashboard node. The Dashboard View displays.
  • From the Dashboard View, select the Host Summary Tab.
  • Notice the new host is listed along with the Client Version and the Last Connection time.
Host Summary
Host Summary

Depending on the options you set for the Host Identification, the host may be added with a different name than the name you previously added. In that scenario the host is added to a group called Agent Devices. To see this in action, delete the host then wait for the agent to re-connect. Once reconnected, you will see a new Agent Server group with the host listed in the group.

Agent Devices Group
Agent Devices Group

If the agent has internet access, the agent automatically updates when a new version becomes available, otherwise, Server Manager attempts to update the agent when a new update becomes available. If WMI or Windows Shares access is unavailable from the host the agent is installed, we can configure Server Manager to ignore the host when updating agents. To disable the automatic installation and updates of a host's agent, open the Host Properties View then de-select the Automatically install option located on the General Tab.

Disable Agent Installation
Disable Agent Installation

How to Manually Run the Templates on Demand

The templates we assigned run hourly and daily respectively. To trigger the templates to run the next time the agent connects we need to queue the execution.

  • From the Explorer View, expand Hosts then find the target host.
  • Right click on the target host then select Execute. The template is queued for execution the next time the agent connects.

How to Verify Event Log Files have been Remotely Backed Up

Once the Event Log File Backup template is complete, we can find the saved logs in output directory.


If a client is not connecting, you can troubleshoot on the client-side by remoting into the server, then opening the agent.log file:

C:\ProgramData\Corner Bowl\Server Manager Agent\agent.log

If there is a problem with the target host or other configuration properties you can modify the parameters by opening the configuration file as an administrator in notepad. By default the file is located in:

C:\ProgramData\Corner Bowl\Server Manager Agent\cbsmagt.exe.config
For detailed information on the agent configuration file, search the in-application help for Agent-Based Monitoring.

Last Updated: March 21st, 2024