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

Show Nested Active Directory Groups (PROCESSADHIERARCHY)

By default, when you generate a Permissions analysis and choose to Include users with AD group membership, only the top-most group that a user is a member of displays in analysis results (that is, if the user is a member of a subgroup within that group, the path to that subgroup is not shown).  

PROCESSAD_false

ControlPoint Application Administrators can, however, choose to have the entire group hierarchy (that is, the path to any subgroup of which the user is a member) display in analysis results by changing the Show Nested Active Directory Groups Value from False to True.

NOTE:  This is an Advanced Setting.

Config Setting SHOWADGROUPS

PROCESSAD_true

NOTE:  When the entire AD hierarchy must be processed, performance may be impacted. Remember that you can also view the full Active Directory hierarchy by opening the AD Group Membership dialog.

AD Group Members dialog

 

Use Minimum Activity Date as Start Date (USEACTIVITYDBDATES)

By default, when an Activity analysis is invoked, users are allowed to enter a Start Date that precedes the earliest record of activity retained in the database.  ControlPoint Application Administrators can, however prevent an earlier Start Date from being entered by changing the Value of the ControlPoint Configuration Setting Use Minimum Activity Date as Start Date from False to True.

NOTE:  This is an Advanced Setting.

WARNING:  Depending on the size of your SharePoint environment, setting this value to True may result in significantly longer page load times, as ControlPoint must perform a query to determine the first valid Start Date that can be entered.

Config Setting USEACTIVITYDBDATES

NOTE:  If this value is set to False, ControlPoint can only retrieve data as far back as the oldest record of activity retained in the database, regardless of the Start Date entered.

Changing Default Settings to Improve Application Performance

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

 

Time to Run an Operation Before Timing Out (OPERATIONTIMEOUT)

When you initiate an operation in ControlPoint, ControlPoint will use WCF to start the operation on all farms that are part of the operation.  By default, this WCF request will time out if it has not been completed within 24 hours.  For an operation performed on a home farm, a timeout message will be recorded in ControlPoint Administration Log (xcAdmin.log) stating that the operation was taking too long; however, the operation will be completed normally and you will see results in the ControlPoint user interface.  For a remote farm in a multi-farm installation, the same message will be recorded, but the operation will not be completed but the user interface will "hang" until it is cancelled.

ControlPoint Application Administrators can change the amount of time it takes for an operation to complete before timing out by updating the Value of the ControlPoint Configuration Setting Time to Run an Operation Before Timing Out.

Note that this time is expressed in hours.

Config Setting OPERATIONTIMEOUT

 

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen