立即与支持人员聊天
与支持团队交流

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

Number of Child Objects Specified for an Object in the SharePoint Hierarchy Doesn't Match Number Displayed

Issue

When you expand a Web application or site collection in the SharePoint Hierarchy, the number of child objects you see is fewer than the number that appears in parentheses.

Reason

ControlPoint is security-trimmed to enforce SharePoint permissions.  The number in parentheses beside an object represents all child objects.  However, the objects that you actually sees depends on your SharePoint permissions.  See ControlPoint Security in the ControlPoint User's Guide.

 

The Loading of Site Collections in the SharePoint Hierarchy is Extremely Slow

Issue

When a Web application in the SharePoint Hierarchy is expanded, it takes an exceptionally long time for site collections to load

Possible Reason

When a Web application is first expanded, ControlPoint must both load the site collections and build the folders into which they are grouped (based on the value specified for the ControlPoint Configuration Setting Maximum Number of Objects to Display Before Foldering (NAVCAP).  If the Web application has an extremely large number of site collections (for example, thousands of MySites), this process can be time-consuming.

Resolution

The ControlPoint Application Administrator can increase the amount of time that foldered objects in the SharePoint Hierarchy remain in cache.

If the time that takes for site collections to load is unacceptably slow, ControlPoint Application Administrator can configure the application to pre-load site collections from a server-side cache .

 

Error Occurs When Attempting to Launch ControlPoint from a SharePoint Site

Issue

When an attempt was made to launch ControlPoint from within a SharePoint site, a dialog displays with a message that an unexpected error has occurred.

Possible Reason

The ControlPoint for Site Admins and/or ControlPoint Menus for Site Settings feature was activated for the site but was not configured properly for the farm.

Resolution

Follow the procedure for Configuring Site Administration Features for Your SharePoint Farm.  After updating the file webnew.config, remember to save it as web.config.

 

A Business Administrator's SharePoint Sites Do Not Display in the SharePoint Hierarchy

Issue:

·When a member of the ControlPoint Business Administrator's group logs into ControlPoint, the SharePoint site collections/sites that the user manages do not display in the SharePoint Hierarchy.

OR

·A Business Administrator's permissions for SharePoint sites have changed, but those changes are not reflected in the SharePoint Hierarchy.

Possible Reason(s):

·The user does not have sufficient permissions for the SharePoint site(s) to be administered

·The user has management permissions for a subsite but not its parent site.  (By default, if a member of the ControlPoint Business Administrators group has permissions to manage a subsite at any level below a site collection's root site but does not have permissions to manage its parent, the subsite does not display in the ControlPoint SharePoint Hierarchy or object pickers.)  

Config Setting SHOWALLBASITES FALSE

· Since the last ControlPoint Discovery:  

§the user was added to the Business Administrator's group

OR

§the user's SharePoint permissions have changed.

Possible Resolution(s):

·Make sure the user has Full Control or equivalent permissions to the SharePoint sites to be administered in ControlPoint.  See Making ControlPoint Available to Business Users (Site Administrators) in the ControlPoint User's Guide.

·If the user has management permissions for a subsite but not its parent site, the subsite will be included in a ControlPoint operation if it is within the scope of the selection, even if it does not display in the SharePoint Hierarchy.  ControlPoint Application Administrators can also configure the application to display all Business Administrator sites in the SharePoint Hierarchy .

·Either run an interactive Discovery or wait for the scheduled Discovery job to run.  

 

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级