Converse agora com nosso suporte
Chat com o suporte

ControlPoint 8.9 - 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 Using Discovery to Collect Information for the ControlPoint Database Cache Using Sensitive Content Manager Services Managing ControlPoint Configuration and Permissions Preparing Your Environment for Using ControlPoint Sentinel 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 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
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

Exclude Web Parts from the Discovery (EXCLUDEWEBPARTS)

The ControlPoint Discovery process does not, by default, collect data about Web Parts used in your environment, which would enable administrators to generate Web Parts analyses from the ControlPoint database cache. This is because, depending on the number of Web Parts in your environment, a significant amount of the total processing time may be required.  It is important to note, however, that when Web Parts are excluded from Discovery:

·Web Parts analyses can only be run on real-time (not cached) data, and

·the following list boxes will not be populated (that is, you will not have the option of selecting from a list of  Web Parts):

§Advanced Search - Web Parts Used

§Web Parts by Part / Web Parts by Site - Web Parts.

To include Web Parts from the Discovery process, change the Value of the ControlPoint Setting Exclude Web Parts from Discovery from True to False.

hmfile_hash_247927a9

NOTE:  If you installed ControlPoint prior to version 5.2.345.0, the default value will be false.

Site Collections to Exclude from Full Discovery (URLEXCLUDE)

By default,  the ControlPoint Discovery process runs on all site collections within your SharePoint farm.  ControlPoint Application Administrations can, however, exclude site collections whose url contains a specified text string from both the nightly Discovery process and any interactive Discovery that is run on the entire farm.  

NOTE:  Remember that data in analyses run from cache can only be reported up to the date of the last Discovery

To exclude site collections that contain a particular text string from the Discovery process, enter the string as the Value for the ControlPoint Setting Site Collections to Exclude from Full Discovery.  Enter multiple text strings as a comma-separated list.

Config Setting URLEXCLUDE

CAUTION:  If any part of a site collection's url contains the text string you specified, it will be excluded from Discovery.  Use caution in selecting strings to be sure you do not exclude more than you intend.  For example, the excluded string of "Test" would exclude "My Test Site Collection" but would also exclude "Product Testing."

Web Applications to Exclude from Full Discovery (WAPEXCLUDE)

By default, the ControlPoint Discovery process runs on all Web applications in a SharePoint farm.  ControlPoint Application Administrations can, however, exclude one or more  (up to a maximum of 6) Web applications from the Discovery.

It may be useful, for example, if the Web application that hosts your MySites is large and time-consuming to discover.  You can exclude that Web application from the ControlPoint Discovery.  

NOTE:  Remember that activity data in analyses run from cache can only be reported up to the date of the last Discovery.

To exclude a Web application from the Discovery process, enter the Web application's GUID as the Value of the ControlPoint Setting Web Applications to Exclude from Full Discovery.  Use the following guidelines:

1To locate a Web application's GUID, select the Web application in the ControlPoint Farm Hierarchy, right-click and choose Properties.

2Copy the Id's Property Value and paste it directly into the Value field.

WAP Guid

3Repeat steps 1 and 2 for each Web application you want to exclude (up to a maximum of 6).  Use a comma (,) to separate each GUID in the list.

Changing Settings to Accommodate Special Environmental Factors

These configuration settings display in the ControlPoint Settings list under the category Environment.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação