Enterprise Reporter 3.5 - Installation and Deployment Guide


	NOTE: In order to create the database, the currently logged in account must have appropriate rights (including SysAdmin rights) on the SQL Server®, or you must use appropriate SQL credentials. NOTE: In order to upgrade the database, the currently logged in account must have db-owner rights on the SQL Server, or you must use appropriate SQL credentials. NOTE: In order to create groups, the currently logged in account must be able to add groups to the domain’s Users OU, and be able to add members to groups.

•

If you use an existing database, you can connect to it during the installation process. You must know the database name and the SQL Server® where it resides.


	CAUTION: Any existing database will automatically be upgraded (even if it is new and empty). Ensure you back up the database before beginning.

•

If you complete the installation process without a fully functioning database, use the Database Wizard to create a new database. For more information, see Using the Database Wizard to Create or Connect a Database .


	NOTE: Enterprise Reporter must have a database to fully function. If there is no database, you will receive an error message when trying to log on with the Configuration Manager.

There are parameters that you can set when creating an Enterprise Reporter database:

•

You can adjust the initial size of the database or the database log file. If your database will contain a lot of collected data, increase its size. This will improve performance. Use the Database Estimator Tool for further information based on the types of collections being performed.

•

You can choose where to store the database and logs by specifying file paths.

When you allow Enterprise Reporter to create the database, you also have the option to automatically create the following Domain Local security groups:

•

Reporter_Discovery_Admins

•

Reporter_Reporting_Admins

•

Reporter_Reporting_Operators

•

Reporter_Discovery_Nodes

You may optionally enter customized group names during setup. Assign names that reflect the purpose of each group to ensure clarity when group names are displayed in various system administration tools.

These groups provide access to the appropriate tables in the Enterprise Reporter database and are used to allow Windows® authentication on the SQL Server®. For more information, see Security Groups in Enterprise Reporter .


	NOTE: If you enter the names of existing security groups, Enterprise Reporter will use the existing groups instead of creating new ones.


	NOTE: If you choose not to allow Enterprise Reporter to create the necessary groups, the database will be created without the necessary security groups and SQL roles for Enterprise Reporter to function.

A corresponding SQL login and role is created for each group.

•

For example, for the Reporter_Discovery_Admins group, a Reporter_Discovery_Admins login and a Discovery_Admin_Role are created.

•

In this example, the Reporter_Discovery_Admins will then be given the Discovery_Admin_Role. These roles will define the scope of access to Enterprise Reporter. For more information, see Role-Based Security in Enterprise Reporter .

Installing and Configuring Enterprise Reporter

•

Installing Enterprise Reporter

•

Installing the Components

•

Upgrading Enterprise Reporter

•

Licensing Enterprise Reporter

•

Role-Based Security in Enterprise Reporter

•

Managing Your Database Using the Database Wizard

Installing Enterprise Reporter

Once you have determined where you will deploy Enterprise Reporter and have ensured that your computers meet the system requirements, you are ready to install the Enterprise Reporter server and consoles. During the installation process, you can choose whether to install all components on the same computer or on separate computers.


	NOTE: For basic instructions about how to install all of the Enterprise Reporter components onto one server, see the Enterprise Reporter Quick Start Guide.

After the initial installation process is complete, you must create the Enterprise Reporter database. The Enterprise Reporter database can be created and configured automatically during the installation or can be set up later using the Enterprise Reporter Database Wizard utility.

If you have an existing Enterprise Reporter installation and are creating another database with the same version, you can transfer your Enterprise Reporter configuration information (clusters and nodes, discoveries, and reports) using the Database Content Wizard. For more information, see Appendix: Database Content Wizard .

If necessary, you can install additional consoles for other users.

•

Install the Configuration Manager for all Enterprise Reporter administrators. Ensure that each administrator is added to the Reporter_Discovery_Admins group.

•

Install the Report Manager for each user who is required to produce reports. Ensure that for each installation, the user is added to the Reporter_Reporting_Admins group, or the Reporter_Reporting_Operators group as appropriate.

Installing the Components

There are five components that you can install:

•

Enterprise Reporter server

•

When this option is selected, the Database Wizard and the Encryption Key Manager will also automatically be installed.

•

Configuration Manager

•

Report Manager

•

Database Wizard

•

Log Viewer

These components can be installed as needed using a single installer.


	NOTE: Installations must be done locally. You must be logged in with credentials that allow you to install software. NOTE: If you are creating the database when you install your server, as recommended, you must have rights to create database on the SQL Server.

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 .

Next, the Database Wizard displays automatically after you close the Enterprise Reporter server installation window. If the Quest Enterprise Reporter Database Wizard does not open automatically, you may start it manually from the Windows Start menu.

You can either create or connect a new database (see To create a new database during the installation process ) or use an existing database (see To use an existing Enterprise Reporter database during the initial installation ).

To create a new database during the installation process

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.

For more information, see Security Groups in Enterprise Reporter .

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 .

- OR -

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

For help troubleshooting errors, see Database Configuration Issues .

To use an existing Enterprise Reporter database during the initial installation


	CAUTION: If the database is from a previous version of Enterprise Reporter, it will automatically be upgraded. Ensure you back up the database and the encryption key before beginning.

Select Select/Upgrade Existing Database and choose Next.

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.

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, as only databases to which the current credentials have access are shown.

Confirm which 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.

Confirm that you backed up the encryption key using the Encryption Key Manager, and then click Next.

Confirm that you have created a backup of your database by selecting I understand and with to continue, then click Next.

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

Confirm or edit the names for the security groups and click Next.

Review the warning message and click OK to continue.

- OR -

Click Cancel to further modify the Security Group Types or the Security Group Names.

To complete the database upgrade, click Finish.

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

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


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

- OR -

If errors occur during an upgrade, they are detailed at the end of the process. For more information, see Database Configuration Issues .

To launch the Database Content Wizard