지금 지원 담당자와 채팅
지원 담당자와 채팅

Enterprise Reporter 3.5.1 - Configuration Manager User Guide

Product Overview Configuring the Configuration Manager
Starting the Configuration Manager Finding answers and getting help Overview of Enterprise Reporter Communications and Credentials Required Using the Credential Manager Setting Up Your First Collection Computers (Nodes) Modifying Your Deployment Configuring Global Settings Customizing the Configuration Manager View
Understanding Discoveries Creating Discoveries
Step 1. Create the Discovery (Name) Step 2. Choose what to include in your discovery (Scopes) Step 2a. Choose scopes for your on-premises discoveries
Choosing your Active Directory Scopes Choosing your Computer Scopes Choosing Your Exchange Scopes Choosing Your File Storage Analysis Scopes Choosing Your Microsoft SQL Scopes Choosing Your NTFS Scopes Choosing Your Registry Scopes
Step 2b: Choose scopes for your cloud discoveries Step 3. Schedule your Discovery Step 4: Review the summary
Managing Discoveries Troubleshooting Issues with Enterprise Reporter Appendix: PowerShell cmdlets Appendix: Encryption Key Manager Appendix: Log Viewer

Auditing Enterprise Reporter Activity

User activity from the Configuration Manager, the Reporter Manager console, and Encryption is stored in the Quest Enterprise Reporter Windows Event Log on the machine for the Enterprise Reporter Server. Using this information, you can audit the following user activity for compliance purposes.

The following information is provided in the event log.

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 53, 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.

 

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>)

 

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:

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.

See also:

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

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.

The following requirements must be met:

Before you begin:

Click Change to choose another folder, then click Next.
9
Click Install, then click Finish.
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택