The majority of Discovery Performance-related ControlPoint Settings apply to Discovery only when run via the ControlPoint Discovery timer job or via the Control application interface. However, the following settings are also used by the Discovery Service:
You can run a Discovery on your entire farm or a Partial Discovery on selected Web applications/site collections either interactively or on a one-time or recurring schedule.
You may want to manually run a Full Discovery when:
·the nightly Full Discovery job is disabled or has failed to run, or
·you want to perform an ad hoc update to the ControlPoint cache.
A Partial Discovery can be useful:
·when you want to update the ControlPoint cache for specific Web applications/site collections only without having to run a more resource-intensive Full Discovery. (For example, if you just granted new permissions to a user in the Business Administrators group and want sites to be visible to that user in the SharePoint Hierarchy, you can run a partial Discovery just on the Web application(s) containing the sites that the user manages.)
·for Web applications or site collections that you have excluded from the Full Discovery process. For example, some Web applications, such as those that contain My Sites, can greatly increase the Full Discovery run time. Web applications containing such sites may be excluded from the Full Discovery process and scheduled to run less frequently.
IMPORTANT: Unlike Full Discovery, which runs under the ControlPoint Service Account, manual Discovery is run under the credentials of the logged-in user. Therefore, you can only discover site collections for which you are a Site Collection Administrator.
To run a Discovery manually:
1From the Manage ControlPoint tree choose ControlPoint Management > Discovery.
2Use the information in the following table to determine the appropriate action to take.
If you want run a...
do not modify the Selection section.
NOTE: The default selection encompasses the entire farm, except for any Web applications and/or site collections that have been excluded from the Full Discovery process.
select the Web application(s)/site collection(s) on which you want to run Discovery, using the procedure for Changing Your Selection.
NOTE: The Partial Discovery will include all Web applications/site collections that you explicitly select, regardless of whether they have been excluded from the Full Discovery process.
§run the Discovery immediately (by clicking the [Run Now] button).
If you have Sensitive Content Manager installed in your environment, ControlPoint Sensitive Content Manager (SCM) Services can be used as an alternative to the default ControlPoint Scheduled Job Review timer job, which runs from SharePoint Central Administration as a means of checking for:
·content analysis (CA) jobs ready to be uploaded from ControlPoint to Sensitive Content Manager for scanning
·scan results ready to be downloaded from Sensitive Content Manager to ControlPoint for further action.
ControlPoint SCM Services run as Windows Services, and offer the following advantages:
·unlike the ControlPoint Scheduled Job Review job, which checks for Sensitive Content Manager upload and results jobs on a fixed schedule (by default, every ten minutes), SCM Services carry out these checks continuously
·because they support multi-threading, SCM Services are especially suited to very large content analysis jobs.
The Metalogix ControlPoint SCM Services run as Windows Services on the server where ControlPoint is installed.
Note that the letters CA in the name of each service stand for "content analysis."
ControlPoint SCM Services can be configured at the time ControlPoint is installed or upgraded, or at any time when the Configuration Wizard is launched. See Configuring ControlPoint Services for details.
To launch the SCM Services Setup application:
1Navigate to the location where the SCM Services files reside (by default, C:\Program Files\Metalogix\ControlPoint\ControlPointFeatures\Services\ContentAnalysis)
2Open CASetup.exe (using the Run as Administrator option).