Chat now with support
Chat with Support

Metalogix ControlPoint 8.5 - O365 Administration Guide

Preface The ControlPoint Configuration Site Managing Your Farm List Setting Up ControlPoint Services Using Discovery to Collect Information for the ControlPoint Database Cache Updating Full Discovery and Scheduler Windows Jobs Using Sensitive Content Manager Services Setting Sensitive Content Manager End Points and Managing Scanning Preferences Managing Your ControlPoint License Registering and Re-registering the ControlPoint Online App for Modern Authentication Purging Historical Activity and Storage Data from the ControlPoint Services (xcAdmin) Database Modifying ControlPoint Configuration Settings
Changing Default Settings for Actions and Analyses Changing Default Settings to Improve Application Performance Changing Settings to Improve Discovery Performance Changing Default Settings for Navigation Changing Trace Switch Logging Levels Changing Default Settings for Compliance Managing Site Provisioning Settings Setting Preferences for the ControlPoint Scheduler Changing Settings for Anomalous Activity Detection Miscellaneous and Custom Configuration Settings Special-Purpose Configuration Settings ControlPoint Online-Specific Settings

Maximum Number of Users to Act On (MAXUSERSFORACTION)

By default, when you want to run a ControlPoint action that operates on SharePoint users, up to two thousand (2000) users may be included in the operation, as determined by the People Picker entry.  Before running the action, ControlPoint evaluates the number of users included in the People Picker entry, and if it exceeds the maximum number allowed, the action is not carried out and the following message is recorded in the ControlPoint Task Audit:

The number of users ([numusers]) has exceeded the allowable threshold of [maxusers].

This setting is especially useful as a "safety net" when an operation allows wildcards to be used in the People Picker and could potentially act on more users than intended.

ControlPoint Application Administrators can, however, specify a different limit by changing the Value of the ControlPoint Configuration Setting Maximum Number of Users to Act on.

NOTE:  This is an Advanced Setting.


NOTE:  This setting does not apply to users within the scope of a SharePoint User Profile property selection, for which no maximum is enforced.


Changing Trace Switch Logging Levels

ControlPoint contains a number of trace switches that control the type and level of detail that is captured in the ControlPoint Administration (xcAdmin) log. Quest Support may suggest that one or more of these be changed for diagnosis and troubleshooting purposes.

NOTE Trace switches are Advanced settings.

Valid values for all trace switches, listed from least to most detail, are:


·Error (the default)




Trace Log Valid Values

Note that as the logging level increases, the amount of detail is "additive." For example, if you select the logging level Info, then Errors and Warnings will also be included.

If you want to change the logging level  for...

Edit the following setting ...

the SharePoint hierarchy building for navigation and selection

SharePoint Hierarchy Access Logging

the amount of time it takes the SharePoint Hierarchy to load

SharePoint Hierarchy Load Time Logging

reports and actions general processing

Traverse Entry Logging

Additional Traverse Entry Logging

the interaction between ControlPoint and databases

Database Interaction Logging

the validation of SharePoint users by ControlPoint

SharePoint Access Logging

aspx page major events

aspx Page Major Event Logging

the interaction between ControlPoint and Active Directory

Active Directory Interactions Logging

operations performed by the ControlPoint Scheduler

ControlPoint Scheduler Logging

the management of linked SharePoint groups

Manage Linked SharePoint Group Logging

WCF Services calls

WCF Service Call Logging

ControlPoint Policies and Site Provisioning operations

ControlPoint Policies Logging

copy/move at set site properties operations

Copy/Move and Set Site Properties Logging

Interactive Analysis (SharePoint 2010)

Interactive Analysis Logging

non-specific events

Non-Specific Event Logging

Audit Log archiving

Audit Log Archive Logging

Workflow reporting for the Comprehensive User Analysis

Comprehensive User Workflow Report Logging

access to the Managed Metadata Service Application database

Managed Metadata Service Application Database Access Logging

ControlPoint operations performed via PowerShell

PowerShell Processing Logging

Set List properties operations

Set List Properties Logging

Social Activity Analysis processing

Social Activity Analysis Logging

ControlPoint Statistics Lists calculations

Statistics Lists Calculation Logging

the ControlPoint Database Recovery operation

ControlPoint Database Recovery Logging

Changing Default Settings for Compliance

These configuration settings display in the ControlPoint Settings list under the category Compliance, and apply when Sensitive Content Manager is installed in your environment.

Compliance Endpoints

As an alternative to setting all Sensitive Content Manager EndPoints via the Sensitive Content Manager Configuration Maintenance dialog (the recommended method) you can set them individually.

The Value of each Compliance EndPoint must be set to point to the server(s) on which Sensitive Content Manager is configured your environment.  Use the information in the following table for guidance.


Sensitive Content Manager Configuration Maintenance Equivalent

Web Services Endpoint for Compliance Scan Upload

Sensitive Content Manager Upload EndPoint

Web Services Endpoint for Compliance Scan Results

Sensitive Content Manager Results EndPoint

Web Services Endpoint for Compliance Profile Requests


Sensitive Content Manager Profile EndPoint


Sensitive Content Manager Search Terms




Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating