Chat now with support
Chat with Support

Metalogix ControlPoint 8.5 - Release Notes

Metalogix® ControlPoint 8.5

Release Notes

November 2020

These release notes provide information about the latest Metalogix® ControlPoint release.

·New Features

·Resolved Issues

·Known Issues

·System Requirements

·Product Licensing

·Third Party Contributions

·About Us

New Features

Version 8.5 of Metalogix ControlPoint introduces the following features:

·The installation of the the ControlPoint Configuration Site into an existing Web application, informally referred to as "Native" is now referred to as a "Non-Standard."

·For ControlPoint for Office 365 (ControlPoint Online):

§During an installation/upgrade you can specify:

§a host header to use  for the ControlPoint Online Configuration Site

§an O365 email account as the ControlPoint "from" account

§Global Administrators and SharePoint Administrator in the Office 365 tenant can view the entire SharePoint Hierarchy and perform operations on all site collections via ControlPoint Online.

·For Compliance Functionality:

§ControlPoint 8.5 works best with Metalogix Sensitive Content Manager version 2.1, so it is recommended that both be installed/upgraded together for improved performance.

§A new action, Manage Scanned Files, allows you to review and act on individual items/files for which Sensitive Content Search Terms have been found.

§A Terms Detected column can be added to SharePoint lists that have been scanned for compliance.

§Scanned Files analyses have been enhanced, allowing you to include only the most recent instances of scanned files.  For faster processing an additional parameter, Security trimming using cached permissions, uses permissions collected since the last run of Discovery instead of the real-time permissions of users who performed scans.

Resolved Issues

The following is a list of issues addressed in this release.


Work Item

Case No.

The issue "ControlPoint is not providing full reports" has been resolved.



The issue "ControlPoint Alerts not displaying name of Site Creator" has been resolved.



Known Issues

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

Installation and Configuration


Issue ID

·If ControlPoint is uninstalled using an account that does not have sysadmin privileges, any existing ControlPoint Policies cannot be removed.

Workaround if you want to delete existing ControlPoint Policies:

§Before uninstalling ControlPoint, delete the policies using Manage ControlPoint Policies.


§Uninstall ControlPoint using an account that has sysadmin privileges.


When a manual (scripted) installation is performed, the Launch ControlPoint shortcut is not created on the server's desktop or Start menu.

Workaround: Launch ControlPoint by entering the url in a browser.


After a manual (scripted) uninstallation is performed, several files remain in the Metalogix/ControlPoint/ControlPoint Features folder.  You can delete these files manually.


Login and Security Trimming


Issue ID

·When Firefox or Chrome is used as the browser, the Sign out option refreshes the page but does not sign the user out.

Workaround:  This is not an issue with Internet Explorer.


·If a ControlPoint user has permissions to SharePoint sites only through a web application Full Control permission policy, and this permission was granted after the initial run of ControlPoint Discovery, site collections and sites within that web application will not display in Search Hierarchy results if cached data is used.

Workaround:  Before running Discovery, give the user any level of permissions to any site within each site collection in the web application.  Only then will Discovery be able to “discover” that the user has Site Collection Admin rights via the web application policy.  After the next Discovery run has finished, you can remove the site-level permissions.


Business Administrators Functionality


Issue ID

·Members of the Business Administrators group can run live permissions reports even when the ControlPoint Setting "BAPreventRealTime" is set to True.


·For SharePoint 2010 Claims-enabled web applications, members of the Business Administrators group cannot access sites to which they have permissions if those permissions are granted via an Active Directory Group.

Workaround:  Grant the user permissions to the site(s) directly.


User Interface


Issue ID

·The “Clone Work Area in the new browser window” does not work for dashboard links due to the “Selection” tab being empty.


·For a SharePoint 2013 farm:  When Chrome is used as the browser, the SharePoint Hierarchy may not be expandable.

Workaround:  Refresh the browser or invoke a ControlPoint operation from the left navigation pane (to trigger an event). Note that it is not necessary to actually run the operation.


·For a SharePoint 2013 farm:  The first time ControlPoint is invoked after an upgrade, the dashboard may not display in the main page.

Workaround:  Refresh your browser.


·When running ControlPoint on a SharePoint 2013 farm using Internet Explorer 8, Charts for the Top Site Collections By Size and Sites Created In the Last 30 Days are not displayed correctly in the Dashboard.

This is not an issue with other versions of Internet Explorer or with Chrome or Firefox.


·When using Internet Explorer build 11.0.9600.18617, report results do not fill the entire results section.

Workaround:  Use a different build of Internet Explorer or a different browser




Issue ID

Selection scope is lost when you click on the user drill down link on a Site Permissions report on a remote farm.


ControlPoint Policies


Issue ID

·When using IE with Compatibility View turned off, when the policy rule ‘Control Document/Item deletion’ is selected, the ‘Allow Attachments to be Deleted’ checkbox is disabled. (Work Item )

Workaround:  Turn Compatibility View on or use a different browser.


·The "ControlPoint File Upload Size" policy does not work properly for SharePoint 2016 and 2019.[QA


Permissions Operations


Issue ID

·When a Set SharePoint Group Permissions action is run with the parameter “Propagate to all items with unique permissions” checked, the permissions level is not propagated to the items.


·The Manage Permissions Inheritance action fails to restore inheritance at the list item level.


Operations Involving Workflows


Issue ID

·Reusable workflows are not being migrated during the Duplicate Workflow Definition operation.


·In a SharePoint 2010 Non-Standarde Edition installation, a cross-farm Copy/Move List operation fails with access denied error when including workflows.


Operations Involving Managed Metadata


Issue ID

·In a SharePoint 2010 environment, when a ControlPoint Managed Metadata operation (such as Create Managed Metadata or Set Metadata Value) is run. Managed Metadata terms that were selected in the Parameters section may not be validated, and the message There was an error processing the request may display.

Workaround:  Make sure that the SharePoint August 2013 Cumulative Update has been applied.


Site Provisioning


Issue ID

·When running SQL Server 2012, you may not be able to create a custom template for a site collection using a 2013 Experience.

Workaround:  Install Microsoft SQL Server 2012 SP1 Reporting Services Add-in for Microsoft SharePoint, which can be found at


·Site Provisioning errors when using an https url.  


Compliance Functionality (Sensitive Content Manager)


Issue ID

·If the Terms Detected column is populated in SharePoint for a list item with attachments and the item is rescanned, the Detailed Classification may show a higher severity level for the item than it did in the original scan, even if the content of the item itself did not change.  

This would occur because Sensitive Content Manager evaluates the search terms in the Terms Detected column—which may have been detected for one of the attachments—as part of the analysis.


·After a rule is applied to a scan, the page is refreshed and the scan details are not visible.


·2013 Standard Edition:  When Chrome is used as the browser and a member of the Compliance Administrators group attempts to initiate a Compliance action, a pop-up message displays that the user must be a member of the Compliance Administrators group.

Workaround:  Either try logging out and logging back in or use a different browser.


·The “Detailed Actions Taken Analysis” Search function does not filter results properly.


·“Unable to Classify” files display as “Undetectable” in the exported file.


·The ControlPoint Policy “Scan item for sensitive data when content is added” fails when "Require documents to be checked out " is enabled.


·If a file is rescanned after its name has changed and Scanned Files by Scope is run using real-time data, the file displays twice in report results, with both the old and new name.


ControlPoint Sentinel for Anomalous Activity


Issue ID

·The ControlPoint Anomalous Activity Detection timer job is not created in Central Administration upon an upgrade. (Work Item )


§To add the timer job, re-run the ControlPoint Installer as a Repair.


§Have Anomalous Activity detection performed as part of the ControlPoint Scheduled Job Review.  Refer to the topic “Preparing Your Environment for Using ControlPoint Sentinel” in the ControlPoint User Guide for details.




Issue ID

·When a report is run on real-time data, only the first page of results that are visible in the UI is exported.  

Workaround:  If you schedule the report, full results will be included in the output file.


·If the ControlPoint Setting “Display URL Instead of Site Name in SharePoint Hierarchy (SHOWURLASTITLE)” is enabled, the site collection/site name is also replaced by the URL in reports using real-time (non-cached) data.


·When running a Duplicate Files report, subsites might not be considered in the results.


·SP2013: The site link in the site properties report does not correspond to the correct site.


·SP2010/2013 Standard and Non-Standard: When running a “Site Activity Analysis” with default parameters, i.e. Farm Scope, the report only displays sites with activity. Existing sites without activity are not included.


·If a ControlPoint Task Audit is run, the expand/collapse option for the report will not work correctly. The report will be displayed in expanded format, no matter if that option was checked or not.



·Change Log analyses return a maximum of 2000 results.  

Workaround:   Run the analysis on smaller scopes


·When a Most/Least Activity report is scheduled with one or more (but not all) Include Report: options selected, and the Output Type is SharePoint List, a separate list is created for each “Include Report” option.  Empty lists are created for options that were not selected.  


·Trend analysis for Activity returns results only when Discovery is run on one or more targeted site collections.


·All users listed as "Inactive" in a 2010 ADFS Environment. ControlPoint’s “Inactive Users” report essentially compares results of two other reports. The total users list generated by a Site Permissions report is run against the total list of users with activity, as determined by Activity by User.  An environment with only 2010 ADFS users is erroneously reporting all users inactive.


·After drilling down in the results of a Site Permissions report that was run on more than one farm in a multi-farm environment, the selection scope is lost.


·The Site Collection Properties lists only site-level features, and lists no features when the “Limit reports to site collections with the following features” filter is applied.


ControlPoint for Office 365 (ControlPoint Online)


Issue ID

·If a Permissions analysis is run with the Show External Users Only option selected, both internal and external users are included in analysis results.

NOTE:  This issue generally occurs only when the logged in user is not an Office 365 Global Administrator.


·In SharePoint Hierarchy Report results, subsites of a site in one site collection may show the results of other sites on a different site collections.


·If the server on which ControlPoint is installed is rebooted, results of analyses (including the ControlPoint Task Audit) that are run in real time fail to render in the ControlPoint application interface.  Instead, the message An unanticipated error has occurred displays.

Workaround:  On the server on which ControlPoint is installed, open IIS Manager and recycle the MetalogixOnline Application Pool.


·Users specified in the ControlPoint Setting ExcludedUsersAudit are not actually being excluded from the Audit Log analysis.


·When you open an item in the ControlPoint Configuration Setting list for editing, a blank Title field displays and will not allow you to save your changes until it is populated.

Workaround:  Copy the Parameter Name to Title field before saving or use the ControlPoint Settings page in the application interface.


·Sites migrated from BPOS (pre Office365) are not visible in ControlPoint.


Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
RSS Feed
Contact Us
Licensing Assistance
Technical Support
View All
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating