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

Search Using Cached Data (CACHEDSEARCH)

By default, ControlPoint uses real time data to search the SharePoint Hierarchy for operations such as:

·Search Hierarchy

·Change Selection

·Copy/Move destination selection

The use of real-time data means that search results are always current and will include even sites that were created immediately before the search was initiated.  It may also take more time to complete a search, depending on its scope.  If ControlPoint users routinely conduct searches that include a large numbers of objects, ControlPoint Application Administrators can configure ControlPoint to use data from the ControlPoint database cache (and thus speed up searches) by changing the Value of the ControlPoint Setting Search Using Cached Data from false to true.

NOTE:  This setting applies to the search functionality only.  The full browse tree always uses real-time data.

If cached data is used, search results will not include sites for which users only have permissions via a Web application policy.

NOTE:  Data from this cache is current as of the last Discovery run.


Maximum Number of Objects to Display Before Foldering (NAVCAP)

By default, the maximum number of child objects (that is, site collections, sites or lists) that can display directly beneath a single parent in the left navigation pane is 45.  (That is, up to 45 site collections can display beneath a Web application, up to 45 sites beneath a site collection, and so on).  This limit is set to provide you with predictable performance when opening nodes within the navigation tree; it takes additional time to open a node that contains a large number of objects.

If the number of child objects beneath a particular node exceeds the set limit, ControlPoint generates a series of subfolders which contain subsets of objects, grouped alphabetically, as shown in the example below.  

Hierarchy Foldering

ControlPoint Application Administrators can modify this number by changing the Value of the ControlPoint Setting Maximum Number of Objects  to Display Before Foldering.

NOTE:  While you may want to decrease this value, it is generally recommended that you not increase it, as performance may be negatively impacted and may trigger a warning message in the browser.

Config Setting NAVCAP

This setting applies to site collections, sites, and lists.  The maximum number of SharePoint users and groups that display beneath a site are configured via different parameters.  See:

·Maximum Number of SharePoint Groups to Display in SharePoint Hierarchy (SPGROUPCAP)

·Maximum Number of Users to Display in SharePoint Hierarchy (SPUSERCAP)


Maximum Number of SharePoint Groups to Display in SharePoint Hierarchy (SPGROUPCAP)

By default, up to 45 SharePoint Groups can display beneath a site in the SharePoint Hierarchy.

ControlPoint Application Administrators can, however, modify this number by changing the Maximum Number of SharePoint Groups to Display in SharePoint Hierarchy Value.

Config Setting SPGROUPCAP

If the number of SharePoint groups with permissions to a site is greater than the specified parameter value, the list will be truncated. For example, if you set the Maximum Number of SharePoint Groups to Display in SharePoint Hierarchy Value to 10, and 12 groups have permissions to a site, the first 10 groups (in alphabetical order) will display in the Groups folder.  (Remember, however, that the total number of groups with permissions for the site displays in parentheses to the right of the Group folder.)


Preload All Site Collections in Server-side Cache (PRELOADSITECACHE)

By default, whenever you expand a Web application in the SharePoint Hierarchy,  site collections are loaded—and any folders within which site collections are grouped are built—in real time.  For Web applications that contain an excessively large number of site collections (such as thousands of MySites), the time it takes to expand a Web application may be prohibitively long.  

ControlPoint Application Administrators can configure ControlPoint to load site collections and folders from a server-side memory cache—so that the contents of Web applications can be displayed immediately—by changing the Value for the ControlPoint Setting Preload All Site Collections in Server-side Cache from false to true.


This server-side cache is updated on the first request to ControlPoint after its application pool is recycled.  If IIS is configured for a nightly recycle, the restart would occur shortly thereafter.  Normally the first request is from the ControlPoint Scheduled Job Review task.  The server-side cache can also be refreshed on an as-needed basis from the Manage ControlPoint panel.

NOTE:  The child objects within a site collection are not affected by this setting and will always load in real-time.  

Whenever the Preload All Site Collections in Server-side Cache Value is changed, the application pool must be recycled for the change to take effect.


Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating