You can modify console settings to point to a different Core Services computer and enable SQL authentication. You can also adjust the settings to improve console performance.
The console options settings enable you to point to a different Core Services computer, by changing the specified IP address and port number. You can also enable SQL authentication. To modify console settings, click Tools > Options.
NOTE:Secure Configuration Manager supports IPv4 and IPv6 addresses, but uses IPv4 addresses for communication among the console, Core Services, and the Secure Configuration Manager database.
The size of your Secure Configuration Manager database and number of concurrent connections can affect console performance. Secure Configuration Manager automatically refreshes data in the console to ensure that you view the most up-to-date information. However, if the console tries to obtain more data than can be pulled from the database within the specified refresh period, the console can pause or stop responding instead of displaying the requested data. This usually occurs when the database contains a large volume of data, your enterprise has more than 500 endpoints, there are multiple concurrent console connections to the database, or a combination of all these factors.
To remediate the issue, you can increase the refresh period to improve console performance. You can also disable the automatic refresh period and use only the F5 function to manually refresh the console.
To change the console refresh period:
On the Tools menu, click Options.
On the Options window, click Other.
(Optional) To increase the time between refresh intervals, enter a new value in the Refresh Period (seconds) field up to 60 seconds.
(Optional) To disable the refresh rate, deselect the Enable Automatic List Refreshes check box. To manually refresh the console, you must press F5.
Click OK.
You can specify whether Core Services terminates a console session that has been idle for a designated amount of time. You can also specify how often Core Services checks for idle sessions. When a session times out, the console user must log on again. Processes that the user starts before the timeout occurs continue to function. For more information about modifying timeout settings, see the Help for the Database tab of the Core Services Configuration Utility.