Chat now with support
Chat with Support

ControlPoint 8.7 - 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 Setting Sensitive Content Manager EndPoints and Managing Scanning Preferences Managing ControlPoint Configuration and Permissions 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

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.  

 

"A Script on the Page is Causing Internet Explorer to Run Slowly..."

Message  

A script on the page is causing Internet Explorer to run slowly.  Stop running this script?

Possible Resolutions

If you encounter this message when trying to expand a node in the left navigation pane,  click [Yes] then re-open the node.  

Note that, once child items within a node are loaded, they are cached and are not reloaded:

·for the remainder of your ControlPoint session

OR

·until the SharePoint Hierarchy has been refreshed.

ControlPoint Application Administrators may also find that decreasing the number of child items that display within a subfolder improves performance, especially if it has been set higher than the default value.  (The more items there are within a subfolder, the more time it will take for them to load.)

You may also be able to alleviate the issue by adjusting certain Internet Explorer configuration settings. Quest Support can provide more detail.

 

Troubleshooting Discovery

 

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating