Chat now with support
Chat with Support

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

Using the Database Wizard to Create or Connect a Database

The Database Wizard is used to create or connect an Enterprise Reporter database. You can either create the database when the wizard is automatically launched after installing the Enterprise Reporter server, or launch the wizard as a stand-alone application.

* 
NOTE: The Database Wizard is installed with the Enterprise Reporter server by default.
To create a database using the Database Wizard
* 
NOTE: If you use the Database Wizard on the same computer as the Enterprise Reporter server, when the database creation is complete, the Enterprise Reporter server service is restarted, and the server will be connected to the new database. If you create the database on a different computer, you must change the database to which you are connected. See Changing the Connection to the Enterprise Reporter Database .
•
Click the Start menu, select All Programs | Quest | Enterprise Reporter | Database Wizard and click Next.
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.

For more information, see Security Groups in Enterprise Reporter .

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.

For help troubleshooting errors, see Database Configuration Issues .

13
Click Cancel.

Upgrading a Database

The Enterprise Reporter database must be the same version as the Enterprise Reporter server. You can use the Database Wizard to upgrade your database outside of the installation process.

To upgrade an Enterprise Reporter database
* 
CAUTION: It is recommended that you back up your Enterprise Reporter database and encryption key before beginning this process. You cannot undo this operation once it has started.
 
* 
NOTE: Once an upgrade has started, all connections to the database will be closed and the database will be unavailable until the upgrade completes successfully.
1
If you are starting the Database Wizard from the Start menu, click the Start menu and select All Programs | Quest | Enterprise Reporter | Database Wizard and click Next.
- OR -
If the Database Wizard is already running, skip this step.
2
Choose Select/Upgrade Existing Database and click Next.
3
Enter the target SQL Server.
You can either type the SQL Server 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.
4
Confirm database name.
You can type a database name or browse to find one. Enterprise Reporter validates that the database exists, and is a valid Enterprise Reporter database. If the Browse dialog box is empty, ensure the SQL Server is correct. Or, try using different credentials since only databases to which the current credentials have access are shown.
5
Confirm which type of authentication to use to connect to the SQL Server and click Next.
6
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 connects to the SQL Server using Windows authentication by default. If you want to connect using SQL credentials, enter them.
7
Confirm that you backed up the encryption key using the Encryption Key Manager and click Next.
If the database is from a previous version of Enterprise Reporter, the database automatically upgrades.
8
Confirm that you have created a backup of your database by selecting I understand and wish to continue and click Next.
9
If the Domain Local security group type was not selected during creation of the existing Enterprise Reporter Database, you are asked to confirm that you wish to continue with the original security group type.
Using the Domain Local group type is recommended. For information on security groups, see Security Groups in Enterprise Reporter .
10
If required, enter or browse to the domain of the Enterprise Reporter server service account.
11
Confirm or edit the names for the security groups and click Next.
12
Review the warning message and click OK to continue.
- OR -
Click Cancel to further modify the Security Group Types or the Security Group Names.
13
To complete the database upgrade, click Finish.
If errors occur during an upgrade, they are detailed at the end of the process. For more information, see Database Configuration Issues .
A task progress dialog is displayed during the upgrade process.
14
When the upgrade completes successfully, click OK to open the Encryption Key manager.
15
Select the Export Key option to create an encryption key backup file. For more information, see Exporting a key file .
- OR -
Select the Import Key option to import an encryption key backup file. For more information, see Importing a key file .

Deleting a Database

If you no longer want an Enterprise Reporter database, you can use the Database Wizard to remove it from the SQL Server. You must have rights to remove a database.

 
* 
TIP: It is recommended that you do not delete the database currently in use by the server. If you delete the current database, the Enterprise Reporter server service cannot start, and you will be unable to open the Configuration Manager or the Report Manager. This option is intended for deletion of Enterprise Reporter databases no longer in use.
To delete a database using the Database Wizard
1
Click the Start menu and select All Programs | Quest | Enterprise Reporter | Database Wizard.
2
Click Next.
3
Select Remove Database.
4
Enter the SQL Server where the database is stored.
You can either type the SQL Server 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.
5
Enter or browse to the database to remove and click Next.
Enterprise Reporter uses the stored connection settings to connect to the SQL Server®. If you want to change the type of authentication or the SQL credentials, enter them before clicking Next.
Enterprise Reporter validates the SQL Server and your right to remove a database on it before you can proceed to the next step.
6
Click Finish to remove the database.

Changing the Security Mode

You can use the Database Wizard to change the security mode of the SQL Server where your database resides. SQL servers can use either Windows authentication (Integrated mode), or Windows and SQL authentication (Mixed mode). Changing the security mode may grant access to additional groups and revoke access from already configured groups, so exercise caution with this option.

* 
NOTE: If you change the security mode, it affects all databases on the SQL Server, not just the Enterprise Reporter database. You must have adequate rights on the SQL Server to make this change.

If you change the security mode to Windows, any service configured to connect to the SQL Server using SQL authentication will fail.

To change the security mode of the SQL Server
1
Click the Start menu and select All Programs | Quest | Enterprise Reporter | Database Wizard.
2
Click Next.
3
Select Change Security Mode and click Next.
4
Enter the target SQL Server.
You can either type the SQL Server 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.
5
Confirm the database name.
You can type a database name or browse to find one. Enterprise Reporter validates that the database exists and is a valid Enterprise Reporter database. If the Browse dialog box is empty, ensure the SQL Server is correct. Or, try using different credentials, as only databases to which the current credentials have access are shown.
6
Confirm which type of authentication to use to connect to the SQL Server and click Next.
7
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 connects to the SQL Server using Windows authentication by default. If you want to connect using SQL credentials, enter them.
8
Change to the desired mode, and click Next.
9
Click Finish to change the security mode.
* 
NOTE: You must restart the SQL Server service for this change to take effect.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating