Chat now with support
Chat with Support

Enterprise Reporter 3.5 - 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 Overview of Enterprise Reporter communications and required credentials Installing Enterprise Reporter Step-By-Step Walkthroughs

Scheduling Report Delivery to Recipients

Once the data has been collected, the reports can be generated. Using the Schedule tab of the Report Manager, you can create a schedule that will automatically deliver the desired reports to your specified recipients.

To do this, you must:

1
On the Report tab of the Report Manager, expand Report Library | Active Directory.
2
Locate the Domain Users without Recent Logons report, and drag it into the My Reports container.
If you did not rename the report when you modified an existing report (see Modify an Existing Report), the report will have a (1) after its name so you can differentiate them.
2
Click +New Schedule.
3
Name the schedule Compliance Reports.
4
Click Monthly, and select day 1 of the month.
2
Click Configure mail server, and enter the server name and port number.
6
1
2
Select Domain Users without Recent Logons, and click OK.
3
Click the Modify Report Parameters icon for the Domain Users without Recent Logons report.
4
In the Report Parameters pane, complete the Parameter Set Name: by typing [Domain Name] Users not logged in for 90 days to identify the parameter values you will use.
5
In the Include the following domains parameter, type the domain name, and click Add.
You can also click Search, locate and add the domain, and click OK.
6
In the Users not logged on in the last (days) parameter, change the number of days to 90.
7
Click Save.

Your report will now run automatically, reporting on the data from your scheduled discovery.

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.

5
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.

1
On the Configuration page, click Manage global change history settings.
2
For the Computer discovery type, click Disabled to toggle the setting.
3
Click Close.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating