Chat now with support
Chat with Support

ControlPoint 8.6.1 - for Office 365 Administration Guide

Preface The ControlPoint Configuration Site Managing Your Farm List Managing Your ControlPoint License 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 Registering and Re-registering the ControlPoint Online App for Modern Authentication 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
Troubleshooting

Maximum Number of Objects to Pass to the Selection Builder (MaxObjectsForSelection)

By default, when a ControlPoint user wants to initiate an operation from search or data analysis results, an unlimited number of SharePoint sites can be added to the Selection Builder.

Selection Builder

A large number of objects passed to the Selection Builder may, however, significantly drain system resources.  ControlPoint Application Administrators can limit the number of sites that are added to the SelectionBuilder by changing the Value of the ControlPoint Setting Maximum Number of Objects to Pass to Selection Builder.  (Note that 0 is used as the default value to represent "unlimited.")

Config Setting MaxObjectsforSelection

If the specified number is met, no additional sites will be added to the Selection Builder and the user will be presented with a warning message.

Number of Seconds After Which Browser Reports Server Timeout (SERVERTIMEOUT)

By default, the ControlPoint server timeout value is set to 60 minutes, or 3600 seconds. (The normal browser timeout value is 1.5 minutes.)  This value represents the amount of time that the browser will wait for an action or analysis to complete on the server before issuing the following message:  

An action or analysis you requested is taking longer than expected.  If you requested an analysis, try changing the option to use data from the cache, or narrow the scope of the analysis.  If Discovery was running at the time you made your request, try again after Discovery completes.

The default value should be sufficient in most cases.  To avoid his issue, administrators can:

·narrow the scope of their action or analysis (in the case of some analyses, you can also use cached instead of real-time data)

·if the Discovery process is running, wait for it to complete.

·perform the action or analysis on a scheduled basis.

ControlPoint Application Administrators can modify server timeout by changing the Value of the ControlPoint Setting Number of Seconds After Which Browser Reports Server Timeout.

For example:

·If you are managing a very large farm and you want to be able to perform very large, time consuming actions and analyses, you may want to increase this value.

NOTE:  The size of a search or analysis is also limited by the maximum number of line items that can be displayed in results. See Maximum Line Items in Real-time Reports (REPCAP).

·If you are managing a smaller farm and/or would like to have a server timeout reported more quickly, you can decrease this value.

NOTE:  Remember that this value is specified in seconds.

 

Idle Time Before Session is Terminated (STIMEOUT)

By default, the ControlPoint application session timeout property is set to 600.  This value represents the number of minutes between requests after which a ControlPoint session times out.  ControlPoint Application Administrators can modify the session timeout by changing the Value of the ControlPoint Setting Idle Time Before Session is Ended.

NOTE:  This is an Advanced Setting.

NOTE:  Remember that this value is specified in minutes.  The maximum value for this setting is 525600.

 

Maximum Size of Library in Which to Search for Web Part Pages (WEBPAGESLIMIT)

When either Discovery or an interactive Web Part analysis is run, document libraries are searched for Web Part Pages from which Web Parts are collected.  Because this can be a resource-intensive process, by default only document libraries that have 50 items or fewer are searched. ControlPoint Application Administrators can, however, specify a different threshold by changing the Value of the ControlPoint Setting Maximum Size of Library in Which to Search for Web Part Pages.

Note that, at a higher threshold, more Web Part Pages will be searched, but the process will become more resource-intensive.

NOTE:  If you want to include all document libraries in your search, regardless of size, set the threshold to 0.

 

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating