Chat now with support
Chat with Support

Quest has tools and processes in place to identify, protect, detect, and remediate vulnerabilities and incidents when they occur, including external security partners. As part of our standard security operations, Quest does not use CrowdStrike in any of our operations. We are reviewing our third parties, and so far, there is minimal affect. It is Quest's policy not to provide further technical details unless they directly impact customer data.

Enterprise Reporter 3.5.1 - Installation and Deployment Guide

Product Overview Installation Considerations for Enterprise Reporter Installing and Configuring Enterprise Reporter Managing Your Enterprise Reporter Deployment Troubleshooting Issues with Enterprise Reporter Appendix: Database Content Wizard Appendix: Encryption Key Manager Appendix: Log Viewer

Checking the Enterprise Reporter configuration after recovery

Start the Configuration Manager and check the health of the recovered Enterprise Reporter configuration.

2
Select Information.
3
Click the Discovery Nodes tab.
5
Select Yes on the popup message.
6
Select Discovery Management and click Manage Discoveries.

 

Appendix: Database Content Wizard

The Enterprise Reporter Database Content Wizard can be started from the Windows Start menu or from within the main Database Wizard.

To run the Database Content Wizard, you must have control and alter permission on the database. During installation, if the sa account is not selected, the Enterprise Reporter service account is added as a member of the Discovery_Admin_Role and Discovery_Nodes_Role roles. Both accounts have control and alter database permissions.

The Enterprise Reporter Database Content Wizard allows you to perform the following tasks on the information stored in Enterprise Reporter SQL Server® Databases:

Software Requirements

Starting and Configuring the Enterprise Reporter Database Content Wizard

1
Start the main Database Wizard by clicking the Start menu, and select All Programs | Quest | Enterprise Reporter | Database Content Wizard.
2
Optionally, click Advanced Settings to configure how long the server will wait for a response.
3
Optionally, set the SQL Server Connection Timeout.
4
Optionally, set the SQL Server Command Timeout.
5
Optionally, click Reset to defaults to restore both timeouts to 60 seconds.
6
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating