This section describes steps that you can take to ensure that your existing environment is in a state that facilitates a smooth upgrade.
To prepare your existing environment for upgrade:
Ensure that all agent computers are available and communicating with their designated management server:
In the Control Center console, ensure that there are no open events from the AppManager for Self Monitoring module (AMHealth) that indicate a problem with an agent computer. If you find issues, resolve them.
Use Control Center to create a Server view that shows agent computers where the agent status is offline and resolve any issues with offline computers. For more information about creating a Server view, see the Control Center User Guide for AppManager, available on the AppManager Documentation page.
Use the netiqsync.exe utility to check for differences in job status between agents and QDBs and, optionally, stop orphaned jobs. The utility is available in the Extras\Agent Migration\Utilities\Appmanager Tools folder in the location where you saved the installation package. For more information about using the utility, see the readme.txt file.
Back up the CCDB and all QDBs. For more information about creating a backup copy, see Section A.2.1, Creating Backup Copies of the Repositories.
Ensure that the management server is in a healthy state:
From a command prompt on the management server, change directory to Program Files (x86)\NetIQ\AppManager\bin and enter netiqctrl.exe.
To identify any pending jobs, enter stat Server_Name netiqms, where Server_Name is the name of the management server.
(Conditional) If the output shows jobs in a constantly pending state, cold start the management server to force a refresh of the pending jobs.
(Conditional) If you have configured custom maintenance jobs (for example, database maintenance jobs), disable them until the upgrade is complete.
Use Control Center to identify any ad hoc child jobs with a monitoring policy as a parent and take steps to clean up the ad hoc child jobs:
Create a new Jobs view in the Master management group (or modify the existing Jobs view) with the following characteristics:
Flat view showing only child jobs
No server or local filters applied
In the new or modified Jobs view, filter the Job Type column to display only ad hoc jobs and filter the Knowledge Script column to display only jobs started by the Knowledge Script Group that is running as a monitoring policy (for example, AMHealth_HealthCheckAMAgentComponents).
(Conditional) If the new Jobs view displays jobs after you apply the filters, either stop and delete the jobs or contact Technical Support for help with cleaning up the environment.
NOTE:Because it is possible to create ad hoc jobs from a Knowledge Script Group that has not been applied as a monitoring policy, use caution when performing this step and ensure that the ad hoc jobs are children of a parent monitoring policy.