Chat now with support
Chat mit Support

ControlPoint 8.8.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 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 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

Users with Permissions Granted Through a Claim are not Showing Up in Permissions Analysis Results

Issue

One or more users who have permissions to SharePoint objects through a claim are not being included in permissions analysis results.

Possible Reason

If your SharePoint farm includes claims-based authentication, permissions granted through a claim may not be reliably reported because SharePoint only retains permissions information for an augmentation claims-based user for a limited time after the user logs in.

The same behavior can be observed in SharePoint. For example, the SharePoint Site Permissions > Check Permissions feature may or may not show permissions granted through an augmentation claim, depending on when the user last logged in.

 

Troubleshooting Site Provisioning

 

Site Provision Request Workflow Failed on Start

Issue

The SharePoint workflow associated with Site Provisioning is configured to start automatically but the Workflow Status column of the Site Provisioning Manager grid, shows a status of Failed on Start.

Possible Reason

Configuration information for the SharePoint workflow components that support automatic starting must be added to ControlPoint.

Workaround

You may need to start the workflow manually.  You can access the Workflow page for the Site Creation Requests list via the [Workflow] button on the Manage Provisioning Requests page.  

 

Provisioning Requests Manager: Workflow Status Column is Blank

Issue

In the Site Provision Request Manager, the Workflow Status column is blank for all requests

Site Provisioning Workflow Status NULL

Possible Reason

·The Value of the ControlPoint Setting does not match the name of the workflow used for Provisioning request processing.

OR

·WorkFlowName is correct, but the workflow has not been started.

Solution

Make sure the WorkFlowName is the same as the name of the workflow used to process Provisioning requests and that the workflow has been started.

 

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen