The following is a list of enhancements that are implemented in Enterprise Reporter 3.5.2.
Multi-task Active Directory discovery is collecting data multiple times. |
|
Microsoft Entra ID discovery has errors when FIDO2 certificate field is populated. |
|
Microsoft Entra ID discovery fails when collecting deleted users MFA authentication methods. |
|
Microsoft Entra ID discoveries should use the default tenant name from the application registration. |
|
Report Schedules save with the local time, but the UTC day of the week. |
|
Unable to deploy nodes with alternate credentials from a different domain. |
|
Active Directory group membership information is not being collected. |
|
Incorrect byte array data in database for extended attribute. |
|
Missing group membership data for nested group members with NTFS and Computer discoveries. |
|
Some of the PDF cross references do not link to their destination pages. |
|
AD Discovery - Unable to Connect to Database When Primary domain controller (PDC) is shutdown |
|
OneDrive discoveries: Returning unexpected results when "Contribute" permission is being assigned |
|
NTFS discoveries: NTFS duplicate files calculation may not be looking at whole computer, only share |
|
Microsoft Entra ID discoveries: Group member of itself not being handled properly |
|
Exchange discoveries: Exchange exclusions should be followed in some cases |
|
Active Directory and Exchange discoveries: Duplicate contacts and distribution groups |
|
NAS Configuration UI Option on NTFS and File Storage Analysis Scopes pages causes confusion |
|
Exchange Online discoveries: cannot collect mailbox folders permissions with "/" in name |
|
Exchange Online discoveries: cannot collect permissions for some mailbox folders |
|
WORKAROUND: Disable UAC before using the Change function to install the server |
||
Crash upon launch of Configuration Manager console post upgrade installation |
||
Database Wizard does not auto-start after installing Enterprise Reporter on PC with enabled UAC |
Registry permissions for a 64-bit key are not being collected when using a 32-bit node |
||
WORKAROUND: Close the Configuration Manager, and open it again |
||
The dollar sign ($) used for hidden shares does not look correct in Trebuchet font |
||
SQL Discovery does not enumerate the SQL Server located on the same system as Enterprise Reporter |
||
SQL Discovery does not support SQL Server cluster as a target |
||
Unicode characters are not displayed correctly when exported (out of box reports) WORKAROUND: Update report layout to font that supports your character |
||
Issues may occur when using two Report Manager consoles on the same machine |
||
Custom query reports can allow security breach if SQL Server/database is not properly permissioned |
||
Security Explorer cannot take action against 32 registry key from 64 bit machine |
||
Report layout retains parameters that have been deleted and/or renamed |
||
Exporting Summary reports to CSV will not work for sub reports or graphs |
||
The value displayed in the time last collected in Custom Query reports is being reported in GMT and not local time |
||
Special characters not handled correctly in SSRS published reports - query fails to run in RDL |
||
The option to display nested groups and their members in reports is not supported in SSRS |
||
Custom report column headers do not appear on first page in a tabular report when exported to SSRS |
||
Advanced calculated field used in reports not supported in SSRS - reports not published |
||
Custom images do not export from Report Manager reports to SSRS |
||
Operator EqualswithGroupExpansion is not supported in SSRS. An error will occur when report is published. |
||
For the Enterprise Reporter Server, we recommend the following minimum hardware.
| |||
|
For the Configuration Manager and Report Manager, we recommend the following minimum hardware.
| |||
| |||
For the Enterprise Reporter SQL Server, we recommend the following minimum hardware.
| |||
The following hardware is required for Enterprise Reporter 3.2 and higher.
• |
Intel® or AMD 2 GHz multiprocessor (with at least 2 cores) |
The following operating systems are supported for Enterprise Reporter components.
Windows Server® 20H2 |
|||
Windows Server® 2004 |
|||
Windows Server® 1909 |
|||
Windows Server® 1903 |
|||
Windows Server® 2019 |
|||
Windows Server® 1809 |
|||
Windows Server® 2016 |
|||
Windows Server® 1803 |
|||
Windows® 11 |
|||
Windows® 10 |
The following operating systems are supported for Enterprise Reporter discovery targets.
Windows Server® 2025 Functional Level |
|||||
Windows Server® 2016 Functional Level |
|||||
Windows Server® 2012 R2 Functional Level |
|||||
Windows Server® 2012 Functional Level |
|||||
Windows Server® 2025 |
|||||
Windows Server® 2022 |
|||||
Windows Server® 20H2 |
|||||
Windows Server® 2004 |
|||||
Windows Server® 1909 |
|||||
Windows Server® 1903 |
|||||
Windows Server® 2019 and 1809 |
|||||
Windows Server® 2016 and 1803 |
|||||
Windows Server® 2012, 2012 R2, and 2012 Core |
|||||
Windows® 11 |
|||||
Windows® 10 |
|||||
Windows® 8.1 |
|||||
NetApp® 9.4 |
|||||
NetApp® 9.3 |
|||||
EMC® VNX 7.1.47.5 X (Supported by collecting as a Windows Server) |
|||||
EMC® VNX 7.0.35.3 X (Supported by collecting as a Windows Server) |
|||||
SQL Server® 2022 |
|||||
SQL Server® 2019 |
|||||
SQL Server® 2017 |
|||||
SQL Server® Clusters |
|||||
SQL Server® 2016 |
|||||
SQL Server® 2014 |
|||||
SQL Server® 2012 |
|||||
Exchange® 2019 |
|||||
Exchange® 2016 |
|||||
Exchange® 2013 |
Enterprise Reporter can support IPv6 (Internet Protocol version 6) as well as IPv4.
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 Server® 2022 Always On |
• |
SQL Server® 2019 Always On |
• |
SQL Server® 2016 Always On |
• |
SQL Server® 2014 Always On |
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.
The following software is required for Enterprise Reporter.
For more information and installation instructions, see the Active Roles Quick Start Guide.
The following additional considerations are required:
To collect Exchange information, the following additional considerations are required:
To collect Exchange mailbox folders, the following additional considerations are required:
To collect Exchange Online information, the following additional considerations are required:
The following services are required on the Enterprise Reporter server and nodes.
The following services must be enabled on discovery targets for collections.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center