Chat now with support
Chat with Support

ControlPoint 8.7 - Administration Guide

Preface Configuring the Environment in Which ControlPoint Will Run The ControlPoint Configuration Site Managing Your Farm List Managing Your ControlPoint License Granting ControlPoint Access to Web Applications and Content Databases Configuring ControlPoint Services Using Discovery to Collect Information for the ControlPoint Database Cache Using Sensitive Content Manager Services Setting Sensitive Content Manager EndPoints and Managing Scanning Preferences Managing ControlPoint Configuration and Permissions Modifying ControlPoint Configuration Settings
Changing Default Settings for Actions and Analyses Changing Default Settings to Improve Application Performance Audit Log Configuration Settings Changing Settings for Anomalous Activity Detection Restricting Functionality for Members of the Business Administrators Group Changing Default Settings for ControlPoint User Groups Changing Settings to Improve Discovery Performance Changing Settings to Accommodate Special Environmental Factors Changing Default Settings for Navigation Managing Site Provisioning Settings Specifying Global Settings for ControlPoint Policies Setting Preferences for the ControlPoint Scheduler Miscellaneous and Custom Configuration Settings Special-Purpose Configuration Settings
Changing Trace Switch Logging Levels Archiving SharePoint Audit Log Data Troubleshooting
ControlPoint Log Files Troubleshooting Configuration Errors Troubleshooting the ControlPoint Application Interface Troubleshooting Discovery Troubleshooting SharePoint Users and Permissions Troubleshooting Site Provisioning Troubleshooting ControlPoint Operations

Use Activity Min. Date as Start Date (UseActivityDbDate)

By default, when an Activity Analysis includes a date range, there are no restrictions on the Start Date users can select, even if it precedes the earliest date that activity that is retained in the database.  ControlPoint Application Administrators can, however, restrict the Start Date that can be selected (that is, prohibit users from selecting a Start Date earlier than the first date of available activity) by changing the Value of the ControlPoint Setting UseActivityDbDate from False to True.

If this value is set to True, page load time may take significantly longer.

"Show unique permissions only" Default Value (SHOWUNIQUEPERMONLY)

When a permissions analyses is initiated, users have the option of including only objects with unique (non-inherited) permissions or objects with both inherited and non-inherited permissions.  Having Show unique permissions only selected is the ControlPoint default.  

ControlPoint Application Administrators can, however, change the default (so that Show Unique Permissions Only is unselected) by changing the parameter value of the ControlPoint Configuration Setting "Show unique permissions only" Default Value from true to false.

Config Setting SHOWUNIQEPERMONLY

 

Duplicate Files Report Limit (DuplicateFilesReportLimit)

By default, when a Duplicate File analysis is run, up to 3000000 (three million) files can be evaluated for duplicates.  ControlPoint Application Administrators can, however, increase this number by changing the Value of the ControlPoint Setting Duplicate Files Report Limit.

NOTE:  This is an Advanced Setting.

DuplicateFilesReportLimit

NOTE:  If you set too high a limit, out-of-memory exceptions may occur, particularly on 32-bit operating systems.

 

Users to Exclude from Reports (EXCLUDEDUSERS)

By default, unless one or more users are specified in the People Picker, all SharePoint users are included in the following ControlPoint analyses:

·Site Permissions

·Comprehensive Permissions

·Site Collection Activity

·Site Activity

·Activity by User

·Activity by Document

·Inactive Users

ControlPoint Application Administrators can, however, exclude certain users and/or Active Directory groups from these analyses by entering the user account name(s) as the Value for the ControlPoint Configuration Setting Users to Exclude from Reports.  Enter multiple account names as a comma-separated list.

You may, for example, want to exclude common system accounts such as Sharepoint\System and NTAuthority\Authenticated Users.  

NOTE:  You must exclude users based on full account names (sometimes known as pre-Windows 2000account names in Active Directory), not display names.  For example, you cannot exclude system accounts by entering the display name System Account.

EXCLUDEUSERS

You can still run permissions and activity reports on excluded users if you enter them in the People Picker.  

NOTE:  You can exclude users from audit log analyses via the ControlPoint Configuration Setting Users to Exclude from Audit Log Analyses.

 

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating