When you start the Management Console for Unix service, it reads Java Virtual Machine (JVM) system variables from a configuration file.
You can set custom configuration settings by adding system variables, one per line, to the custom.cfg file, in the form:
The custom.cfg file is in the application data directory:
%SystemDrive%:\Documents and Settings\All Users\Application Data\Quest Software\Management Console for Unix\resources
%SystemDrive%:\ProgramData\Quest Software\Management Console for Unix\resources
Here are some general tips for adding system variables to the custom.cfg file:
The following topics give you details about setting custom system variables:
Management Console for Unix uses a heartbeat to verify that the:
You can customize the heartbeat interval for the automatic QAS Status update. However, if you change the heartbeat interval you must reconfigure automatic QAS agent status for all hosts previously configured.
To customize heartbeat interval
Locate the custom.cfg file.
(See Setting Custom Configuration Settings for more information about customizing configuration settings for the mangement console.)
Add the following property:
where n is the number of times per day. (The default is 6 times a day.)
Valid values are: 1,2,3,4,6,8,12, and 24 times a day.
The actual time of day that heartbeats are sent vary from host to host.
Save the custom.cfg file.
Restart the Management Console for Unix service.
Technical Support may request that you enable and generate some debug logs for troubleshooting purposes.
To enable the debug log
(See Start/Stop/Restart Management Console for Unix Service for details.)
(See Setting Custom Configuration Settings for general information about customizing configuration settings for the mangement console.)
By default, the debug logs are saved in the application data directory at:
%SystemDrive%:\Documents And Settings\All Users\Application Data\Quest Software\Management Console for Unix\logs
%SystemDrive%:\ProgramData\Quest Software\Management Console for Unix\logs
Management Console for Unix uses the host computer's Active Directory credentials to publish its address to the Control Center, perform single sign-on, and to validate a user's log on. On a Microsoft Windows server, the host computer's credentials are available by means of the Windows SSPI, but this limits Management Console for Unix to managing hosts in the same forest to which the Windows server is joined.
If you wish to use Management Console for Unix to manage a foreign domain or forest from a Windows server, then you must disable SSPI. (See Disable SSPI for Single Sign-on.) However disabling SSPI will disable single sign-on capabilities.
Note: To perform single sign-on, you must
On a Unix server, Management Console for Unix looks for the host computer's credentials by searching for a Kerberos keytab file in the following default locations:
To override the default location, set the console.keytab system property in the custom.cfg configuration file, as follows:
(See Setting Custom Configuration Settings for more information about overriding the default configuration settings.)
If Management Console for Unix cannot find host computer credentials, it will run without host credentials by relying on a correctly configured DNS to find foreign domain controllers. This means that Management Console for Unix will be unable to publish its address to the Control Center, perform single sign-on, or fully validate passwords used when logging on.
Note: When you install Management Console for Unix2.5 on Windows 8, Windows SSPI is automatically turned off because single sign-on does not currently work on Windows 8.