Chat now with support
Chat mit Support

Enterprise Reporter 3.2.2 - Quick Start Guide

Introducing Quest® Enterprise Reporter Key Features of Enterprise Reporter Enterprise Reporter Components For information on installation, see Installing Enterprise Reporter . System Requirements An Overview of Enterprise Reporter Communications and Credentials Required Installing Enterprise Reporter Step-By-Step Walkthroughs

Change History Reporting

Enterprise Reporter can help you quickly identify changes that have occurred in your environment. If you enable change history, a record of all changes over time is kept. You can then report on these changes, and ensure that required changes have been made, or investigate unwanted changes. You can track changes to:

As part of your job, you are responsible for monitoring changes to critical services. Once a week, you must generate a report to ensure only expected changes are being made. Since collecting change history involves more data, you want to scale up your cluster to handle the increased traffic.

You will need to take the following steps:

Add Another Node to a Cluster

Each target is assigned to a node, balancing the distribution across the nodes until all the nodes are processing as many tasks as they are able. If no nodes are available to process the task, it must wait until a node becomes available.

When you run a computer discovery, each computer in the discovery is separate task that can be assigned to a node. In this case, adding nodes will speed up the performance of your discovery. This is particularly important as we are collecting change history data as well, which will increase the time taken to process each task.

In this scenario, you are going to add another node to handle collecting more data from a larger number of targets.

Click Add.

Enable Change History for the Computer Discovery Type

You configure change history at a global level for each discovery. All discoveries of that type will collect this data. When you create a discovery, the Name page indicates whether change history is enabled for the discovery type.

In this scenario, it is important to enable change history before running the first discovery, so that all changes are captured.

On the Discovery Management | Configuration page, click Configure global change history settings.
For the Computer discovery type, click Disabled to toggle the setting.
Click Close.

Create and Schedule a Discovery

Since you need this weekly, you can create a weekly discovery. In this simple case, we are assuming that the targeted computers are located relatively close together. If they were very dispersed, you would create different discoveries in the appropriate cluster to ensure faster collections. Each computer should only be in one discovery, so while we are going to configure the discovery to collect the minimal needed data, if at a later time more information is needed, this discovery should be expanded, rather than creating a new one to gather the new data.

On the name page, enter Computer Services so you can identify the discovery easily once you have a list of discoveries.
On the Scopes page, click Add to choose your computers.
Browse to locate the computers, click Include, and click OK to close the Browse dialog box.
On the Scopes page, click Import to add computers from a file.
Browse to locate the file containing the computers to add, select the file, click Open to start the import, review the import results, and click OK to close the results screen. For more information, see Importing Computers to Your Scopes.
Click Next.
Click Weekly and schedule the discovery to run once a week.
Click Finish.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen