Enterprise Reporter 3.5.2

Table 2. Resolved issues
Resolved issue	ID
tblUsedCredentials has extra rows after deleting cluster and node. As a result of this, the Credential Manager is displaying a deleted node when updating credential passwords.	452486
Multi-task Active Directory discovery is collecting data multiple times.	483365
Microsoft Entra ID discovery, with multiple credentials, is unable to authenticate second credential. Workaround: Create another Microsoft Entra credential, using the second credential that you tried to authenticate. When added first, it will authenticate. Go to the original discovery and the second credential will now be authenticated.	483539
Microsoft Entra ID discovery has errors when FIDO2 certificate field is populated.	485385
SQL Server installation is missing VC++ redistributables.	487121
Microsoft Entra ID discovery fails when collecting deleted users MFA authentication methods.	488145
Microsoft Entra ID discoveries should use the default tenant name from the application registration.	489497
Report Schedules save with the local time, but the UTC day of the week.	497919
Unable to deploy nodes with alternate credentials from a different domain.	502922
Active Directory group membership information is not being collected.	504669
Memory leak when running computer discoveries.	505983
Incorrect byte array data in database for extended attribute.	513338
Computer ObjectSID extended attribute is not collected.	522099
When an Active Directory user is deleted their tblDomainUser record is tombstoned, but their tblAccount record is not.	527890
Documentation update required for Microsoft Entra ID discovery minimum permissions. Global Reader, Report Reader and Hybrid Identity Administrator Roles added to the list of required permissions.	542915

Known issues

The following is a list of issues known to exist at the time of release.

Table 3. Known issues
Known issue	ID
Missing group membership data for nested group members with NTFS and Computer discoveries. Workaround: To ensure all nested group membership is collected in a timely manner, it is recommended to create separate Active Directory discoveries for each domain and to avoid using the option Collect nested group members on NTFS and Computer discoveries.	447703
Cloud Discoveries: Cloud Discoveries cannot retrieve information from Azure, when only TLS 1.3 is deployed.	493845
Some of the PDF cross references do not link to their destination pages.	380
Deprecated support for collection of OneDrive attribute 'TenantSyncClientRegistration". No longer available in the One Drive Configuration Settings library report.	235861
When using Multi-Factor Authentication, which uses delegated-only Azure application, there may be inconsistencies with the collection of the Exchange Online mailboxes.	236024
Using discovery credentials that are multi-factor authenticated, may result in some objects not being collected.	236031
To reduce the potential load on ARS Server, we are disabling 'Multiple Tasks' option on the AD scope when collecting ARS attributes.	475475
AD Discovery: If only a read-only domain controller is available for Active Directory discovery, collection will fail.	475471
AD Discovery - Unable to Connect to Database When Primary domain controller (PDC) is shutdown	475473
OneDrive discoveries: Groups are not being properly collected on edits of the group properties/permissions	4009
OneDrive discoveries: Returning unexpected results when "Contribute" permission is being assigned	4221
OneDrive discoveries: Custom Permissions are only returning the "name" of the custom permission and no results on actual set permission	4222
NTFS discoveries: NTFS duplicate files calculation may not be looking at whole computer, only share	7839
PowerShell intermittently returns OneDrive configuration settings incorrectly and updating these attributes is slow on native portal	9902
Microsoft Entra ID discoveries: Group member of itself not being handled properly	11022
Active Directory discoveries: “TTL” Group Member Property: Data may be overwritten and lost with multiple collections from multiple domains using the “Collect nested groups and members” option	18891
Exchange discoveries: Exchange exclusions should be followed in some cases	25018
Active Directory and Exchange discoveries: Duplicate contacts and distribution groups	25023
NAS Configuration UI Option on NTFS and File Storage Analysis Scopes pages causes confusion	27809
Computer discoveries: Windows service(s) are collecting as a failure on discovery when they are access denied.	27907
Exchange discoveries: Error on Exchange 2007 after collecting mailboxes with subfolders and permissions	76507
Exchange Online discoveries: cannot collect mailbox folders permissions with "/" in name	108051
Exchange Online discoveries: cannot collect permissions for some mailbox folders	108052
Computer discovery: Find Computers dialog: incorrect domain hierarchy after select child domain in Available Scopes	125087
Azure discoveries: Azure Licensed User with Service Plans may report incorrect service plans for users if service plan has not be provisioned	128479
Computer discoveries: With some computer discoveries using a shared data location, objects that have been deleted may not be correctly tombstoned in the database	128660
NTFS discovery taking excessive time to complete when metadata selected and encryption enabled on files and folders	170551

