AppManager for Microsoft Windows provides several categories of Knowledge Scripts that enable you to identify and monitor resources of Microsoft Windows operating systems. These Knowledge Scripts provide an overview of the health and availability of Microsoft Windows in your environment.
Key Features
This hotfix resolves the following issues:
- General_EventLog does not have the ability to ignore events that occur on an AppManager agent while the agent is in maintenance mode.
- General_Report_PingMachine returns a runtime error when no data is found in the AppManager repository for the specified report period.
- General_Counter does not allow a cluster name or computer name in a counter string query.
- NT_CPULoaded jobs are taking too long to run, and processor usage for the top N processes is only collected when an event is raised.
- Async_NTEventLog
- Async_NTEventLog Knowledge Script has high memory usage in
netiqmcwhen monitoring a large number of new events. - Async_NTEventLog Knowledge Script does not take agent maintenance mode into consideration.
- Async_NTEventLog Knowledge Script does not properly collect data for event matches found while the AppManager agent is in maintenance mode.
- Async_NTEventLog Knowledge Script has high memory usage in
- Async_NTEventLogRX Knowledge Script:
- Async_NTEventLogRX allows monitoring of most recent new event log fields.
- Async_NTEventLogRX Knowledge Script has the wrong event severity for used for success audit event type.
- AMAdmin_UpgradeJobs no longer being shipped with AppManager.
- NT_PagingHigh allows use of a higher
pagefileactivity per second threshold. - General_EventLogRX:
- Using a filter file for filtering causes job errors.
- General_EventLogRX Knowledge Script does not have the ability to ignore events on an AppManager agent that occur while the agent is in maintenance mode.
netiqmc.exefails due to an unhandled exception fromqdotneta4.dll.- NT_ServiceHung Knowledge Script:
- NT_ServiceHung Knowledge Script does not have the ability to exclude specific services when monitoring all services.
- NT_ServiceHung Knowledge Script does not maintain the Process ID (PID) for the process serving each monitored service.
- NT_ServiceHung does not allow selecting services to monitor by start-type.
- No matching data streams are found when configuring
ReportAMKnowledge Script jobs, or a timeout is received when selecting the Knowledge Script, data stream or server group during configuration ofReportAMjobs. - Discovery_ReportAgent does not run properly within AppManager 9.1 and later environments.
- NT_RegistryChange cannot detect registry key or value changes across agent service, agent computer, or job restarts.
- Attachments specified in Action_SMTPMail actions with file paths that contain whitespace within the path (Example:
C:\Program Files (x86)) result in an error that the attachment cannot be found.
File Description
| Filename | Usage |
|---|---|
| AM70-WinOS-8.1.X.0.msi | This is the module installer |
| AM70-WinOS-8.1.X.0.ini | This configuration file is used with the AppManager setup program. |
| AM70-WinOS-8.1.X.0.xml | This configuration file is used for deploying the module with Control Center. This is the file you check into the Control Center Web Depot |
| AM70-WinOS-8.1.X.0-RepositoryFiles.exe | This compressed file contains the QDB and console files. You do not need to run this file during installation |