Chat now with support
Chat with Support

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

Upgrading Enterprise Reporter

The following sections outline how to upgrade Enterprise Reporter.

•
Preparing to Upgrade Enterprise Reporter
•
Upgrading Enterprise Reporter Components
•
Upgrading Enterprise Reporter Nodes
•
Upgrading Manually-Configured Enterprise Reporter Nodes

Preparing to Upgrade Enterprise Reporter

There are four components that you can upgrade: the Enterprise Reporter server, the Configuration Manager, the Report Manager, and the Database Wizard. All components of Enterprise Reporter must be upgraded before it can function correctly and can be upgraded using a single installer.

Before you upgrade the components, you must shut down all Enterprise Reporter components. While the upgrade is in progress, data collection will stop and no reports are run. Be sure to plan the timing of the upgrade accordingly and inform your users that they will be able to resume reporting once the upgrade is complete.

The system, permissions, and port requirements for an upgrade are the same as those for installing Enterprise Reporter. For more information, see Before You Install Enterprise Reporter

* 
CAUTION: It is strongly recommended that you back up your database and the encryption key. You can restore the backup if there are issues with the upgrade.
CAUTION: If upgrading from Enterprise Reporter 3.2, it is strongly recommended that you have your encryption key backup file and user-supplied password available prior to upgrading. The encryption key and password are required to decrypt credentials in the Enterprise Reporter Credential Manager during the upgrade. If the encryption key backup file and user-supplied password are unavailable, all passwords must be re-entered in the Enterprise Reporter Credential manager.
* 
NOTE: During an upgrade, all Exchange Online data that was stored before the upgrade is removed.

In summary, to upgrade Enterprise Reporter, you must:

•
Shut down the Enterprise Reporter server, the Configuration Manager, the Report Manager, and the Database Wizard.
•
Disable clusters to stop discoveries from being sent to the nodes.
•
Cancel any jobs running on the nodes to stop data from writing to the Enterprise Reporter database.
•
Cancel any report jobs running or scheduled to prevent Report Manager from accessing the database.
•
Create a backup of the database.
* 
CAUTION: It is strongly recommended that you back up your database and the encryption key. You can restore the backup if there are issues with the upgrade.
•
Note the port number being used by the Enterprise Reporter server.
•
Upgrade the Enterprise Reporter components.
•
Upgrade the nodes.
•
If there are any manually configured nodes, upgrade them manually.
* 
NOTE: The person performing the upgrade must have permissions to update group membership. A new security role for Reporter_Discovery_Nodes will be created and all node service accounts will be added as members of this group. For nodes to be installed and upgraded the service account must be a member of the group Reporter_Discovery_Nodes.
•
Enable any disabled clusters to resume discoveries.

Upgrading Enterprise Reporter Components

There are four components that you can upgrade: the Enterprise Reporter server, the Configuration Manager, the Report Manager, and the Database Wizard. These can be upgraded using a single installer. Prior to upgrading the components, all Enterprise Reporter components must be shut down.

* 
NOTE: Upgrades must be done locally. You must be logged in with credentials that allow you to install software.
* 
NOTE: When you are upgrading the Enterprise Reporter database, you must have db_owner rights to modify the database on the SQL Server. For more information, see To create a new database during the installation process .
To prepare to upgrade all Enterprise Reporter components
1
Open Configuration Manager.
2
Under Discovery Management, click Manage Discoveries and stop any running Discoveries.
3
Under Discovery Management, click Manage Discovery Clusters.
4
Disable any Clusters.
The Nodes associated with the Clusters will also be disabled when you disable the Clusters.
5
Select the Discovery Nodes tab, then select all nodes and click Stop Node and wait for the nodes to stop.
6
Open Report Manager and confirm that there are no scheduled reports running.
If any reports are running, either abort them or wait until they complete.
7
Close the Configuration Manager and the Report Manager.
8
Shut down the Enterprise Reporter server.
To upgrade all Enterprise Reporter components except Nodes
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
Accept the license agreement and click Next.
6
To upgrade all components, click Next.
- OR -
To upgrade select components, click the drive icon for each component, and select the desired option, then click Next.
Clicking Reset restores the default setting of installing all components.
7
If you are upgrading the Enterprise Reporter server, specify the credentials and the port number 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.
8
Click Install.
9
Click Close and the Database Wizard will start.
For the next steps, see To upgrade an Enterprise Reporter database .
The Enterprise Reporter database must be the same version as the Enterprise Reporter server before data collection and reporting can resume. If you decide you do not want to upgrade the database right now, you can use the Database Wizard at any time. For more information, see Upgrading a Database .
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.
Enterprise Reporter connects to the SQL Server using Windows authentication by default. If you want to connect using SQL credentials, enter them.
6
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.
7
Confirm that you have created a backup of your database by selecting I understand and wish to continue and click Next.
8
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 .
9
If required, enter or browse to the domain of the Enterprise Reporter server service account.
10
Confirm or edit the names for the security groups and click Next.
11
Review the warning message and click OK to continue.
- OR -
Click Cancel to further modify the Security Group Types or the Security Group Names.
12
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.
13
When the upgrade completes successfully, click OK to open the Encryption Key manager.
14
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 .

Upgrading Enterprise Reporter Nodes

Enterprise Reporter nodes must be the same version as the Enterprise Reporter server. Nodes can be upgraded in groups or individually.

* 
NOTE: Nodes that were configured manually must have credentials updated manually before they can be upgraded. For more information, see Upgrading Manually-Configured Enterprise Reporter Nodes .
To upgrade Enterprise Reporter nodes
1
Open the Configuration Manager.
2
To display the nodes, select Manage Discovery Clusters and click the Discovery Nodes tab.
All nodes with versions that are out of sync with the Enterprise Reporter server will display a status of Incompatible Version.
* 
NOTE: Nodes may only be upgraded if the node service account is a member of the group Reporter_Discovery_Nodes. The upgrade process will attempt to add all node service accounts to this group. If this attempt is unsuccessful, the account must be added manually for a successful node upgrade.
3
If nodes are stopped, click Restart node.
4
Select the nodes you want to upgrade and click the Upgrade Node icon.
5
Optionally, select Specify an alternate credential for Node service deployment, then select the account.
* 
NOTE: This account must have permission to copy files in the Admin$ share folder and to install and run services.
6
Click Yes.
The status of the node will change to Upgrading. Once the Nodes have been updated, their statuses will change to Enabled and any Cluster associated with the Nodes will also become enabled.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating