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

Upgrading Manually-Configured Enterprise Reporter Nodes

Nodes that were configured manually must have credentials updated manually before they can be upgraded.

2
To display the nodes, select Manage Discovery Clusters and click the Discovery Nodes tab.

 

6

 

Upgrading Enterprise Reporter in Kerberos only environment

This upgrade process is for environments that were using NTLM authentication when Enterprise Reporter was initially installed and have switched to Kerberos only authentication. For example, you have Enterprise Reporter 3.5.1 currently installed, NTLM has been disabled and only Kerberos is available, and you plan to upgrade to Enterprise Reporter 3.5.2.x.

Upgrade Requirements

5
Click View License Agreement and scroll to review the entire license agreement.
6
Select I accept these terms, click OK to close the agreement, and click Next to continue the installation.
NOTE:  
Clicking Reset restores the default setting of installing all components.
If you have any nodes running that cannot be shut down you will get a warning message to disable and stop the Nodes. Select the I understand and wish to continue check box. The nodes will be manually updated locally or removed and re-installed after the upgrade.
10
Click Install.
1
Click the Start menu and select All Programs | Quest | Enterprise Reporter | Database Wizard and click Next.
2
Choose Select/Upgrade Existing Database and click Next.
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.
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.
8
Select to enable The encryption key will need to be backed up, using the Encryption Key Manager and The database cannot be used until the upgrade completes successfully and click Next.
11
Click Finish to start the upgrade.
13
Click OK and close the Database Wizard.
1
2
Click the Discovery Nodes tab.
One node may display a Status of Incompatible Version and the other as Faulted. The node on the same system as Enterprise Reporter (upgraded) is displaying a Status of Incompatible Version, because Windows does not restrict WCF communication with the node on the same system and the UPN or SPN is not needed in this case.
3
Right click the node that displays the status of Incompatible Version and select Node Properties.
The Applying changes to Node dialog opens stating that the change has been successfully made to the node. Click on Close.
4
Click on the Incompatible Version node and in the Discovery Nodes menu bar select Upgrade Node (or right click and select Upgrade Node).
5
A dialog opens, click Yes if you want to proceed.
When the upgrade is completed the node will display Enabled and the version will be the version of the upgrade. The node is now available and discoveries can be run using this node.

Nodes in the failed or faulted state can only be updated by removing the node from the Enterprise Reporter database and then reinstalling. Nodes can be in this state:

2
Local nodes with a status of Incompatible can be upgraded by selecting it, and clicking Upgrade Node.
Nodes that start and then fail with a status of Starting Failed will need to be removed.
4
Click Remove Node on the node on the remote system.
NOTE:  
6
Click Add Node, select the system from which the failed node was removed.
7
Select the Node Credentials.
10
Nodes installed on the remote systems have a status of Faulted. These nodes will not bei able to communicate with Enterprise Reporter server service over Kerberos.
Local nodes (installed on the same system as Enterprise Reporter) will have a status of Incompatible Version. Select these nodes and click on Upgrade Node. Once upgrade the nodes will have a status of Enabled.
6
Right click the Enabled node, select Node Properties, and enter the UPN or SPN.
A Node Change pop-up opens to indicate that a change has been made to the node.
Nodes with the status of Faulted, due to the enabling of Kerberos, need to be removed.
10
Click Add Node, select the system from which the faulted node was just removed.
14
The newly add node will have a status of Enabled once the upgrade is complete.

Use the following information to update nodes in environments where Kerberos authentication has been implemented, but Enterprise Reporter has not been updated for Kerberos support.

Even after upgrading Enterprise Reporter with Kerberos support, the nodes will indicate as Faulted. The only exception to this will be the node (if configured) installed on the same system as Enterprise Reporter. This node can be upgraded in the typical manner.

To upgrade the other nodes, you need to run the node installation on each of the systems that have faulted. The reason is that since Kerberos has been implemented, the installed node software cannot communicate with the Enterprise Reporter Server Service located on the system where Enterprise Reporter is installed.

To resolve this, the Update-ERNode command includes a UpnSpn parameter to allow the inclusion of the User or Service Principal Name needed for Kerberos communications. For example, the following command upgrades the specified node in specified cluster using a User or Service Principal Name for node installation in a Kerberos only environment.

Update-ERNode "First Cluster" "AMERGEN01" administrator@amer.sitraka.com

1
Run the following command to list all the nodes in the variable $Nodes:
$Nodes = Get-ERNode -Cluster "First Cluster" $Nodes
Version : 3.5.1.6
Computer :
AMERGEN01.amer.sitraka.com
ServiceCredentialId : 08814be4-7b6d-41b2-8f66-998ebcd671ee
SqlCredentialId : 00000000-0000-0000-0000-000000000000
Status : Enabled
MaxJobSlots : 0
ClusterId : 94356c24-ab3f-4ab8-a407-65de08bfe4dc
3
Run the Get-ERNode -Cluster "First Cluster" command to see the process of the upgrade of the nodes.

See the appendix in the Enterprise Reporter Configuration Manager User Guide for details on using the Enterprise Reporter PowerShell commands.

After Upgrading Enterprise Reporter

After upgrading Enterprise Reporter, open the Configuration Manager to see an overview of What’s New and any new discovery configuration features that may need to be updated manually. Validate your current cluster, node, and discovery configurations.

Licensing Enterprise Reporter

You need either a trial or full license to use Enterprise Reporter. You must have a valid license to use the Configuration Manager; no license is required for the Report Manager. If you have questions about your license, contact your sales representative.

Topics:  

 

Enterprise Reporter for Windows Servers

Enterprise Reporter for Active Directory

Enterprise Reporter for SQL Server

Enterprise Reporter for File Storage Analysis

Enterprise Reporter for Exchange

Enterprise Reporter for Microsoft 365

Enterprise Reporter Suite

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating