Chat now with support
Chat with Support

Metalogix ControlPoint 8.6.1 - 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
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 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

Depth at Which to Stop Discovey When Time Restriction is Reached (DISCOVERYRESUMELEVEL)

By default, when the Maximum Discovery Run Time limit is reached, the Full Discovery process will stop after it has finished processing the current site collection.  For farms with deeply nested sites, however, ControlPoint Application Administrators may want to specify a location within the site collection at which Discovery will stop by changing the Value of the ControlPoint Configuration Setting Depth at Which to Stop Discovery When Time Restriction is Reached.

The number you enter represents the depth below the site collection (which is represented by 1, the default value) within the site being processed where you want Full Discovery to resume the next time it runs.


When the Depth at Which to Stop Discovery When Time Restriction is Reached limit is reached, Discovery will finish processing the current site and its immediate children.  It will stop when it reaches the specified level within the next site in the site collection.


Discovery Pause Time to Allow Other Operations (DISCOVERYSLEEP)

ControlPoint Discovery is task that collects cached information for data analysis and reporting.

Because Discovery is a resource-intensive process, it is configured to pause at regular intervals to allow other processes to access a greater share of the machine's CPU and disk resources.  

ControlPoint Application Administrators can change this pause time by modifying the Value of the ControlPoint Settings Discovery Pause Time to Allow Other Operations. This value represents the number of milliseconds that Discovery pauses to let other processes proceed.  


If the Discovery Pause Time to Allow Other Operations value is decreased, the Discovery process will take less time to complete, but users will experience slower response times while it runs.  Conversely, if this value is increased, the Discovery process will take longer to complete, but users will experience faster response times.

TIP:  If Discovery is run only as a nightly process and system usage is low at that time, the default value is usually sufficient. If Discovery is run manually while users are active, and/or usage is high when nightly Discovery is run, it may be advantageous to increase the Discovery Pause Time to Allow Other Operations time.  


SQL Command Timeout for Discovery Process (DISCOVERYTIMEOUT)

By default, any single call to SQL server during the Discovery process will time out after 1200 seconds (20 minutes).  If Discovery does not complete successfully and the ControlPoint Administration Log (xcAdmin.log) indicates that a timeout has occurred, ControlPoint Application Administrators can increase the SQL Command Timeout for Discovery Value.



As of version 5.2.345.0, Full Discovery can run a maximum of 1260 minutes (21 hours) at one time.  If ControlPoint has a particularly large farm to discover and Discovery has not completed within that timeframe, it will continue where it left off the next time it is run, either manually or on schedule.  ControlPoint Application Administrators may want to decrease the time restriction—to ensure that Discovery is not consuming system resources during peak usage times—by updating the Value of the ControlPoint Configuration Setting Maximum Discovery Run Time.


NOTE:  If the Value is blank, Full Discovery will be processed in a single run.

The location within a site collection where Discovery will stop when the time restriction is reached is determined by the Configuration Setting Depth at Which to Stop Discovery When Time Restriction is Reached.


Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating