Release Notes
October 2024
These release notes provide information about the Quest Sensitive Content Manager 2.2.5 release. Quest Sensitive Content Manager uses a micro-service architecture and can be integrated with Microsoft SharePoint, Quest ControlPoint and Quest Essentials.
·About Quest Sensitive Content Manager 2.2.5
Quest Sensitive Content Manager (SCM) provides a reliable, accurate and flexible solution for detecting sensitive information within enterprise content management systems. SCM ships with pre-built analysis profiles such as General Data Protection Regulation (GDPR), Personally Identifiable Information (PII), Protected Health Information (PHI), Payment Card Information (PCI) in addition to the detection capabilities with customizable analysis profiles.
This version of Quest Sensitive Content Manager introduces the following features and improvements:
General
·Metalogix Sensitive Content Manager has been rebranded to Quest Sensitive Content Manager.
·Supports TLS 1.3 which is faster and more secure than TLS 1.2. For more information about SQL server setup for TLS 1.3, contact Quest Technical Support.
The following is a list of issues, including those issues attributed to third-party products, known to exist at the time of release.
Description |
Reference No. |
---|---|
The SCM Document Routing Service (DRS) fails with the message: Could not find file in FileStorage when you submit a zip file which contains a duplicate filename within its folder hierarchy and a DRS restart occurs while processing the zip file contents. |
162998 |
installer.log file is not created when the installer is launched automatically after a restart due to a .NET framework installation. |
181442 |
Exception log messages distort the Logs screen after expanding and then refreshing the page. |
171761 |
Special characters in destination or file storage folder name will cause the installation to fail. |
178114 |
License re-validation message for an expired license is not displayed. |
178733 |
Exception logs are not shown completely when expanded for long messages in Internet Explorer. |
174158 |
Rollback is not triggered when hostname on the IIS Information screen has special characters in it. |
182299 |
IIS Firewall rules are not regenerated when you run the installer to repair or upgrade. |
182391 |
Rabbit configuration details (PEM file, Rabbit certificate, etc.) are not regenerated when repairing SCM. Workaround: uninstall and reinstall SCM. |
189372 |
A non local-admin service account user is not able to clear registry during installation but logs a confusing message in the log file: License details collected from the installer could not be committed to the service connection point. Workaround: Assign local admin rights to the service account. |
193359 |
Restarting the VM or ending the installer process in the middle of an installation causes failures when attempting to re-install. Workaround: Run the Microsoft install and uninstall tool to repair the installation. |
201042 |
Some logs entries appear with incorrect TimeStamp while the system gradually upgrades the different services from 2.0 to 2.1 |
208702 |
SCM 2.0 - The Administration Center UI prompts for user credentials 3 times on Windows 2016 and IE v11.3808 Workaround: Use Chrome or Edge browser, or add the site to the intranet zone . |
209320 |
SCM Installer fails if IIS Express 8 is installed on the target server. Workaround: Uninstall IIS Express and try again. |
209737 |
Administration Center UI in both Chrome and Firefox shows incorrect time if auto adjust for DST is disabled. |
209815 |
Some characters that can be considered as delimiters or separators affect keyword detection and may result in false positive search term detections in Excel and CSV files. |
238599 |
A Search term with a semicolon in its title is incorrectly separated with a space on the Report Details screen. |
240879 |
When new SCM node is installed, the services Log Level in appsettings.json file is reset to the default value of Warning regardless of the Log Level setting in the main node. |
243102 |
If old versions of RabbitMQ and Erlang are present on the system then upgrading to version 2.2.1 may cause the RabbitMQ folder to be created incorrectly under the %APPDATA% path. Workaround: Ensure the old versions of RabbitMQ and Erlang are uninstalled completely or relocate the RabbitMQ data folder via the support tool scripts before attempting the installation again. |
303910 |
Search terms are not detected in Microsoft Word documents with headers formatted with multiple columns |
313628 |
The message The RabbitMQ Server path does not exist in Program Files appears if you attempt to install SCM on a system where Erlang 24 is present but not RabbitMQ. Workaround: Uninstall Erlang 24 before attempting to install SCM again. |
315380 |
On a Windows Server 2016 environment the upgrade from SCM 2.2 to 2.2.1 may fail on deploying Analysis Service when a user initially installs SCM 2.2 and a different user upgrades to SCM 2.2.1 or later. Workaround: Either install with the same original user or remove SCM and re-install cleanly again. |
316963 |
Existing (SCM 2.2 and 2.2.1) report overview analyzed and unsuccessful counts will temporarily show incorrectly when SCM is upgraded to 2.2.2. New scans will show the counts correctly. |
324785 |
A recently added user to the Administration Center security group will get an unauthorized error message if the user attempts to logon immediately after being added to the group Workaround: Either recycle the Admin service application pool or Restart IIS. |
352267 |
Any 8- or 11-character words with a valid country code in the 5th and 6th characters are incorrectly detected as valid Swift Codes. |
404774 |
A service-only server cannot be repaired if the primary SCM server has been configured to run its services using the Local System account and the service-only server account does not have proper permissions on the SCP. |
423164 |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 利用規約 プライバシー Cookie Preference Center