The following is a list of issues, including those attributed to third-party products, known to exist at the time of release.

Table 4. Installation known issues
Known issue	ID	Issue ID
Installing the Enterprise Reporter Server using the Change functionality of the installer fails when UAC is enabled WORKAROUND: Disable UAC before using the Change function to install the server	371	215300
Crash upon launch of Configuration Manager console post upgrade installation	423
Database Wizard does not auto-start after installing Enterprise Reporter on PC with enabled UAC	124827

Table 5. Configuration Manager known issues
Known issue	ID	Issue ID
If an ACL references an ACE that is unresolved, that ACE remains unresolved even if the underlying issue is fixed	366	179774
For SQL Server 2000, users who have permissions assigned to database objects will not show properly in the Database Object Permissions report. These permissions are not currently being collected.	367	180536
Registry permissions for a 64-bit key are not being collected when using a 32-bit node	368	180545
A refresh issue sometimes causes a node that was manually removed to remain in the Configuration Manager WORKAROUND: Close the Configuration Manager, and open it again	370	203553
Alternate credentials for a discovery will be ignored if the discovery target is the same machine as the node processing the discovery task. The service account for the node is used to perform the discovery.	376	316195
The dollar sign ($) used for hidden shares does not look correct in Trebuchet font	379	347709
NTFS discovery errors on DFSROOT folders that are actually on the machine but collector says they cannot be found	396	384183
SQL Discovery does not enumerate the SQL Server located on the same system as Enterprise Reporter	397	384273
SQL Discovery does not support SQL Server cluster as a target	413	399407
Microsoft 365 distribution group account type may be updated incorrectly in the database when changing discovery options and collecting mailbox delegates with permissions	444	622477
Exchange throttling warning can occur during large Exchange collections: “The server cannot service this request right now. Try again later.” Create and run smaller discoveries or update Exchange throttling policy. For more information, see Knowledge Base article SOL205286.	446	624722
Multiple errors when using multiple nodes and running ARS collection with AD if nodes do not have prerequisites	449	626447
Special characters in collected data can cause a sorting issue in the SQL Lite database. Data may appear to be deleted when it is not.	2123	212195
When running the ER consoles in 4K resolution, they do not scale properly; 1920x1080 or lower works better. Solution article for DPI settings is available.	164903

Table 6. Report Manager known issues
Known issue	ID	Issue ID
Potential Security Risk Enterprise Reporter sets the PowerShell script execution policy to Unrestricted. This policy is required to allow non-signed scripts to run with reports. The execution policy can be reset if required for security. If set to RemoteSigned or Restricted, some reports will not run.	478387
If you have made changes to parameter values when scheduling a report, you must click Save to preserve your changes. If you navigate away from the parameters, your changes are lost. If you make a change in parameters, you are not warned that you will lose your changes if you do not click Save.	369	180547
Account credentials for a schedule report share will be ignored if the share is on same machine as the Enterprise Reporter server. The service account for the Server is used to access the share and deliver the reports.	376	316195
Unicode characters are not displayed correctly when exported (out of box reports) WORKAROUND: Update report layout to font that supports your character	381	358358
Issues may occur when using two Report Manager consoles on the same machine	403	388313
Custom query reports can allow security breach if SQL Server/database is not properly permissioned	438	613837
NullReferenceException occurs in all reports if they were created with parameters named with reserved words	2124	501242
Boolean parameters are shown incorrectly in the Excel files of reports that are created with the auto-layout wizard	2125	588670
Security Explorer cannot take action against 32 registry key from 64 bit machine	10570
Scheduled reports write to local share using Enterprise Reporter service account instead of account associated with the schedule	11028
Report layout retains parameters that have been deleted and/or renamed	85849
Exporting Summary reports to CSV will not work for sub reports or graphs	120306
The value displayed in the time last collected in Custom Query reports is being reported in GMT and not local time	122626
NTFS: Cannot collect Shares with Cyrillic names in Shares	122634
When running the ER consoles in 4K resolution, they do not scale properly; 1920x1080 or lower works better. Solution article for DPI settings is available.	164903

Table 7. SSRS known issues
Known issue	ID	Issue ID
Special characters not handled correctly in SSRS published reports - query fails to run in RDL	372	223723
The option to display nested groups and their members in reports is not supported in SSRS	373	224951
Scripts are not supported in SSRS reports	374	224953
When a report is published to SSRS, charts are not published and sometimes a blank space will appear in the SSRS report	409	398868
Links in reports are not supported in SSRS. Reports that include links to other reports include File Storage Analysis reports and Remediation Reports.	411	398872
Custom report column headers do not appear on first page in a tabular report when exported to SSRS	426	490510
Some Enterprise Reporter Exchange library reports publish with errors due to fields that cannot be converted. Exchange Server Details report is not supported for publishing.	431	509490
Microsoft Entra and Microsoft 365 reports do not publish correctly to SSRS - errors related to Raw Azure ID and unsupported data types	10819
Advanced calculated field used in reports not supported in SSRS - reports not published	10889
Custom images do not export from Report Manager reports to SSRS	18362	4156245
Parameters used in report layout as binded values are not supported when a report is exported to SSRS.	18363	4156245
Operator EqualswithGroupExpansion is not supported in SSRS. An error will occur when report is published.	85754
The ability to publish reports to Quest Knowledge Portal and the integration with Quest Knowledge Portal has been removed from the product. After upgrade to Enterprise Reporter 3.5, all reports will have to be published to SSRS, as previously published reports to Quest Knowledge Portal will no longer be available and cannot be updated.	ADO -265787

System requirements

Before installing Enterprise Reporter, ensure that your system meets the following minimum hardware and software requirements.

Topics:

•

Hardware requirements

•

New required hardware

•

Supported operating systems

•

Active Roles supported versions

•

IT Security Search supported versions

•

Supported Internet protocols

•

SQL Server supported versions

•

Required software

•

Required services

Hardware requirements

Enterprise Reporter Server

For the Enterprise Reporter Server, we recommend the following minimum hardware.

Table 8. Enterprise Reporter Server Hardware Requirements

Component

Recommended specifications

Memory

•

Minimum: 8 GB RAM

•

Recommended: 16 GB RAM

Processor

•

Intel® or AMD 2 GHz multiprocessor (with at least 2 cores)

•

64-bit processor

Hard disk space

•

10 GB

•

The file share used for the optional Shared Data Location requires space for storage of collected data. Space requirements vary with the amount of data collected.

Configuration Manager and Report Manager

For the Configuration Manager and Report Manager, we recommend the following minimum hardware.

Table 9. Configuration Manager and Report Manager Hardware Requirements

Component

Recommended specifications

Memory

•

Minimum: 16 GB RAM

•

Recommended: 16 GB RAM

Processor

•

Intel® or AMD 2 GHz multiprocessor (with at least 2 cores)

•

64-bit processor

Hard disk space

•

Configuration Manager: 2 GB

•

Report Manager: 20 GB

Enterprise Reporter nodes

For the Enterprise Reporter nodes, we recommend the following minimum hardware. For detailed recommendations for node requirements, see

Table 10. Node Hardware Requirements

Component

Recommended specifications

Memory

•

Minimum: 16 GB RAM

•

Recommended: 16 GB RAM

Processor

•

Intel® or AMD 2 GHz multiprocessor (with at least 2 cores - 4 recommended)

•

64-bit processor

Hard disk space

•

10 GB for installed files plus 10-100 GB extra space for processing collections

Enterprise Reporter SQL Server

For the Enterprise Reporter SQL Server, we recommend the following minimum hardware.

Table 11. SQL Server Hardware Requirements

Component

Recommended specifications

Memory

•

Minimum: 16 GB RAM

•

Recommended: 24 GB RAM

Processor

•

Intel® or AMD 2 GHz multiprocessor (with at least 4cores)

•

64-bit processor

Hard disk space

•

100 GB or more for larger environments


	NOTE: SQL Server performance is needed to support inserting data into the database tables and to support querying that data for reporting purposes. To improve the performance of data collection or reporting, consider enhancing the SQL Server memory and processor.

Database size estimator

The Enterprise Reporter database is the storage location of all data collected for reporting. As such, the amount of hard disk space required is directly related to the amount of data being collected. The Database Size Estimator tool shipped with Enterprise Reporter can help determine how much space will be required.

