• Become a portal pro
• Download
• Print
• My Downloads ()

• Support
• Technical Documentation
• Enterprise Reporter 3.5.2
• Enterprise Reporter 3.5.2 - Quick Start Guide

Enterprise Reporter 3.5.2 - Quick Start Guide

Table of Contents  

Introducing Quest® Enterprise Reporter Key Features of Enterprise Reporter Enterprise Reporter Components

Enterprise Reporter Architecture

System Requirements Overview of Enterprise Reporter communications and required credentials

Node credential and alternate credential details for on-premises discoveries Detailed permissions for Enterprise Reporter discoveries Permissions for Enterprise Reporter discoveries on NAS devices Permissions for Enterprise Reporter tenant applications Minimum permissions for installing Enterprise Reporter Minimum permissions for installing Enterprise Reporter Kerberos Requirements Port Requirements

Installing Enterprise Reporter

Create/Connect Your Enterprise Reporter Database Configure Enterprise Reporter Licenses Activating or Updating Your License Create Your First Enterprise Reporter Cluster and Node

Step-By-Step Walkthroughs

Pre- and Post-Migration Assessment

Configure a cluster for data discovery Create a discovery to define the data collection Run the discover to collect the data Run the reports you want and export them

Manage Compliance

Modifying an Existing Report Scheduling the Discovery Scheduling Report Delivery to Recipients

Changing History Reporting

Add Another Node to a Cluster Enable Change History for the Computer Discovery Type Create and Schedule a Discovery Scheduling the Report

File Storage Consolidation

Configure a Cluster to Perform the Data Discovery Create Discoveries to Define the Data Collection Run the Discoveries to Collect the Data Run the Reports You Need

Microsoft 365 and Microsoft Entra ID Reporting

Setup Enterprise Reporter Microsoft Entra Applications for Microsoft 365 Discoveries Create a Discovery to Define the Data Collection Run the Discovery to Collect the Data Run the Reports

• Viewing Topics 13 - 16 of 44

×

Kerberos Requirements

If the network is using Kerberos for authentication, then there is an option to enter a UPN or SPN for both the Enterprise Reporter server and the node during install. This allows the node and Enterprise Reporter server to communicate in a Kerberos only environment.

Port Requirements

For the Enterprise Reporter components to communicate, some ports must be open.

•

The default port used for communication between the server and the consoles is 7738. This port is also used by the nodes to access the server. The port is configured during installation of the server, and is required in the connection dialog box for both the Configuration Manager and the Report Manager.

You can view the port currently in use on the Information page in the Configuration Manager, and the System Information tab in the Report Manager.

•	The default port used for communication from the Enterprise Reporter server to the nodes is port 7737. This port may be configured during installation.

The following figure shows the ports that are used by the various Enterprise Reporter components.

Figure 3. Ports used by Enterprise Reporter components.

*For more information on ports used when creating a discovery, see Table 18.

**For more information on ports used during data collections, see Table 19.

The following table shows the ports used by all of the Enterprise Reporter components.

 

Table 18. Ports used by Enterprise Reporter components

			Configuration Manager	Report Manager	SQL Server	ER Server	ER Nodes
Application	Port	Type	Components
FTP	20, 21	TCP		X
SMTP	25	TCP	X	X		X
WINS / NetBiOS Name Resolution	42	TCP UDP				X
DNS FQDN Resolution	53	TCP UDP	X	X		X
Kerberos	88	TCP UDP	X			X
RPC Service & Endpoint Mapper / WMI	135	TCP UDP	X
NetBIOS Name Service	137	UDP				X
NetBIOS Datagram (browsing)	138	UDP	X
LDAP	389	TCP UDP	X
SQL	1433	TCP		X	X	X	X
SQL Server Browser Service	1434	TCP UDP	X	X
Enterprise Reporter Node	7737	TCP				X	X
Enterprise Reporter Server	7738	TCP	X	X		X	X

The following table outlines the ports used by all of the Enterprise Reporter discoveries.

.

Table 19. Ports used by Enterprise Reporter discoveries

Active Directory

Microsoft Entra ID

Azure Resource

Computer

Exchange

Exchange Online

File Storage Analysis

Microsoft Teams

NTFS

OneDrive

Registry

SharePoint Online

SQL Server

Application

Port

Type

Discoveries

WINS / NetBiOS Name Resolution

42

TCP UDP

X

X

X

X

X

X

X

DNS FQDN Resolution

53

TCP UDP

X

X

X

X

X

X

X

HTTP

80

TCP

X

X

X*

X

X

X

X

X

Kerberos

88

TCP UDP

X

X

X*

X

X

X

X

RPC Service & Endpoint Mapper / WMI

135

TCP UDP

X

X

X

X

X

NetBIOS Name Service

137

UDP

X

X

X

X

X

X

X

Remote Registry

139

TCP

X

X

X

X

X

ICMP

X

X

X

X

X

LDAP

389

TCP UDP

X

X

X

X

X

X

X

HTTPS

443

TCP UDP

X

X

X

X

X

X

SMB / Remote Registry

445

TCP

X

X

X

X

X

X

LDAP Secure

636

TCP

X

DCOM on XP/2003 and below (uses an open port in this range)

1024 - 5000

TCP UDP

X

X

X

X

X

SQL

1433

TCP

X

X

X

X

X

X

X

X

X

X

X

X

X

SQL Server Browser Service

1434

UDP

X

LDAP GC

3268

TCP

X

X

WinRM

5985 5986

TCP UDP

X

X

X

DCOM on Vista/2008 and above (uses an open port in this range)

49152 - 65535

TCP UDP

X

X

X

X

X

X

X

*Exchange 2013 and higher

The following figures outline the ports used by the Enterprise Reporter discoveries.

Figure 4. Ports used by Active Directory collections

Figure 5. Ports used by Microsoft Entra ID and Microsoft 365 collections (Exchange Online, MS Teams, OneDrive, and SharePoint Online)

Additional ports for Microsoft Entra ID and Microsoft 365 discoveries to be set on the Node:

•	Open ports 49151-65535 TCP Outbound

•	Open ports 49151-65535 UDP Outbound

 

Figure 6. Ports used by Computer collections

Figure 7. Ports used by Exchange collections

Additional port for Exchange discovery to be set on the Node:

•	Open WinRM HTTP port 5985 TCP Outbound

 

Figure 8. Ports used by File Storage Analysis collections

Figure 9. Ports used by NTFS collections

Figure 10. Ports used by Registry collections

Figure 11. Ports used by SQL collections

Installing Enterprise Reporter

Once you have ensured that your computers meet the system requirements, you can install the Enterprise Reporter server and consoles, and set up the Enterprise Reporter database. For full information on installing Enterprise Reporter, see “Installing and Configuring Enterprise Reporter” in the Quest Enterprise Reporter Configuration Manager User Guide.

To install Enterprise Reporter components

1	Open the self-extracting file named Enterprise_Reporter_<version number>_x64.exe.

2	Select a location for the extracted files.

3	In the folder Quest Enterprise Reporter\en-US double-click the Enterprise_Reporter_<version number>_x64.msi file.

4	On the Welcome screen of the Setup Wizard, click Next.

5	Click View License Agreement and scroll to review the entire license agreement.

Optionally, click Print to send a copy of the agreement to the printer.

6	Select I accept these terms, click OK to close the agreement, and click Next to continue the installation.

- OR -

Select I do not accept these terms, click OK to close the agreement, and click Cancel to exit the installation.

7	To install all components, click Next.

- OR -

•	To install individual components, click the drive icon for each component, select the desired option, and click Next.

If you have selected to not install the Reporter Server, and the network is using Kerberos for authentication, then enter a UPN or SPN.

Clicking Reset restores the default setting of installing all components.

8	If you select the Reporter Server component without the Database Wizard component, a warning that the Database Wizard will be installed automatically is displayed. Click Next to continue.

9	If you are installing the Enterprise Reporter server:

•	Specify the credentials to be used by the Enterprise Reporter server service.

This service account must be able to access the SQL Server where the Enterprise Reporter database resides.

•	If the network is using Kerberos for authentication, then enter a UPN or SPN for the Enterprise Reporter server to use.

•	Verify the default port of 7738 to be used for the Enterprise Reporter server.

If the default port 7738 is in use, specify an alternate port for the server.

10	Click Next.

11	Click Install.

12	Click Close.

If errors are encountered during installation they are listed on this page.

13	If you have installed the server, you must configure the database.

- OR -

If you have installed the Configuration Manager or Report Manager without the server, you must add the required user to the proper security group or they cannot open the console.

For more information, see Role Based Security in Enterprise Reporter in the Quest Enterprise Reporter Installation and Deployment Guide.

Create/Connect Your Enterprise Reporter Database

Next, you must create the Enterprise Reporter database. The Database Wizard appears automatically when you install the Enterprise Reporter server.

1	Choose Create New Database, and click Next.

2	Enter the target SQL Server instance.

You can either type the instance name or browse to it. If you browse, you will see all SQL Servers in your subnet that are configured to advertise their presence. If you do not see your server on the list, you must type the name.

3	Type a name for your database.

- OR -

Type the name of the existing empty database to be connected, or browse to it.

4	Select the preferred type of authentication to use to connect to the SQL Server and click Next.

Enterprise Reporter connects to the SQL Server using Windows authentication by default. If you want to connect using SQL credentials, enter them before clicking Next.

5	Select the appropriate level of encryption for the data sent between the client and SQL server.

NOTE: Enterprise Reporter supports TLS 1.3; however, TLS 1.2 remains a requirement since SQL Server 2022 satellite services require TLS 1.2 to be enabled. For more information on TLS support, see Microsoft documentation.

•	Strict (SQL Server 2022): Select this option for SQL Server 2022 and Azure SQL Managed Instance or when the instance has Force Strict Encryption enabled.

•

Mandatory: Select this option when the instance has Force Encryption enabled. It can also be used when no encryption is configured for the instance, but Trust server certificate is enabled. While this method is less secure than installing a trusted certificate, it does support an encrypted connection.

•

Optional

Enabling Trust server certificate, when 'Optional' or 'Mandatory' encryption is selected, or if the server enforces encryption, means that SQL Server will not validate the server certificate on the client computer when encryption is enabled for network communication.

Under Host name in the certificate, you can provide an alternate, yet expected, Common Name (CN) or Subject Alternative Name (SAN) in the server certificate. You would use this option when the server name does not match the CN or SAN, for example, when using DNS aliases. Leaving this option blank allows certificate validation to confirm that the CN or SAN matches the server name.

Enterprise Reporter validates the SQL Server and your right to create a database on the instance before you can proceed to the next step.

6	If necessary, adjust the initial database size or file paths, and click Next.

Use the Database Estimator tool for further information based on the types of collections being performed.

7	If required, enter the domain of the Enterprise Reporter server’s service account.

8	Enter the names for the security groups, and click Next.

Using the default group names is recommended.

9	Review the message box, and click OK to continue.

- OR -

Click Cancel to further modify the Security Group Names.

10	Optionally, accept the default to open Configuration Manager.

Once the database is created, you will use the Configuration Manager to enter the Enterprise Reporter licenses and configure the collection of network information.

11	Click Finish to create the database.

A task progress dialog will be displayed as the database is created.

12	When creation is complete and successful, a notice to backup the encryption key is displayed. Click OK to accept the message and start the Encryption Key Manager.

IMPORTANT: It is important to backup the encryption key. The Encryption Key Manager will automatically start on the Enterprise Reporter Server. Use the Export Key option to create a back up file of the encryption key. For more information, see Appendix: Encryption Key Manager .

- OR -

If errors were encountered during database creation, an error dialog box displays.

 

•  Previous
• Viewing Topics 13 - 16 of 44
• Next 

Search this document Search all documents for this product-version Search all documents for this product Search all documents

×

 Welcome to Quest Support

You can find online support help for Quest *product* on an affiliate support site. Click continue to be directed to the correct support content and assistance for *product*.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating

© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center