This section provides some tips for troubleshooting deployment tasks.
When you install the AppManager agent, if the installation was successful but the agent computer does not appear in the Servers view of the Master management group, you might need to add the computer and re-run Discovery. For more information, see Section 3.4, Adding a Computer to the Master View of a QDB.
If you enable a rule but do not see the deployment tasks you expect, it might be due to one of the following reasons:
The corresponding tasks have already completed. Look for tasks in the Tasks view with a status of Completed.
The installation package is already installed on the agent computer. The Deployment Service does not generate a deployment task if the installation package is already installed on the agent computer. For example, if you configure a rule to install the AppManager agent and module for Microsoft SQL Server, if the same version of the agent is already installed, the Deployment Service generates only the deployment task for Microsoft SQL Server. Check the Software Inventory list of installed AppManager components on the agent computer.
There might be an error in the configuration of the installation package. Review the Status Details column for the deployment rule for any errors. For example, invalid credentials might be specified in the configuration.
No agent computers were selected. Review the rule to verify the agent computers are specified.
When you finish configuring the deployment rule, the Deployment Service generates the deployment tasks, but the tasks are not deployed correctly because the agent computer does not support the packages you want to install.
You need to wait until the deployment task installs the AppManager agent. The Deployment Service does not generate deployment tasks for modules until the agent installation is complete.
If the agent computer does not have software inventory information for the AppManager agent, the AppManager agent cannot communicate with the deployment Web server computer or you specified the wrong the deployment Web server computer name when you configured the agent installation package.
If you do not want a task to be recreated after you delete it, do one of the following:
Disable the associated deployment rule that generates the deployment task.
For those tasks you do not want to run that are associated with a deployment rule you do not want to disable, reject the task to change its status to Rejected.
Deployment tasks can enter an Error state for a variety of reasons, such as an incorrect installation package configuration. Review the status details for a task in an Error state by clicking the task and in the Tasks tab clicking Deployment Task Properties. The Deployment Task Properties window also includes information from the pre-installation check.
Another common source of errors with deployment tasks is providing incorrect credentials in the deployment rule. The Deployment Rule Wizard does not validate the credentials you specify. To validate the credentials for a deployment task, click the task and in the Tasks tab click Change Credentials.
To generate new deployment tasks after you update a rule, delete any existing deployment tasks. After you delete the existing tasks, the Deployment Service can generate new deployment tasks.
If you uninstall the AppManager agent manually from the local computer, it can take up to 72 hours for the Deployment Service to create a new deployment task for the installation package. For more information about changing this interval, see Section 9.3, Deployment Preferences.
If you encounter the following error when installing the AppManager Windows agent, view the msierror.log file on the agent computer to determine the errors:
The Windows Installer encountered a fatal error, so the installation could not complete.
Typically this error occurs when:
The agent computer does not have enough free disk space for Control Center to install the AppManager agent. The AppManager agent requires approximately 30 MB of free disk space.
The specified installation path does not exist. If you specify an invalid installation path, Control Center installs the agent in the default location, C:\Program Files\NetIQ\AppManager.
The msierror.log file is typically located in %SystemRoot%\temp\WmiRel. To access this file on a remote computer, you must have Administrator privileges to \\MACHINENAME\ADMIN$\Temp\WmiRel\msierror.log.