サポートと今すぐチャット
サポートとのチャット

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

Changing the Size of the Node Log Files

Enterprise Reporter writes to log files. By default, the node logging level is set to Warning and the cumulative size of the log files is set to 1000 MB. You can manage the log files within each discovery cluster by setting the node logging level and the cumulative size of the log files. For information on changing the node logging level, see Changing the Node Logging Level .

3
Click Apply.

Scope Enumeration Issues

When selecting scopes in an on-premises discovery such as NTFS or Active Directory, the credentials in use determine the available scopes. Depending on your discovery, you may be:

If you are using alternate credentials, and no scopes are available, this may indicate a DNS issue. Ensure the credentials you are using are fully qualified.

Data Collection Issues

You may run into situations where not all of your data is collected, or even no data is collect at all. The first thing you need to determine is what tasks in the discovery are failing. Once you have located the problem tasks, you can use the errors and statistics generated to pinpoint the problem.

There are several other things that you can examine:

During an Active Directory discovery, if collection issues are related to overloaded domain controllers, disable Create multiple tasks for each domain and specify multiple domain controllers for the domain instead. For details, see AD Discovery: Optionally select one or more domain controllers .
The node may not have access to that server. Check your credentials, and change them if necessary. For details, see Node credential and alternate credential details for on-premises discoveries .

See also:

Computer Discovery Errors

This section outlines some of the errors that may occur during collection and some suggested approaches for resolving them.

 

Retrieving addresses: access is denied

- OR -

Retrieving cached logon count: Requested registry access is not allowed

 

The service account, or the alternate credentials used in the Computer discovery does not have administrator access on the remote server. The account requires local Administrator rights on each target.

To verify, run regedit.exe as the service account (by holding shift and right-clicking on the executable to run with different credentials) and attempt to connect to the remote server.

Issues collecting computer information

Ensure that Windows Firewall exceptions are added for File and Printer sharing (SMB-In) and Windows Management Instrumentation (WMI).

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択