Users to Exclude from All ControlPoint Policies (CPPOLICYSUPERUSERS)
By default, when you apply a ControlPoint policy to users, all users included in the User Selection will be included in the policy. ControlPoint Application Administrators can, however, exclude specified users from all ControlPoint policies by entering one or more user names (in the format domain\user) in the Value field of the ControlPoint Configuration Setting Users to Exclude from All ControlPoint Policies. Enter multiple names as a comma-separated list.
For example, you may want to exclude from all policies:
·the ControlPoint Service Account, to allow administrators to perform actions such as Delete Site and Copy/Move actions in ControlPoint. (Remember, ControlPoint actions are actually carried out by the ControlPoint Service Account rather than the logged in user).
·all accounts operating as the System Account (sharepoint\system), which may include, but not be limited to, the ControlPoint Service Account.
·farm administrators.
NOTE: You must exclude users based on full account names (sometimes known as pre-Windows 2000account names in Active Directory), not display names. For example, you cannot exclude system accounts by entering the display name System Account.
Users specified in this setting will always be excluded from all policies, including any policies to which they have been explicitly added.
Content Creation Policy url (POLICYSERVICEURL)
When a ControlPoint policy is created that uses a content creation rule, a custom Web service must be set up which runs whenever content is added to a site within the scope of the policy. For example, you may want to be notified whenever a document is posted that contains "flagged" content.
If such a policy is to be implemented, the full service url to the location of the Web service must be the Value for the ControlPoint Configuration Setting Content Creation Policy url.
NOTE: In order to simulate the environment in which it will be used, it is recommended that the functionality be tested on the Web front-end server on which ControlPoint is installed while logged in as the ControlPoint Service account.
Setting Preferences for the ControlPoint Scheduler
These configuration settings display in the ControlPoint Settings list under the category ControlPoint Scheduler.
Maximum Number of Scheduled Jobs to Submit at One Time (MAXSUBMIT)
By default, up to five scheduled jobs can run at any one time. For example, if three scheduled jobs are running at the time the ControlPoint scheduler task next checks the queue for pending jobs, an additional two jobs will be submitted.
ControlPoint Application Administrators can change this number by updating the Value of the ControlPoint Setting Maximum Number of Scheduled Jobs to Submit at One Time.
For example:
·You may want to increase this number if jobs are generally scheduled to run when system usage is low, to allow more of them to run concurrently.
·You may want to decrease this number if interactive performance of your farm is being affected by the processing of scheduled jobs.
This setting can be used in conjunction with Number of Minutes Scheduler Will Wait Before Next Group of Jobs (OVERIDESCHEDULETIMERMINUTES) to fine-tune the behavior of the ControlPoint scheduler.