Tchater maintenant avec le support
Tchattez avec un ingénieur du support

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

Configuring Change History

For selected discovery types such as Active Directory, SQL Server, NTFS, and Registry, change history allows you to report on changes over time to the objects you collect. For example, if you choose to collect the change history for the NTFS discovery type, and a new file is added to a previously collected folder, you can see this reflected in a change history report. For more information, see Best Practices for Creating Discoveries .

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 addition to the discoveries you can create and run in Enterprise Reporter, there is additional information that is common to more than one type of discovery, such as user accounts, groups or group members. To collect change history information for this data, enable change history for the Common discovery type.

To enable or disable change history for a discovery type
1
Click Configuration.
2
Click Manage global change history settings.
A button shows the current status of the change history configuration for each discovery type.
3
Click the Enabled or Disabled button to toggle the setting.
4
Click Close.

Configure Logging

You can set the amount of logging information that is collected from the Enterprise Reporter Server.

Each user of Configuration Manager can also configure the amount of logging information that is collected from each Configuration Manager computer. We recommend the default setting of Debug to collect as much information as possible. The following logging levels are available:

•
Debug
This is the most verbose logging level (maximum volume setting).
•
Information
The Information level is typically used to output information that is useful to the running of ER.
•
Warning
Warning is often used for showing when exceptional behavior has occurred. These can usually be handled without issue.
•
Error
Error is used to log all unexpected errors.
•
Fatal
Fatal is reserved for special exceptions/conditions causing a failure of a component (console or server) with the ER product.

Credential Manager

•
Manage credentials
You can manage credentials for use throughout the system. For more information, see Using the Credential Manager .

Database Settings

•
Database Timeouts
You can increase the timeout for the Enterprise Reporter server. Connection timeouts control how long the server has to establish a connection to the database, while the command timeout controls the amount of time available for processing a command on the database.
For more information, see Troubleshooting Connection Timeouts .
•
Defragment Indices
This option is available for systems running SQL Server Enterprise edition and is enabled by default. When this option is enabled, database indices are defragmented in the background as a regular part of collections to enhance the performance of both collection and reporting tasks.
•
Frequency Threshold
Database indices will become more fragmented from frequent collections or from collections with large amounts of data. If Defragment Indices is enabled, you may optionally set the Frequency threshold to control the minimum amount of time that must elapse between tasks to defragment the database indices.
For example, if the frequency threshold is set to 3 hours, and a defragmentation task finishes at 9am, no other defragmentation task will be allowed to begin until 12 pm at the earliest. For any threshold, only one defragmentation task will run at a time.
Enterprise Reporter running on systems that are not equipped with SQL Server Enterprise edition requires database indices to be defragmented manually during a shutdown using the Database Wizard to Perform Database Maintenance.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation