Chat now with support
Chat with Support

Metalogix ControlPoint 8.2 - Administration Guide

Preface Configuring the Environment in Which ControlPoint Will Run The ControlPoint Configuration Site Managing Your Farm List Managing Your ControlPoint License Configuring Web Applications and Content Databases for ControlPoint Configuring ControlPoint Services Using Discovery to Collect Information for the ControlPoint Database Cache Using Sensitive Content Manager Services Managing ControlPoint Configuration and Permissions Modifying ControlPoint Configuration Settings
Changing Default Settings for Actions and Analyses
Supress "Item is inherited - no processing done" Message(SkipNotDoneMsg) Maximum Line Items in Real-time (REPCAP) "Use Cached Data" Default Value (CACHEDREP) Abort Report Processing on Error (ABORTREPORTONERROR) Display "Include users with AD group membership" Parameter (SHOWADGROUPS) Copy/Move Default Temporary Location (TEMPLOCATION) Time to Retain Page Data in Cache (CACHEREPORT4) Time to Retain Temporary UI Objects in Cache (UICACHEDURATION) Number of Reports to Keep in Memory After Drill-Down (RVSESSIONSKEPT) Exclude Web Application(s) from Statistics List (DASHBOARDWAPEXCLUDE) Number of List Items to Display in Selection Grid (DISPLAYSINGLELISTITEMS) Use Activity Min. Date as Start Date (UseActivityDbDate) Show unique permissions only" Default Value (SHOWUNIQUEPERMONLY) Duplicate Files Report Limit (DuplicateFilesReportLimit) Users to Exclude from Reports (EXCLUDEDUSERS) Eliminate Claims Prefix from Username in Reports (UseCleanedLoginNameInReports) Maximum Number of Orphaned Users to Delete Per Scheduled Batch (OrphanDeleteBatchSize) CSV Delimiter Character (CSVDELIMETER) Largest Active Directory Group to Expand in Reports (MAXMEMBERS) Maximum Number of Users to Act On (MAXUSERSFORACTION) Hide the "Set User Direct Permissions" Action in Permissions Management (PREVENTUSERPERMS) Prevent Set Site Collection Quotas (PreventSetSCQuota) Show Nested Active Directory Groups (PROCESSADHIERARCHY) Hide Interactive Analysis Link (RESTRICTSL) Use Minimum Activity Date as Start Date (USEACTIVITYDBDATES)
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 Changing Trace Switch Logging Levels Changing Default Settings for Compliance 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
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

Maximum Number of Objects to Processed in Parallel (MaxParallelProcs)

By default, ControlPoint Discovery processes up to two site collections/sites simultaneously, for improved performance over sequential processing.  For Actions and reports, sequential processing is used by default (that is, the objects involved (site collection, site, subsite, lists, and so on) are processed one at a time, in hierarchical order).  ControlPoint Application Administrators may, however, choose to

·increase or decrease the maximum number of objects that should be processed simultaneously (i.e., in parallel), and/or

·specify the operation(s) (Discovery, Actions, and/or Reports) for which parallel processing should/should not be used.

It is recommended the Maximum Number of Objects to Process in Parallel Value be set to the number of cores on the server machine where the processing occurs.

If you are encountering errors during the processing of operations for which parallel processing is used, it is recommended that you gradually decrease the Maximum Number of Objects to Process in Parallel Value.  

If the Maximum Number of Objects to Process in Parallel Value is set to 0 or 1, no parallel processing will occur (that is, objects for all operations will be processed sequentially).

Config Setting MaxParallelProcs

NOTE:  If the value is greater than 1 and the value of Operations Using Parallel Processing (ParallelProcs) is blank, parallel processing will apply to Discovery.  Otherwise,it will apply to operations specified for

 

Operations Using Parallel Processing (ParallelProcs)

By default, ControlPoint Discovery processes up to two site collections/sites simultaneously, for improved performance over sequential processing.  For actions and reports, sequential processing is used by default (that is, the objects involved (site collection, site, subsite, lists, and so on) are processed one at a time, in hierarchical order).  ControlPoint Application Administrators may, however, choose to

·increase or decrease the maximum number of objects that should be processed simultaneously (i.e., in parallel), and/or

·specify the operation(s) (Discovery, Actions, and/or Reports) for which parallel processing should/should not be used.

Specify the operations for which parallel processing should be used by completing the Value of the ControlPoint Setting ParallelProcs with one or more of the following values:

·D (Discovery)

·A (Actions)

·R (Reports)

Enter multiple values as a comma-separated list.  

NOTE:  If the Operations Using Parallel Processing Value is blank, parallel processing will apply to Discovery only.

Config Setting ParallelProcs

For this setting to be operational, the Value of the setting Maximum Number of Objects to Processed in Parallel.

 

Objects Subject to Parallel Processing (ParallelProcSites)

By default, when Maximum Number of Objects to Process in Parallel is set to a value greater than 1, ControlPoint processes operations in parallel at the site collection level.  ControlPoint Application Administrators can, however, have parallel operations processed at the site level by changing the Value of the ControlPoint Setting Objects Subject to Parallel Processing from false to true.

NOTE:  This is an Advanced Setting.

Config Settings ParallelProcsSites

SQL Command Timeout Value (COMMANDTIMEOUT)

By default, the ControlPoint SQL Command timeout value is set to 300 seconds. This value represents the amount of time that ControlPoint will wait for a SQL command to execute before issuing the following message:  

[Method Name]Timeout Exception:  The server has timed out.

The default value should be sufficient in most cases.  However, for an exceptionally large or busy farm, the ControlPoint Application Administrator may need to increase the Value of the ControlPoint Setting SQL Command Timeout Value.

NOTE:  This is an Advanced Setting.

Config Setting COMMANDTIMEOUT

NOTE:  Remember, this value is specified in seconds.

 

Related Documents