Larger environments

Larger environments may have additional requirements for memory, processor, and hard disk space. There are many factors that can affect these requirements.

•

The type of collections being performed.

Some discoveries collect many object types and attributes that require multitudes of inserts into multiple database tables; therefore, they require a more robust SQL Server. Other discoveries collect just a few object types that require minimal inserts into a few database tables; therefore, they require a less robust SQL server.

For example, A computer discovery collecting 10,000 computers will be inserting into 20+ database tables. An NTFS discovery collecting 10,000 files and folders will only be inserting into 3 database tables. The inserts are more expensive and the computer discovery will require more SQL server resources.

•

The size of collections being performed.

The size of the database directly relates to the amount of data being collected and being queried from the SQL Server. In other words, the size of the database directly relates to the number of rows in the database. Each discovery type stores different amounts of data. Use the Database Estimator tool for further information based on the types of collections being performed.

•

The location of the SQL Server in relation to the collection targets.

The power of your SQL Server combined with the performance of your network will dictate how fast data can be sent and retrieved from the database. The further away the SQL server is from collection targets and the slower the network speeds, the more a robust SQL Server will help improve performance.

New required hardware

The following hardware is required for Enterprise Reporter 3.2 and higher.

•

Intel® or AMD 2 GHz multiprocessor (with at least 2 cores)

Supported operating systems

The following operating systems are supported for Enterprise Reporter components.


	NOTE: It is not recommended that the server or console be installed on a domain controller.

Table 12. Supported Operating Systems
	ER Server	Consoles	Nodes
Operating Systems	Enterprise Reporter
Windows Server® 2025	X	X	X
Windows Server® 2022	X	X	X
Windows Server® 20H2	X		X
Windows Server® 2004	X		X
Windows Server® 1909	X		X
Windows Server® 1903	X		X
Windows Server® 2019	X	X	X
Windows Server® 1809	X		X
Windows Server® 2016	X	X	X
Windows Server® 1803	X		X
Windows® 11		X
Windows® 10		X

The following operating systems are supported for Enterprise Reporter discovery targets.

Table 13. Supported Operating Systems for Discovery Targets


	Active Directory	Windows Server	File Storage Analysis	SQL Server	Exchange
Supported Operating Systems for Discovery Targets	Licences
Domain Functional Levels
Windows Server® 2025 Functional Level	X
Windows Server® 2016 Functional Level	X
Windows Server® 2012 R2 Functional Level	X
Windows Server® 2012 Functional Level	X
Computers
Windows Server® 2025		X	X
Windows Server® 2022		X	X
Windows Server® 20H2		X	X
Windows Server® 2004		X	X
Windows Server® 1909		X	X
Windows Server® 1903		X	X
Windows Server® 2019 and 1809		X	X
Windows Server® 2016 and 1803		X	X
Windows Server® 2012, 2012 R2, and 2012 Core		X	X
Windows® 11		X	X
Windows® 10		X	X
Windows® 8.1		X	X
Network Attached Storage (NAS) Devices
Dell Fluid File System 6.0		X	X
Dell Fluild File System 5.0		X	X
NetApp® 9.4		X	X
NetApp® 9.3		X	X
NetApp® Filer - Data ONTAP® 8..x - 9.x and above (Cluster mode is supported as of version 8.2)		X	X
EMC Isilon OneFS (Collections require a secure connection to Isilon with a valid certificate.)		X	X
EMC® VNX 7.1.47.5 X (Supported by collecting as a Windows Server)		X	X
EMC® VNX 7.0.35.3 X (Supported by collecting as a Windows Server)		X	X
Pure Storage FlashBlade Purity//FB 4.3.0 * Note: File Storage Analysis partially supported for Pure Storage Flashblade device. Collection of files, folders and shares is supported. Collection of volumes and computer information is not supported.		X	X*
SQL Server Instances
SQL Server® 2022				X
SQL Server® 2019				X
SQL Server® 2017				X
SQL Server® Clusters				X
SQL Server® 2016				X
SQL Server® 2014				X
SQL Server® 2012				X
Exchange Servers
Exchange® 2019					X
Exchange® 2016					X
Exchange® 2013					X

Active Roles supported versions

The following versions of Active Roles are supported as targets of Active Directory discoveries. See the Active Roles web site for the hardware and software requirements for your version of Active Roles.

•

•

•

•

•

IT Security Search supported versions

Enterprise Reporter can be configured to send discovery information to the following versions of IT Security Search. See the IT Security Search web site for the hardware and software requirements for your version of IT Security Search.

•

IT Security Search 11.3 and greater

Supported Internet protocols

Enterprise Reporter can support IPv6 (Internet Protocol version 6) as well as IPv4.

SQL Server supported versions

The following versions of SQL Server® are supported for the Reporter database. See the Microsoft® web site for the hardware and software requirements for your version of SQL Server®:

•

SQL Server® 2022

•

SQL Server® 2019

•

SQL Server® 2017

•

SQL Server® 2016

•

SQL Server® 2014

•

SQL clusters and database mirroring are supported for your deployment, including

•

SQL Server® 2022 Always On

•

SQL Server® 2019 Always On

•

SQL Server® 2016 Always On

•

SQL Server® 2014 Always On

Using SQL Server certificates

SSL encryption of SQL Server connections using certificates

Enterprise Reporter can be configured to work with a SQL Server® instance. To secure communications while working with Enterprise Reporter, data sent over connections to the SQL Server can be encrypted using an SSL certificate.

The steps required to configure this encryption are as follows.

•

Using the Microsoft Management Console (MMC):

•

Install the Certificates snap-in for the SQL Server host computer.

•

Import the certificate to the SQL Server host computer.

•

Using SQL Server Configuration manager:

•

Configure the SQL Server to use the certificate.

•

Configure the SQL Server to force encryption.

•

Restart the SQL Server host computer.

•

Import the certificate to all Enterprise Reporter computers that will communicate with the SQL Server, such as the:

•

Enterprise Reporter server host computer

•

Enterprise Reporter nodes

•

Enterprise Reporter Configuration Manager host computer

•

Enterprise Reporter Report Manager host computer

•

Install Enterprise Reporter on a host computer.

Required software

The following software is required for Enterprise Reporter.

•

Microsoft.NET Framework 4.8

•

Microsoft Excel 2016 or 2019 (required to view reports exported as spreadsheets)

•

Microsoft 365 Excel

•

PowerShell 5.1

Active Roles required software

To collect Active Roles information, the following software is required on the computer where the Enterprise Reporter Configuration Manager is installed and on the computer where the Enterprise Reporter node is installed:

•

ADSI Provider (the version must match the Active Roles version)

For more information and installation instructions, see the Active Roles Quick Start Guide.

The following additional considerations are required:

•

There must be a trust between the Enterprise Reporter domain and the Active Roles domain.

•

The credentials used for the Active Roles discovery must have access to the Active Roles domain.

Exchange required software

To collect Exchange information, the following additional considerations are required:

•

Ensure the Windows Remote Management (WinRM) service is running.

To collect Exchange mailbox folders, the following additional considerations are required:

•

Impersonation needs to be configured on the Exchange organization. Refer to your Exchange Server documentation or use the following method to set up role assignments.

•

PowerShell can be used to add an assignment

New-ManagementRoleAssignment –Name:impersonationAssignmentAdministrator
–Role:ApplicationImpersonation –User:Administrator

•

Alternatively, you can create an administrator role with ApplicationImpersonation role assigned to it and add the required account as a member (or assign ApplicationImpersonation role to an existing administrator role)

Exchange Online required software

To collect Exchange Online information, the following additional considerations are required:

•

Ensure the Windows Remote Management (WinRM) service is running.

Multi-Factor Authentication Cloud Discovery Credential Limitations

Cloud discoveries (Microsoft Entra ID, Azure Resources, Exchange Online, Teams, and SharePoint Online) support both MFA (Multi-Factor Authentication) enabled and disabled credentials. However, using Multi-Factor Authentication enabled credentials on cloud discoveries can result in an incomplete collection that omits one or more of the following objects and attributes.See the following table for details.

Table 14. Cloud discoveries that may be excluded due to Multi-Factor Authentication
Type	Omitted objects and attributes
Microsoft Entra ID	Risky users and Microsoft Entra extended attributes
Azure Resources	Fails with no data returned
Microsoft Teams	No files and folders (drives)
SharePoint Online	Fails with no data returned
One Drive	Fails with no data returned