지금 지원 담당자와 채팅
지원 담당자와 채팅

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

Hide the "Set User Direct Permissions" Action in Permissions Management (PREVENTUSERPERMS)

By default, the Permissions Management for Site Admins option includes the option to Grant user(s) permissions directly.

Permissions Management DIRECT

However, ControlPoint Application Administrators can hide this option (if, for example, your organization adheres to the SharePoint best practice of allowing permissions to be granted only via SharePoint groups) by changing the Value of the ControlPoint Configuration Setting Hide the "Set User Direct Permissions" Action in Permissions Management (PREVENTDIRECTPERMS) from false to true.

NOTE:  This is an Advanced Setting.

Permissions Management NO DIRECT

 

Prevent Set Site Collection Quotas (PreventSetSCQuota)

By default, a ControlPoint user can set a site collection quota via the Set Site Collection Properties action only if the user is  a Farm Administrator or has been given elevated privileges via the security override ACTSECOVRW.

Set Site Collection Properties QUOTA

ControlPoint Application Administrators can, however, allow all ControlPoint users to set quotas for site collections that they manage by changing the Value of the ControlPoint Configuration Setting Prevent Set Site Collection Quotas from True to False.

NOTE:  This is an Advanced Setting.

Config Setting PreventSCQuota

When Prevent Site Collection Quotas is set to Truee (the default value), the Site Collection Quota will not be visible to unauthorized ControlPoint users.

Set Site Collection Properties NO QUOTA

 

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.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택