Enterprise Reporter 3.5 - Quick Start Guide

Table 11. Credential Use and Required Permissions
Credentials	Used For	Permissions Needed
Logged in user	Installing the components of Enterprise Reporter	Administrator access on the local computer.
	Creating the Enterprise Reporter database, roles and logins on the SQL Server® (unless SQL credentials are provided)	Must have the right to create databases, logins and groups.
	Creating the security groups	Depends on the type of groups that are chosen, but must have the right to create groups in the chosen environment.
	Securing the Configuration Manager and the Report Manager. The logged in user is added to the Reporter_Discovery_Admins, Reporter_Reporting_Admins, Reporter_Reporting_Operators, and Reporter_Discovery_Nodes security groups as an administrator for both consoles when installing the server.
Service Account Supplied during installation	Installing and running the Enterprise Reporter server	Login as service right is conferred on the service account by the logged in credentials during installation.
	Connecting to the Enterprise Reporter database (unless SQL permissions are provided)	Read and write permissions are automatically granted during database creation.
	Securing the Configuration Manager and Report Manager. The service account is automatically added to the Reporter_Discovery_Admins, Reporter_Reporting_Admins, Reporter_Reporting_Operators, and Reporter_Discovery_Nodes security groups when installing the server.
Optional SQL credentials Supplied during installation	Can be used to create the Enterprise Reporter database	Must have the right to create databases, logins and groups.
Optional SQL credentials Supplied during installation	If supplied, are used to connect the database by the Enterprise Reporter server.	Read and write permissions are automatically granted during database creation.

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 12.

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

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

Table 12. 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 13. Ports used by Enterprise Reporter discoveries
			Active Directory	Azure Active Directory	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
DCOM on Vista/2008 and above (uses an open port in this range)	49152 - 65535	TCP UDP				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 Azure and Office 365 collections (Exchange Online, MS Teams, OneDrive, and SharePoint Online)

Figure 6. Ports used by Computer collections

Figure 7. Ports used by Exchange collections

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

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

Select a location for the extracted files.

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

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

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.

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.

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.

Clicking Reset restores the default setting of installing all components.

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.

If you are installing the Enterprise Reporter server, specify the credentials to be used by the Enterprise Reporter server service and click Next.

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

If you are installing the Enterprise Reporter server, verify the default port of 7738 to be used for the Enterprise Reporter server, and click Next.

- OR -

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

Click Install.

Click Close.

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

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.

Choose Create New Database, and click Next.

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.

Type a name for your database.

- OR -

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

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.

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

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.

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

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

Using the default group names is recommended.

Review the message box, and click OK to continue.

- OR -

Click Cancel to further modify the Security Group Names.

Optionally, accept the default to open Configuration Manager.

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

Click Finish to create the database.

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

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 .