Enterprise Reporter 3.2.2 - Configuration Manager User Guide

Table 40. Configuration Manager Activity in the event log
Event	Event ID	Event Format
User Login (successful)	2000	User <USERNAME> on machine <MACHINENAME> successfully logged-in to the ConfigurationManager
Create Discovery	2002	User <USERNAME> on machine <MACHINENAME> created discovery '<DISCOVERYNAME>' (<DISCOVERYID>)
Run Discovery (manual)	2003	User <USERNAME> on machine <MACHINENAME> ran discovery '<DISCOVERYNAME>' (<DISCOVERYID>)
Modify Discovery	2004	User <USERNAME> on machine <MACHINENAME> modified discovery '<DISCOVERYNAME>' (<DISCOVERYID>)
Delete Discovery	2005	User <USERNAME> on machine <MACHINENAME> deleted discovery '<DISCOVERYNAME>' (<DISCOVERYID>)
Create Cluster	2006	User <USERNAME> on machine <MACHINENAME> created cluster '<CLUSTERNAME>' (<CLUSTERID>)
Modify Cluster	2007	User <USERNAME> on machine <MACHINENAME> modified cluster '<CLUSTERNAME>' (<CLUSTERID>)
Delete Cluster	2008	User <USERNAME> on machine <MACHINENAME> deleted cluster '<CLUSTERNAME>' (<CLUSTERID>)
Enable Cluster	2009	User <USERNAME> on machine <MACHINENAME> enabled cluster '<CLUSTERNAME>' (<CLUSTERID>)
Disable Cluster	2010	User <USERNAME> on machine <MACHINENAME> disabled cluster '<CLUSTERNAME>' (<CLUSTERID>)
Add Node To Cluster	2011	User <USERNAME> on machine <MACHINENAME> added node <NODENAME> (<NODEID>) to cluster '<CLUSTERNAME>' (<CLUSTERID>)
Remove Node From Cluster	2012	User <USERNAME> on machine <MACHINENAME> removed node <NODENAME> (<NODEID>) from cluster '<CLUSTERNAME>' (<CLUSTERID>)
Enable Node	2013	User <USERNAME> on machine <MACHINENAME> enabled node <NODENAME> (<NODEID>) on cluster '<CLUSTERNAME>' (<CLUSTERID>)
Disable Node	2014	User <USERNAME> on machine <MACHINENAME> disabled node <NODENAME> (<NODEID>) on cluster '<CLUSTERNAME>' (<CLUSTERID>).

You can interrogate the event log directly for object user activity information. As shown in Table 40, each event is logged with the fully qualified user name of the Enterprise Reporter user who performed the event and the machine name where the event occurred.

Report Manager Event Log

Table 41. Report Manager Activity in the event log
Event	Event ID	Event Format
User Login (successful)	2000	User <USERNAME> on machine <MACHINENAME> successfully logged-in to the ReportManager
Create Report	2015	User <USERNAME> on machine <MACHINENAME> created report '<REPORTNAME>' (<REPORTID>)
Run Report (manual)	2016	User <USERNAME> on machine <MACHINENAME> created report '<REPORTNAME>' (<REPORTID>)
Modify Report	2017	User <USERNAME> on machine <MACHINENAME> modified report '<REPORTNAME>' (<REPORTID>)
Delete Report	2018	User <USERNAME> on machine <MACHINENAME> deleted report '<REPORTNAME>' (<REPORTID>)

Encryption Event Log

Table 42. Encryption Activity in the event log

Event

Event ID

Event Format

Security Audit Operation

2020

User <USERNAME> on machine <MACHINENAME> with IP <IPADDRESS> performed <OPERATIONNAME> operation using service contract <SERVICECONTRACTNAME>.

Operations that may be performed are:

•

IsUserInRole - checks the role of the calling user

•

GETIvKey - returns Enterprise Reporter encryption IV key

•

ImportIvKey - sets a new security key

•

GenerateIvKey - generates and sets a new IV key

•

CheckOrUpgradeKey - check the status of the security key and performs an upgrade if possible

•

ResetAllPasswords - resets all passwords

Resolving Configuration Manager Issues

The Configuration Manager is used to configure your data collection. Collecting data involves your network security, which can occasionally cause problems.

Node Issues

A node is a computer assigned to a cluster and is responsible for processing discoveries. In this section, you will find troubleshooting for the following issues related to nodes:

•

Node Deployment Issues

•

Dealing with Unassociated Nodes

•

Dealing with Faulted Nodes

•

Problems Deleting a Node

•

Changing the Node Logging Level

•

Changing the Size of the Node Log Files

Node Deployment Issues

If something goes wrong with your node deployment or upgrade, you can manually install and configure the node. When you manually install a node, it appears in the Configuration Manager as an unassociated node.


	NOTE: You must have administrative permissions on the node host computer to install the node.


	NOTE: If the node host computer is behind a firewall, you must manually install the node.


	NOTE: Performance counters must be enabled on the node machine as the performance information is required by the Enterprise Reporter node performance optimization functionality.

Before you begin:

•

Note the port being used by the Enterprise Reporter server service.

•

For nodes requiring an alternate port, make note of an available port.

The default port is 7737.

•

Ensure the node account is a member of the Reporter_Discovery_Nodes group.

•

If applicable, remove the node in the Configuration Manager. For more information, see What does the status of a node or cluster indicate? .

•

If necessary, use the Control Panel to uninstall the node.