Run this Knowledge Script to trigger AppManager Diagnostic Console to diagnose a problem on a target computer that has raised an event. The diagnosis is driven from the console computer specified in the Location field on the Action tab.
When launched, Action_Diagnose performs the following steps:
Verifies that Diagnostic Console 2.1 or later is installed. If Diagnostic Console 2.1 or later is not installed, this script raises an event indicating that the diagnosis cannot be performed.
Determines whether Action_Diagnose is already running on the console computer. If a diagnosis is already running, Action_Diagnosis raises an event indicating that a diagnosis is in progress. Only one instance of Action_Diagnose can be running at any given time.
Invokes Diagnostic Console to perform the diagnosis and generate an .html diagnostic report. Diagnostic Console collects Windows, Exchange, or Active Directory data based on the configuration of the target computer.
NOTE:The target computer must have Diagnostic Console version 2.1 or later installed in order for Active Directory data to be collected. Windows and Exchange data can be collected with Diagnostic Console version 2.0 or later.
Generates a report using the Output folder prefix and Use Report Agent settings parameters, or the Full path to root of output folders parameter if you are not using the Report agent.
Upon completion of the diagnosis, raises an event that contains the results of the diagnosis. An event for a successful diagnosis will contain either a URL to the default.htm file (if Use Report Agent settings is set to y) or the computer name and full path of the location of the output files. An event for an unsuccessful diagnosis contains an error message explaining why the diagnosis was unsuccessful.
NetIQ Object Linking and Embedding (NetIQOLE) must be registered on the computer on which this script runs. NetIQOLE is an automation object that allows AppManager to be run from a command-line. For more information, see the Administrator Guide for AppManager at the NetIQ AppManager Documentation Web site.
Set the following parameters as needed:
|
Parameter |
How to Set It |
|---|---|
|
Length of time to run diagnosis |
Enter the amount of time that you want a Diagnosis to run. The default is 300 seconds. The maximum allowable run time is 900 seconds. A longer run time will produce more data than reports can generate in a timely fashion. The minimum allowable run time is 60 seconds. A shorter run time is not enough for the agent to collect data and send it to the repository. |
|
SQL Login Name |
Enter the SQL user name required for access to the Appmanager repository when collecting Exchange and Active Directory data. Leave this parameter blank to use NT Authentication for accessing the repository. |
|
SQL Password |
Enter the SQL password required for access to the AppManager repository when collecting Exchange and Active Directory data. |
|
Output folder prefix |
Enter a prefix for the output folder that is generated by the diagnosis. The output folder then uses this prefix in the following naming convention: Prefix_ComputerName_DateTime. The default prefix is Diag. NOTE:The ComputerName is the name of the computer being diagnosed. |
|
Use Report Agent settings? |
Set to y to specify that the Diagnostic results should be integrated into the AppManager Web management server (the Report Binder). The default is y. |
|
Full path to root of output folders (if not using Report Agent) |
Enter the full path to the root of where the output folders will be created. NOTE:This parameter is ignored if Use Report Agent settings is enabled. |
|
Event severity when … |
Enter a severity level, between 1 and 40, to indicate the importance of the following events:
|