Chat now with support
Chat mit Support

Enterprise Reporter 3.5 - 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

Exporting Logs from the Configuration Manager

Exporting Logs for Discoveries

Logs can be used to troubleshoot issues with discoveries. Logs are collected from the Reporter server and all of the nodes within a selected cluster, and zipped into files that can be sent to Quest Support to help resolve certain collection problems. The log files are all sent to the Exported Logs folder on the Reporter server. You may have several different .zip files, which may take some time to appear, depending on your configuration:

•
A ServerLogs.zip file containing the logs from the server.
•
A <Computer Name>_NodeLog.zip file for each node in the cluster.
To export logs
1
On the Manage Discoveries pane, select a discovery.
By selecting a discovery first, the correct cluster for the discovery is automatically chosen.
2
Click the Manage Logs button and select Export Logs.
3
If necessary, change the selected cluster.
4
Click Export.
An Export Logs dialog box appears giving a status of the node logs retrieved. Log retrieval may take time depending on the log size and node location on the network. Once the node logs have been retrieved, a link is displayed for the exported logs.
5
Click the link to locate your zip files.
Zip files are all located in the \ProgramData\Quest\Enterprise_Reporter\Exported_Logs folder.
You can now email your log files to your Quest Support representative.
6
Click Close.

 

* 
NOTE: To help diagnose issues, the ServerLogs.zip contains additional files including the DatabaseMaintenance.log file and a SQLLite file containing Enterprise Reporter system configuration information.
Deleting Logs for Discoveries

If you want only the most recent issue to be displayed in the logs, you can delete old logs. This deletes logs from the default server Logs folder as well as from the Exported Logs folder, except for the most recently exported logs. You can delete logs for a selected cluster or you can delete all server logs.

To delete logs for a selected cluster
1
On the Manage Discoveries pane, select a discovery.
By selecting a discovery first, the correct cluster for the discovery is automatically chosen.
2
Click the Manage Logs button and select Delete Logs.
3
If necessary, change the selected cluster.
4
Click Delete.
To delete all server logs
1
On the Manage Discoveries pane, select a discovery.
By selecting a discovery first, the correct cluster for the discovery is automatically chosen.
2
Click the Manage Logs button and select Delete Logs.
3
Select all the clusters.
If you do not select all the clusters, some node logs may remain without their related server logs.
4
Select the Delete all server logs check box.
5
Click Delete.
Exporting the Configuration Manager Logs

The Configuration Manager logs can be used to troubleshoot issues with the Configuration Manager service. Information is collected from the Configuration Manager service and is zipped into log files that can be sent to Quest Support to help resolve certain Configuration Manager problems. The log files are sent to the desktop on the Configuration Manager computer and may take some time to appear, depending on your configuration:

To export Configuration Manager logs
1
Click Information.
2
Under Client Logging Information, click Export Configuration Manager logs.
3
Click Export.
4
Click the link to locate your zip file.
You can now email your log files to your Quest Support representative.
5
Click Close.
Viewing the Configuration Manager Logs

You can unzip and view the Configuration Manager logs using the Log Viewer.

To view the Configuration Manager logs
1
Click Information.
2
Under Log Viewer, click View logs to open the Log Viewer.

Viewing information about your Enterprise Reporter configuration

Understanding your system setup can be useful when troubleshooting. You can use the Information page to determine where your console, Reporter server and Reporter database are hosted, what port the server is using to communicate, your software version, and other similar information you may find helpful in resolving issues.

To view system information in the Configuration Manager
•
On the Navigation pane, click Information.

Viewing Errors and Statistics for Tasks

For each task of a discovery, you can view collection options, errors, and statistics. These may be helpful when you experience failed collections, data that does not match your expectations, or when working on performance issues. To display the collection options for a task, hold the mouse over any column of data for that task.

For more information, see Viewing Errors and Error Suppressions and Viewing Statistics .

Technical Documentation.

 

Moving the Enterprise Reporter database

The following summary outlines line how to move the Enterprise Reporter Database from one SQL Server to another SQL Server.

•
Backup the database on SQL Server
•
Restore the database from a backup to the new SQL Server
•
Connect Enterprise Reporter to the new database location
•
Verify that the database has been moved successfully

The following procedures assume that you have the following permissions:

•
SQL permissions to access SQL Server Management Studio on both the current and new SQL Server to backup and restore the SQL database.
•
Windows account permissions to copy the database file from one server to another, and to stop and start services on the Enterprise Reporter server.
To back up the Enterprise Reporter database (dbReporter) on SQL Server
1
Open Enterprise Reporter and stop all node services in the Configuration Manager.
2
On the Enterprise Reporter Server, stop the Quest Enterprise Reporter Server services (and the Quest Enterprise Reporter Node services if a node was deployed on the Enterprise Reporter server).
3
Start SQL Management Studio and connect to the SQL Server where the dbReporter database resides.
4
Expand the database node.
5
Right-click on the dbReporter database and select Tasks | Back up.
6
In the Back Up Database dialog, note the location and name of the dbReporter database backup and click OK.
To restore the Enterprise Reporter database (dbReporter) from a backup to the new SQL Server
1
Copy the .BAK file(s) to the new SQL Server.
2
Start SQL Management Studio on the new SQL Server.
3
Right-click on the database’s node and select Restore Database.
4
Under Source, select Device, click the ellipsis (…).
5
Click Add and browse to the backup copies.
6
Click Add, select the .BAK file, and click OK twice.
7
Under Backup sets to restore, select Restore beside the backup name.
8
From the Restore database window, click OK to restore the database.
To connect Enterprise Reporter to the new Database location
1
On the Enterprise Reporter server, stop the Quest Enterprise Reporter Server (and the Quest Enterprise Reporter Node if a node was deployed on the Enterprise Reporter server).
2
You may have more than one node deployed, so be sure to stop all node services.
3
On the Enterprise Reporter server, select All Programs | Database Wizard.
4
Choose Select/Upgrade Database and click Next.
5
Browse to (or type in the name of) the new SQL Server and make sure the Enterprise Reporter database name is correct (for example, dbReporter), and click Next.
6
Accept the defaults on the Security Groups screen and click Next.
7
Click OK on the Database Maintenance Wizard popup that appears regarding replication.
8
Click Finish to initiate the database configuration.
9
Click OK upon completion.
10
Once you are returned to the Main Menu of the Database Wizard, click Close.
11
Start the Enterprise Reporter Server service.
12
Start all Enterprise Reporter node services.
To verify that the database has been moved successfully
1
Open Configuration Manager Information and confirm the database location.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen