By default, the AppManager agent services are started automatically whenever you restart an agent computer. Under normal conditions, the agent services are restarted using a warm startup that preserves information about the jobs that were running when the computer was shut down.
When the agent services are restarted using a warm startup, the Client Resource Monitor automatically restarts all of the jobs that were in progress when the computer is rebooted without requiring you to take any additional action. Because all of the job information is preserved between starts, an agent computer that uses a warm startup for the agent services is identified as being in Persistent mode.
If an managed computer is set to use the Persistent mode, any time jobs are interrupted because of power failures, system shutdowns, or network outages, the AppManager agent services are restarted using a warm startup.
It is also possible to perform a cold startup of the agent services. With a cold startup, the Client Resource Monitor does not remember the jobs that were running before the restart. Any monitoring jobs that were running are lost.
By default, the Client Resource Monitor performs a “warm” startup anytime the service is interrupted. This type of restart preserves information from ongoing jobs in the local repository. However, from time to time you may find it useful to perform a “cold” startup, which doesn’t preserve information about jobs or data. For example, if you have accumulated a large number of jobs on a particular computer, you may want to remove those jobs and data.
To perform a cold startup, start the Client Resource Monitor service (NetIQmc.exe) using the -oa option from the command-line. For example, open a Command window, then type the path to the Client Resource Monitor service with these options:
C:\Program Files\NetIQ\AppManager\bin>netiqmc -oa
Once you perform a cold startup on an agent computer, you must run the discovery script, and then recreate the jobs you want to restart. For example, if you have customized the properties for a specific job but have not changed the default properties for the Knowledge Script, when you restart the job you must restore the customized property settings, such as the changes to threshold settings or data collection options. A cold start of the agent also deletes any delta discovery cache files for all delta discoveries performed by the agent.
NOTE:Before performing a cold startup, consider running an AppManager job report to collect details about the jobs you are running.
Normally, you only perform a cold startup of the AppManager agent if an agent service hangs on a computer or if you want to remove unwanted information. But if you find that you want to use this option regularly, you can manually instruct the Client Resource Monitor service to use the -o option at startup.
To manually set the startup parameters for the agent:
Click Administrative Tools in the Windows Control Panel, then click Services.
Select NetIQ AppManager Client Resource Monitor in the list of services.
Click Stop to stop the service.
Type -o in the Start Parameters field.
Click Start, then click OK.
To change the default Client Resource Monitor startup mode, you must edit a registry key.
To change the default agent startup mode:
Use regedit to find the following registry key:
HKEY_LOCAL_MACHINE/SOFTWARE/NETIQ/AppManager/4.0/NETIQMC/CONFIG
Double-click Persistent.
Set the key value to 0 for a cold startup of the agent or to 1 for warm startup of the agent by default.