You must be a member of the Control Center Administrator group to set Control Center preferences. Preferences control certain aspects of how the Control Center console operates.
To set QDB preferences, use the AppManager Operator Console. For more information, see the Operator Console User Guide for AppManager, available on the AppManager Documentation page.
To configure the Control Center console options, on the Main tab, in the Tools group, click Options. In the Options window, click the Console link to configure any of the following options:
General
These options specify the refresh rate for the current view and how to display Severe events in the console.
Events
These options specify how you work with events in the console.
Jobs
These options allow you to configure the console to prompt the user before starting, stopping, or closing a job.
Charts
These options allow you to configure chart settings that affect how much data to display in charts and how often to update the data.
Servers
These options allow you to configure the types of data and how much data Control Center loads in the Server Information pane.
Knowledge Base
These options allow you to enable the console to connect to a Knowledge Base server.
Skin Selection
These options allow you to change the look and feel of the interface.
For more information about the Console options, see the Help.
To configure the Control Center console health check options, on the Main tab, in the Tools group, click Options. In the Options window, click the Health Check link. The options allow you to configure settings for agent and management server health check events. For more information about the options, see the Help.
To configure the Deployment Server options, on the Main tab, in the Tools group, click Options. In the Options window, click the Deployment link to configure the following options:
General
Credentials
These are the default credentials to use when deploying an installation package on a target computer (for example, installing the AppManager agent). You must provide a domain or local user account that is a member of the Administrator group on the target computer. When configuring a rule, you can use the default credentials you specify here or provide different logon credentials.
If you change the default deployment credentials, the change only applies when you create a new rule. Existing deployment tasks maintain their original deployment credentials.
Schedule
These options specify how frequently the Deployment Server should re-run rules and search for new computers, and when deployment tasks should run. You can also set a default schedule for running deployment tasks.
Confirmations
These options specify whether to display a confirmation window before deleting a package, rule, or deployment task.
Task Management
These options specify how to manage deployment tasks, including:
How long to keep a deployment task in the Control Center database.
How long to display a deployment task in the Control Center console.
For more information about the options, see the Help.
To configure the Control Center console Knowledge Scripts options, on the Main tab of the ribbon, in the Tools group, click Options. In the Options window, click the Knowledge Scripts link.
The option Automatically update Derived KS properties for checked in Base KSs determines whether AppManager automatically updates the logic of derived Knowledge Scripts when you install a new module.
Knowledge Scripts are classified as base Knowledge Scripts or derived Knowledge Scripts. A base Knowledge Script is checked in to the primary QDB and holds all of the Knowledge Script settings (the schedule, parameters, and Advanced tab) and the script logic. A derived Knowledge Script is a copy of a base Knowledge Script (a direct copy or a member of a Knowledge Script Group) and shares the logic with the base Knowledge Script but has its own settings. For example, a base Knowledge Script might have a default threshold of 10 for a certain parameter while the derived Knowledge Script has a default threshold of 20. The two Knowledge Scripts share the script logic, but the settings are different.
The default is to automatically update derived Knowledge Scripts. The update retains the settings (such as thresholds and schedule) of the derived Knowledge Scripts and includes monitoring policy jobs but not ad hoc jobs. If a base Knowledge Script includes new values or removed values, AppManager merges those changes to the derived Knowledge Scripts.
If you do not enable the automatic update option, when you log in to the AppManager consoles and base Knowledge Scripts have been updated, AppManager informs you that base Knowledge Scripts are pending propagation to derived Knowledge Scripts and/or running jobs and provides the option to start the Knowledge Script Propagation Wizard to select which Knowledge Scripts and/or jobs to update.
For more information about how Knowledge Scripts and the automatic update option work, see Section 5.0, Running Monitoring Jobs. For more information about monitoring policies, see Section 7.0, Monitoring by Policy.
To configure the Control Center console security options, on the Main tab, in the Tools group, click Options. In the Options window, click the Security link.
Use the Security options to:
Enable FIPS-compliant security algorithms for AppManager. For more information about FIPS-compliant security, see the Administrator Guide for AppManager, available on the AppManager Documentation page.
Disable vulnerable Transport Layer Security (TLS) versions. This option allows you to disable any TLS versions (for example, TLSv1.0) that are considered vulnerable.
This option is selected by default. If you have a management server that communicates with UNIX agents using the encrypted communications only or authentication and encrypted communications security level and this option is selected, the management server will not be able to communicate with the agents because they require TLSv1.0. You must deselect the option to restore communications.
Any time you change the Security options, you must restart any management servers so they will recognize the new security settings. To allow sufficient time for Control Center to synchronize the changes to the connected QDBs, wait at least one minute before restarting management servers.
To configure the Control Center console event severity status options, in the Tools group, click Options. In the Options window, click Event Severity Status.
Enable the option if you want to display the highest event severity for management groups at the top-most level. Otherwise, you must expand management groups to view the event severity icons for servers in the groups.
If you disable the option, you must refresh the console in order for Control Center to apply the change. In addition, after you disable the option, the Repository Synchronization status might be in an Error or Warning state. This is a temporary condition and the status should return to OK after several minutes.
To view the command queue service options, on the Main tab, in the Tools group, click Options. In the Options window, click the Command Queue Service link.
The Command Queue Service link displays four read-only parameters for the command queue service. To change these parameters, you must log on to the computer where the command queue service is running, stop the service, modify the NQCQS.exe.config file, and then restart the service. Before you edit the file, contact Technical Support. For more information about editing the file and additional parameters that are not visible in the Control Center console, see the Administrator Guide for AppManager, available on the AppManager Documentation page.
To configure the Global Preferences options, on the Main tab, in the Tools group, click Options. In the Options window, click the Global Preferences link to configure the following options:
Audit Settings
This option specifies how long to store historical information in certain tables in the repositories (for example, the ArchiveQueue table in the Control Center repository). For more information, see the Help.
Data
This option specifies how long to store the data points that Knowledge Script jobs collect in the AppManager repository (QDB). For more information, see the Help.