AppManager for Microsoft Windows 8.1.0.5 Release Notes

Support for Windows Server 2019: This hotfix release of AppManager for Microsoft Windows provides support for Windows Server 2019.

Win2000_DFSLinkDown support for Server 2016: This hotfix release of AppManager for Microsoft Windows provides support for monitoring distributed file system (DFS) objects in Windows 2016.(ENG347152)

Option in Discovery_NT KS to control discovery of DFS link objects: By default, the Discovery_NT Knowledge Script discovers the distributed file system (DFS) link objects. However, if there are exceedingly huge number of DFS link objects, discovery could make the environment unstable. This hotfix release adds a check box option in Discovery_NT KS to control the discovery of DFS link objects. By deselecting the check box, you can disable the discovery of DFS link objects.(ENG346596)

NT_DiskSpace throws an error stating "Wrong number of arguments... NQEXT.Item": NT_Diskspace KS is throwing this error when a value for "Drives to monitor" parameter is entered for monitoring a cluster node. With this hotfix release this issue is resolved.(ENG348214)

KS monitoring System EventLog fail error: This issue occurs when more than 23 event IDs are passed in the KS Event ID filter. With this hotfix release, this issue is resolved. (ENG348567)

The executable file nqperfprovider4.exe causes the agent to be in hung or unresponsive state: With this hotfix release of AppManager 9.5, changes are made into the nqperfprovider4.exe, which helps to stop the agent from being in hung or unresponsive state. (ENG348726)

Support for Transport Layer Security 1.2 (TLS): This release of AppManager for Microsoft Windows provides support for TLS 1.2.

Add Threshold Setting to General_EventLog: A new field "Threshold value per event log" is added in the Knowledge Script. If the number of log entries that matches the criteria exceeds this threshold, an event is raised. (ENG348117)

General_AsciiLog fails to return expected results when two strings are entered: While running General_AsciiLog KS with Require Literal Match? multiple strings are entered, and string matching fails. This release of AppManager for Microsoft Windows modifies the search logic from word to character, which resolves the issues. (ENG347133)

NetIQMC crashes when multiple jobs that deal with performance counters run simultaneously: This release of AppManager for Microsoft Windows resolves this issue. (ENG345452)

General_ShortEventLog job causes NetIQMC crash: This release of AppManager for Microsoft Windows resolves this issue. (ENG345850)

Mismatch in mail timing while using Action_SMTPMail KS: While running Action_SMTPMail KS, the Message sent time of the mails sent with attachments are represented in GMT, whereas for the mails sent without attachments are represented in local time. This release of AppManager for Microsoft Windows resolves this issue and all emails have local time. (ENG345583)

Action_SMTPMailRpt report does not open URL links: The URL links in the email reports are relative paths and not complete URLs, and hence does not open in any machine other than the agent machine on which the job runs. This release of AppManager for Microsoft Windows resolves this issue. (ENG346191)

Discovery_Cluster fails to show the discovered resources, in tree view in the consoles, when event collapsing is enabled in the KS: This release of AppManager for Microsoft Windows resolves this issue. (ENG347838)

General_EventLog does not have the ability to ignore events that occur on an AppManager agent while the agent is in maintenance mode. With this release, the Knowledge Script added a new parameter to allow you to tell its job to ignore matching event log records that were written to the monitored logs while the AppManager agent was in maintenance mode. (ENG343204)

General_Report_PingMachine returns a runtime error when no data is found in the AppManager repository for the specified report period. With this release, the Knowledge Script properly detects the state of the record set when it is empty and completes properly. (ENG343096)

General_Counter does not allow a cluster name or computer name in a counter string query. With this release, this Knowledge Script allows querying using a computer name or cluster name in the counter path string parameter so that it can monitor performance counters that are only installed under the context of the cluster or actual computer name. (ENG342308)

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. With this release, the Knowledge Script runs differently with the following settings:

Async_NTEventLog this release resolves the following issues:

Async_NTEventLogRX Knowledge Script, this release resolves the following issues:

AMAdmin_UpgradeJobs no longer being shipped with AppManager. With this release, since AppManager 8.0 and later handle job propagation to upgrade existing jobs, AppManager for Windows is no longer packaging and installing AMAdmin_UpgradeJobs. (ENG343651)

NT_PagingHigh allows use of a higher pagefile activity per second threshold. With this release, you can enter the threshold value up to 9,999 for the Maximum pagefile per second Knowledge Script parameter. (ENG343839)

General_EventLogRX, the following issues are resolved:

netiqmc.exe fails due to an unhandled exception from qdotneta4.dll. With this release, an unhandled exception thrown from netiqmc.exe when running counter-collecting jobs on an agent computer with a large number of installed performance counters was fixed. (ENG344858)

NT_ServiceHung Knowledge Script, this release resolves the following issues:

This release resolves the following issues related to the use of the ReportAM Knowledge Scripts and discovery of the Report Agent:

NT_RegistryChange cannot detect registry key or value changes across agent service, agent computer, or job restarts. With this release, a new Knowledge Script parameter Maintain initial registry information across agent restarts?, has been added to the Knowledge Script to indicate to the job that restarts of an existing NT_RegistryChange job, caused from a job restart, agent service restart, or agent computer reboot, should treat the next first job iteration as a job iteration to compare existing registry information to what was last stored for the monitored registry keys and values. This allows detection of a changed key or value to take place despite the job restart. (ENG344697)

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. With this release, the action can properly find the attachment with the path containing whitespace in its path, and no error will occur as a result of using such a path. (ENG345355)

Action_UpdateEventStatus does not have SQL authentication. In previous releases, only Windows authentication was used in Action_UpdateEventStatus to connect to the AppManager repository to find and make updates to events. With this release, you can enter a SQL Server user account in the SQL Server login parameter for the action to connect to the AppManager repository using SQL authentication. When you specify an SQL Server login, the AppManager's Security Manager collects the password for the user. (ENG342646)

Async_NTEventLog and Async_NTEventLogRx do not monitor logs under Applications and Services logs folder. On Windows Server 2008 and later operating systems, Async_NTEventLog and Async_NTEventLogRx were unable to monitor the custom event logs (for example, channels). In this release, all Windows event logs available for monitoring on an agent computer can be monitored with Async_NTEventLog and Async_NTEventLogRx Knowledge Scripts. (ENG342534)

Async_NTEventLog does not allow filtering on Critical event type. With this release, you can choose to filter on the Critical event type, which is an available type on Windows Server 2008 and later operating systems. (ENG341127)

NT_ServiceDown Knowledge Script includes the ability to monitor services with a partial wildcard. With this release, you can monitor services with similar names in a single job by entering an asterisk before or after the partial name of the service. (ENG275159)

ReportAM_DetailData report generation causes index hint exception error. When running some ReportAM report Knowledge Scripts on AppManager 9.1, error events referencing index hint exceptions were raised. In this release, the exceptions are resolved, so these events will not be raised. (ENG341581)

NT_CpuLoaded Knowledge Script includes NT_TopCpuProcs individual process detail. With this release, the NT_CpuLoaded Knowledge Script adds individual process usage details to events and datastreams created by a job running this script when overall processor usage exceeds the threshold that was set. (ENG341125)

NT_PortHealth can be configured to raise events against the target host. With this release, you can configure an NT_PortHealth job to raise events against the target computer object (proxy events) instead of the agent computer where the job is running. (ENG290400)

Updates to the ReportAM_JobInfo report Knowledge Script. With this release, you can turn off the display of hidden Knowledge Script parameters when running ReportAM_JobInfo, and proxy actions display properly in the report. (ENG264382, ENG225399)

Bug fixes and updates to the NT_FindFiles Knowledge Script. With this release, you can monitor files that reside on a network share (UNC path) with NT_FindFiles. Also, the Knowledge Script can monitor folders that contain over 120,000 files. To accommodate this change, NT_FindFiles was updated to allow disabling the inclusion of filename matches in the detail of events and datastreams raised by this Knowledge Script, because AppManager consoles cannot handle the size of such detail. (ENG341575, ENG342209, ENG342247)

NT_FolderFileCount can now monitor folders with large numbers of files. With this release, you can monitor folders that contain over 120,000 files. (ENG342209)

NT_PortHealth can now test UDP port targets. With this release, you can configure NT_PortHealth to send a stream of data to a UDP port on a target computer to test its availability. (ENG262298)

Bug fixes to the General_EventLog and General_EventLogRx Knowledge Scripts. This release includes bug fixes to General_EventLog and General_EventLogRx to fix several Microsoft .Net exceptions thrown while monitoring events when some event fields are not set by the event provider. Also, an improperly formatted query, when only specific event types were chosen for monitoring, was fixed, so that matching events are properly found on each job iteration. (ENG341880, ENG342331, ENG342072)

General_AsciiLog does not handle events for literal searches properly. In prior releases, when the Require literal match? parameter was set to Yes, events for matches found in the monitoring files were raised for each word in the search string and not for the entire search string. In this release, the issue was resolved and events are raised properly. (ENG342156)

Server groups cannot be selected from ReportAM Knowledge Scripts. When configuring some ReportAM Knowledge Scripts in AppManager 9.1, no server groups are returned in the console for selection. After you install this release, the server groups display and can be selected. (ENG342491)

NT_DiskSpace throws runtime error when using regular expressions in Drives to exclude. When a regular expression was used in the Drives to exclude parameter of NT_DiskSpace, a runtime error would occur. The runtime error was resolved in this release. (ENG342727)

NT_CpuLoaded Knowledge Script now has ability to cap % processor usage. With this release, a new parameter was added to the NT_CpuLoaded Knowledge Script, Cap processor usage values at 100 percent? that allows you to cap the Processor Usage percentage values at 100% on VMWare virtual machines where the counter value is reported over 100%. When set to Yes, the value reported in events and datastreams is 100%, when it is found to be over 100%. (ENG341906)

A new NT Knowledge Script Group is now included in AppManager for Microsoft Windows. With this release, a set of 7 NT-category Knowledge Scripts are customized for out-of-the-box usage and are included in a BestPractices Knowledge Script Group. (ENG341777)

Action_SMTPMail Custom Message options are not working properly. When configuring the SMTPMail action with the Custom message format, the correct message for the event message ($ShortMsg$) variable or event message detail ($DetailMsg$) variable does not display in the SMTP message when a wildcard is used in place of an ending number. In this release, displays the correct message, even if a wildcard is used in the format string. (ENG341145)

NT_DiskSpace event messages show incorrect comparison operators. In WinOS 8.0, the NT_DiskSpace Knowledge Script was converted to the VBScript language. The comparison of collected utilization metrics against the thresholds set in the Knowledge Script resulted in the comparison operators that were wrongly directed in the event details of an event and datastream detail. In this release, the event detail and datastream detail accurately show the comparison operators. (ENG341056)

NT_CPUResource summit string hits maximum limit when 600 processes are running on agent. When NT_CpuResource is running on an agent computer where over 600 processes are present, the detail provided for events and datastreams resulted in a string exceeding the 32K size limit in the Summit BasicScript language used, resulting in a script runtime error. In this release, the NT_CpuResource Knowledge Script has been converted to VBScript, which allows the detail for events and datastreams to handle strings of much larger size. (ENG341017)

General_EventLogRx filter file does not work on WinOS 8.0.93.0. When a file is used to specify the regular expression filters in General_EventLogRx that contains both and exclude filters, the General_EventLogRx did not apply the filters properly to include or exclude events containing the expressions defined. In this release, the filter file parsing and implementation has been fixed to resolve these issues. (ENG341346)

General_EventLog does not detect new events after the first iteration of the job. When using an 8.0 version of the General_EventLog and version 8.0 of the WinOS managed object component installed on an agent, a job iteration that results in no matches found, causes the next job iteration to start its search for new event records to start one record number beyond were it should have started its search. In this release, the last record number reviewed is properly saved for the starting point of the next job iteration when running General_EventLog. (ENG341340)

General_EventLog throws a .Net exception when .NET 4.0 Client profile is present. When a WinOS 8.0 managed object component is installed on an agent computer, with both version 2.0 and 4.0 of the Microsoft .NET Framework installed, the operating system defaulted to loading the managed object with the version 2.0 Microsoft .NET runtime, resulting in a runtime error that version 3.5 or later of Microsoft's .NET Framework is required when running the latest General_EventLog Knowledge Script. In this release, the supported .NET Framework runtimes was fixed in netiqmc.exe.config to direct the operating system to prefer loading version 4.0 over earlier versions, when such combinations are installed on the same agent computer. (ENG341325)

Preinstall fails on Windows Server 2003 agents in Windows OS version 8.0.80. In version WinOS 8.0, Windows Server 2003 (any edition) was erroneously marked to not pass the WinOS preinstallation checks. In this release, when installing WinOS on a computer running Windows Server 2003 (any edition), the preinstall will now pass. (ENG341135)

General_EventLog fails to monitor some events that the user expects to be matched upon during job execution. Some events on Windows Vista/Windows Server 2008 and later operating systems are stored in the event log with “Level=0” event type, which does not correspond to a known type for monitoring. In this release, event type 0 events are monitored as “Informational” events. (ENG340477)

General_EventLog may return old events on iteration 2 of the job if no events were returned on iteration 1. In this release, on all job iterations after the first iteration, only new events are returned by General_EventLog. (ENG340459)

General_EventLog might raise an AppManager event on matches found in the event log that are older than what is normally reviewed during monitoring, if the job is configured to monitor existing events prior to starting the General_EventLog job and if no events were found on the first job iteration. In this release, the proper range of events are monitored on each job iteration. (ENG341014)

When using the Action_WriteMsgToFile Knowledge Script to write event information to a text file, the number of carriage returns between pieces of information cannot be customized. In this release, a new parameter was added to the Knowledge Script allowing the user to select how many carriage return line feeds to use between event details written to the file. (ENG340336)

Discovery_AMHealth failed on computers in which the nqCommonSQL.dll (a file shipped by WinOS) was not properly registered. This issue only occurs on computers that have .NET 4.0 or higher, but not 2.0 or 3.5. The WinOS installer was changed so that nqCommonSQL.dll gets registered even in absence of .NET 2.0 or 3.5. (ENG339518)

General_EventLog and General_EventLogRx were unable to capture events in custom Windows event logs, and not all filters worked correctly under all circumstances. In this release, General_EventLog and General_EventLogRx were revised to be more scalable, capture events in custom Windows event logs, and monitor Critical event types on newer versions of Windows. (ENG329069, ENG262912, ENG295009, ENG337083, ENG338406)

NT_FileSizeSum was unable to obtain the size of certain types of files, due to the use of an outdated Windows API. The NT_FileSizeSum was re-written in VBScript to utilize more standard APIs for obtaining file sizes. As a result of this change, users must stop their existing NT_FileSizeSum jobs and create new ones. (ENG294590)

NT_FileChanged failed to raise an event when the file timestamp changes by exactly one hour, because we assumed the change was due to a Daylight Savings Time change. The Knowledge Script now raises the correct events for files whose timestamps change. (ENG338926)

NT_DiskSpace does not have separate event severities for 'minimum available disk space' and 'maximum disk utilization'. The Knowledge Script now has separate event severities so users have more flexibility. (ENG339753)

NT_ProcessDown and NT_ProcessUp did not correctly monitor processes with a space in the name. These Knowledge Scripts now correctly monitor processes whose names have spaces in them. (ENG339530)

NT_DiskSpace does not properly exclude drives whose size is less than 100 MB. With this release small drives are now properly excluded. (ENG339648)

NT_CpuLoaded not properly accounting for multi-processor computers, when using virtual performance counters. With this release, the Knowledge Script creates datapoints with the correct values, regardless of how many processors are on the computers. (ENG339105)

NT_FindFiles job was stopping its scan of the target folder, when it encountered a subfolder that cannot be accessed due to limited permissions. In this release, NT_FindFiles notes that the subfolder cannot be scanned, but continues to scan other subfolders. (ENG339105)

Remove use of NT_PhysicalDiskIO from NT_Report_PhysicalDiskIO. The NT_PhysicalDiskIO Knowledge Script was removed from WinOS back in the WinOS 7.6 release. The NT_Report_PhysicalDiskIO Knowledge Script referenced the NT_PhysicalDiskIO Knowledge Script to pull in data and create the output and output folders. In this release, data pulled from the NT_PhysicalDiskStats Knowledge Script and reports appropriately on it. (ENG339799)

Support for Microsoft Windows 10. This module now supports Windows 10. For more information, see the System Requirements.

Upgrade of WinOS from previous version may raise an error message. This release resolves an issue in which upgrading the WinOS module on a computer that does not have .NET Framework 3.0 may result in an error message during the install procedure. With this release, the error popup will no longer occur. (ENG339522)

NT_DiskSpace converted to VBScript. The NT_DiskSpace Knowledge Script was converted to VBScript to revolve several issues. Due to this conversion, stop jobs running the previous version of the NT_DiskSpace Knowledge Script and create new jobs. (ENG325179)

Action_WriteMsgToFile Knowledge Script cannot handle strings longer 32KB. This release resolves an issue in which the Action_WriteMsgToFile Knowledge Script could not handle event detail whose string length exceeded 32 kilobytes. With this release, Action_WriteMsgToFile has been rewritten in VBScript, which allows it to handle events exceeding 32 kilobytes in length. (ENG330413)

General_AsciiLog Knowledge Script raises event when monitored folder doesn't exist . This release resolves an issue in which the General_AsciiLog script raises an event regardless of whether or not the “Raise event if no files are found?” option is selected. With this release, the General_AsciiLog script does not check for the existence of the folder the user is monitoring if the “Raise event if no files are found?” option is not selected. (ENG337852)

AMAdmin_GreyMachine Knowledge script has been removed from AppManager for Microsoft Windows. This release has removed the AMAdmin_GreyMachine Knowledge Script as it will no longer be updated in the product. The AppManager for Self-Monitoring module (AMHealth) now provides the functionality once provided by AMAdmin_GreyMachines. (ENG307063)

General_AsciiLog Knowledge Script job iterations exceed 5 minutes long with 20+ jobs running. This release resolves an issue in which 20 instances of jobs running the General_AsciiLog Knowledge Script cause job iterations to take over 5 minutes to complete. With this release, the General_AsciiLog Knowledge Script has been refactored to run more efficiently when searching files it is monitoring. (ENG336298)

General_AsciiLog Knowledge Script monitors more files than user wants to monitor. This release resolves an issue in which the General_AsciiLog script monitored log files that you did not specify it to monitor. With this release, an update to the script ensures that the script monitors only the logs you specified in the parameters. (ENG336720)

Action_SMTPMail Knowledge Script does not support use of TLS when sending messages. This release introduces the ability to have TLS used when sending SMTP action messages. With this release, a new parameter Transmit message using Transport Layer Security (TLS)? provides this support. (ENG337018)

Action_SMTPMail does not provide the ability to mark the email sent as High Priority. This release adds the ability to add a priority marking to the message sent using a new parameter in the Knowledge Script. (ENG262296)

Action_SMTPMail script does not allow attachments. This release adds the ability to add attachments to the message sent by using the “Attachment Options”. New parameters have been added to the Action_SMTPMail Knowledge Script to specify the path to the attachment and the behavior of the action that should be taken if the attachments are not found. (ENG288692)

NT_FileChanged: BasicScript error on FileDateTime() because of regional settings. This release resolves issues in which an error message was received because of regional settings. With this release the NT_FileChanged was converted to VBScript to resolve the issues. Due to this conversion, stop jobs running the previous version of the NT_FileChanged Knowledge Script and create new jobs. (ENG310771)

NT_ServiceChange: Add service exclude parameter when monitoring all services. This release resolves an issue which allows the exclusion of certain services when monitoring all in the Services parameter. (ENG334013)

Async_NTEventLog Knowledge Script accesses all Microsoft Windows event logs. This release resolves an issue in which the Async_NTEventLog script monitored all event logs instead of just the logs specified by the filter parameters in the script. With this release, the Async_NTEventLog jobs only create event notifications for the Windows event logs you are monitoring, instead of every Windows event log on the agent computer. (ENG277017, ENG333960)

Async_NTEventLog Knowledge Script causes high CPU usage on agent computers. This release resolves an issue in which the Async_NTEventLog script caused high CPU usage on agent computers. With this release, the Async_NTEventLog script does not process unnecessary events raised against event logs that you chose not to monitor. (ENG302001)

Action_NTEventLog Knowledge Script generates incorrect data and causes an “XML is not well-formed” event message. This release resolves an issue in which incorrectly formatted details in the Windows Event Viewer generated by the Action_NTEventLog script prevented the event message from displaying properly. With this release, an update to how the Action_NTEventLog script generates the event log text prevents this issue from occurring. (ENG336466, ENG287120)

Discovery_NT Knowledge Script generates an “XML is not well-formed” event message. This release resolves an issue in which running the Discovery_NT script generated an “XML is not well-formed” event message if you used quotation marks (“”) in the display name for a discovered group policy. With this release, the Discovery_NT script properly handles double-quotes in a display name. (ENG335684)

General_AsciiLog Knowledge Script cannot find a file when using date selection format with the wildcard. This release resolves an issue in which the General_AsciiLog script could not find a file using the Date selection format parameter in conjunction with the % wildcard. With this release, this parameter in the General_AsciiLog script works properly. (ENG337073)

General_MachineDown Knowledge Script unable to read the machine list from the AppManager repository. This release resolves an issue in which the General_MachineDown script could not pull a list of monitored computers from the QDB. In this situation, if you selected a parent management group as the group containing the machines you wanted to monitor, the script did not find any machines for the parent. With this release, the Help for the General_MachineDown script includes a reminder in the Select computers from the repository parameter that you must choose an actual management group with machines in it, not a parent group. (ENG334877)

General_PingMachine Knowledge Script does not generate events on any agent. This release resolves an issue in which the General_PingMachine script stopped raising events on any AppManager agents running Windows operating systems older than Windows 7 or Windows Server 2008 where English is not the language used by the agents. With this release, the General_PingMachine script properly generates events on agents running older operating systems where English is not the default language. (ENG337293)

General_Report_MachineAvailability Knowledge Script file locked and missing data. This release resolves an issue in which a General_Report_MachineAvailability job encountered a run-time error that locked the report, and you could not open the report without restarting the agent. With this release, an update to the script prevents the run-time error from occurring, which enables the General_Report_MachineAvailability report job to complete successfully. (ENG336732)

NT_FindFiles Knowledge Script fails when monitoring files over 2 GB in size. This release resolves an issue in which the NT_FindFiles script failed if you tried to monitor a file path that contains files over 2 GB in size. In addition, the script failed without generating an event message about the problem. With this release, the NT_FindFiles script can monitor files over 2 GB in size. (ENG335953)

NT_RegistryChange Knowledge Script opens a registry key in an exclusion list. This release resolves an issue in which the exclusion option for the NT_RegistryChange script failed to open a particular registry key. The script attempted to list all items in a registry key and then apply exceptions, but the script failed when the NetIQ services were not run as Local System. With this release, the script first bypasses services listed as exceptions before raising an event. (ENG336451)

NT_ServiceDown Knowledge Script generates multiple ambiguous events for a stopped service. This release resolves an issue in which the NT_ServiceDown script generated unclear events for two separate but similar parameters: the Raise event if a service was last stopped normally? parameter and the Raise event if a service is stopped and should not be started? parameter. If you selected Yes for one parameter but not the other, the script generated events when a service stopped normally or when a service stopped abnormally. With this release, the logic for this script was updated to address whether a service stopped normally. Also, the parameter text for Raise event if a service is stopped and should not be started? now reads Raise event if a service stopped abnormally and will not be restarted? (ENG336553)

NT_ServiceDown Knowledge Script starts a stopped Manual service after reboot. This release resolves an issue in which the NT_ServiceDown script restarted Manual services if those services had stopped abnormally. With this release, the NT_ServiceDown script does not restart Manual services after the agent reboots. (ENG337436)

ReportAM_EventSummary Knowledge Script causes the AppManager agent to stop unexpectedly. This release resolves an issue in which the ReportAM_EventSummary script caused the agent to stop unexpectedly when attempting to generate a report. With this release, the script properly generates the report. (ENG335446)

Action_RunPowerShell and PowerShell_RunCommand Knowledge Scripts need updates for better customer experience. This release resolves a series of usability issues with the Action_RunPowerShell and PowerShell_RunCommand scripts. These issues include updating the text of the PowerShell command to run parameter to PowerShell scripts, cmdlets, or code blocks to execute. Also, the AppManager for Microsoft Windows Management Guide includes a new appendix that covers how to use four key PowerShell callback functions. For more information, see the Help for these scripts or the management guide. (ENG334264)

Async_SNMPTrap Knowledge Script causes NetIQ Trap Receiver to disconnect. This release resolves an issue in which the Async_SNMPTrap script caused the Trap Receiver to disconnect, requiring you to restart the Trap Receiver service before traps could be received again. With this release, an update to the trap-receiving components in the AppManager for Microsoft Windows managed object allows the Async_SNMPTrap script to work correctly with the NetIQ Trap Receiver. (ENG334196)

General_EventLog Knowledge Script does not filter event log records properly using the Event user filter parameter. This release resolves an issue in which the General_EventLog script failed to find a record based on the values specified in the Event user filter parameter. With this release, the General_EventLog script raises an event based on the event user filter, and it accepts filters such as SYSTEM or NT AUTHORITY\SYSTEM. (ENG333742)

General_EventLog Knowledge Script fails to properly scan event logs for the previous number of hours requested. This release resolves an issue in which you set the Number of previous hours to scan logs parameter to a specific number of hours, but the job returned logs scanned for a different number of hours. With this release, the job properly uses the value you enter for the Number of previous hours to scan logs parameter. (ENG333287)

NT_FolderSize Knowledge Script cannot access the Windows/system32 folder on 64-bit operating systems. This release resolves an issue where if you used the NT_FolderSize script to scan files or folders in the Windows/System32 folder on a 64-bit computer, you received an event message stating that the folder is missing or you didn't have access to it. With this release, an update to the NT_FolderSize script allows you to access the Windows/system32 folder on 64-bit operating systems. (ENG333722)

NT_MemUtil Knowledge Script generates negative data points when paging files are disabled on the agent computer. This release resolves an issue in which the NT_MemUtil script created -1 data points when paging files were disabled on the agent computer. With this release, the NT_MemUtil script does not try to gather data points from the paging counter if you chose to not monitor paging on that computer. Also, the text of the short event message that displays when the paging counter is not found was updated to Unable to read paging file counters, and the detailed message was updated to Unable to read counter for paging file(s). Please ensure paging files are enabled on the agent computer. (ENG333952)

NT_ServiceChange Knowledge Script stops generating events. This release resolves an issue in which the NT_ServiceChange script did not generate events for changes in start type or status of any service after the first job iteration if you specified an asterisk (*) for the Services to monitor parameter. With this release, specifying an asterisk for the Services to monitor parameter lets you check all services, and the script runs properly as a result. (ENG332289)

NT_ServiceDown Knowledge Script does not allow filtering of services that have an Automatic start type which are not delayed or triggered start. This release allows more granular filtering of services that have an Automatic start type. With this release, you can select Automatic [excludes Delayed and/or Trigger Start] as a start-type filter. This option lets you monitor services that start automatically without a delay or any respective trigger associated with those services. (ENG333919)

ReportAM_EventSummary Knowledge Script fails with a Microsoft OLE DB Provider error. This release resolves an issue in which the ReportAM_EventSummary script generated the following error: Microsoft OLE DB Provider for SQL Server [Line: 251] String or binary data would be truncated. This error occurred when events collected by the report have event detail or comments that exceed 255 characters. With this release, the report can now successfully collect and report on events with over 4000 characters of event detail or comments associated with them. (ENG333579)

General_Asciilog Knowledge Script raises an Out of String Space event message. This release resolves an issue in which the General_Asciilog raised an Out of String Space event message while scanning a log file. The General_AsciiLog and General_AsciiLogRx scripts only return matches in length of 32,000 character or less, and the scripts truncate anything over 32,000 characters. (ENG330939)

General_AsciiLogRX Knowledge Script sometimes rescans the entire log file. This release resolves an issue in which the General_AsciiLogRX script sometimes rescanned the entire file being monitored, resulting in duplicate events for matches that already had events raised for them. With this release, the General_AsciiLogRX script does not rescan the entire log file in this situation. (ENG331297)

General_EventLog Knowledge Script fails to match on some events that were filtered by event ID. This release resolves an issue in which the General_EventLog script did not match on some events specified in the Event ID filter parameter when the length of the event IDs specified exceeded 250 characters. With this release, you can specify event IDs of up to 500 characters in length with this parameter. (ENG330372)

General_MachineDown Knowledge Script does not exclude servers that are in Maintenance Mode. With this release, the General_MachineDown script properly excludes servers that are in Maintenance Mode. (ENG331996)

NT_NetworkBusy Knowledge Script raises events on an unplugged network card. This release resolves an issue in which the NT_NetworkBusy script continued raising events on a network card that was unplugged, and as a result had a bandwidth counter value of zero that triggered the events. With this release, the NT_NetworkBusy script includes a new parameter that lets you ignore network interfaces that have a bandwidth counter value of zero. The text of the new parameter is Ignore network interfaces with no bandwidth counter data?. The default setting for this new parameter is No. (ENG327612)

ReportAM_PlainDataInfo Knowledge Script raises a No Data for Report event message when run against a Web-RT_CheckURL job. This release resolves an issue that occurred when you ran ReportAM_PlainDataInfo script against a Web-RT_CheckURL job to report on the Percent Available parameter, and the script raised a No Data for Report event message. With this release, the ReportAM_PlainDataInfo script reports the percent available data from the Web-RT_CheckURL job as expected. (ENG331755)

Support for Windows 8.1 and Windows Server 2012 R2. This release supports Windows 8.1 and Windows Server 2012 R2 on the agent computers. For more information, see the System Requirements.

AppManager agents running General_EventLog jobs sometimes fail with a fault in the ntdll.dll file. This release resolves an issue in which AppManager agents fail when running General_EventLog jobs, and the Windows Application Event Log indicates a fault in the ntdll.dll file. With this release, an update to the managed object prevents the agents from failing in this situation. (ENG327404)

AMAdmin_AgentConfigMSRestrictions Knowledge Script job clears all data from the AllowMs registry key. This release resolves an issue where if you ran the AMAdmin_AgentConfigMSRestrictions job to restrict communication with a specific management server and your list of management server names in the AllowMS registry key value exceeded 256 characters, the job deleted all entries in the AllowMS registry key value. With this release, the buffer that reads the configuration registry value for the agent's management server can handle up to 3,200 characters. (ENG326092)

Discovery_NT Knowledge Script fails with a “Failed to parse” event message. This release resolves an issue in which the Discovery_NT script failed, generating a “Failed to parse the discovery XML” event message, because the PagingFiles registry value on the selected server was empty. With this release, the Discovery_NT script can successfully discover a server on which this registry value is empty. (ENG328856)

General_AsciiLog Knowledge Script fails if a search string includes an apostrophe ('). With this release, the General_AsciiLog script properly handles search strings that contain apostrophes. (ENG329738)

General_EventLogRX Knowledge Script cannot handle a filter XML file that has Japanese characters. This release resolves an issue in which the General_EventLogRX Knowledge Script could not read an XML file used for filtering if that file contained Japanese characters. With this release, this script can read XML files containing Japanese characters. (ENG322778)

NT_CPULoaded Knowledge Script stops reading VMware utilization counters. This release resolves an issue in which the AppManager agent lost the ability to read the VMware counters, and then, after a service restart, the agent could reacquire the VMware counter values. With this release, the AppManager agent does not lose the ability to read the VMware counters. (ENG327153)

NT_ServiceDown Knowledge Script does not recognize new service start types and generates false alerts. This release resolves an issue in which the NT_ServiceDown script raised false events when you used it to monitor new service types that were added with Windows Server 2008 and Windows 7. These new service types include delayed-start automatic services, trigger-start automatic services, delayed/trigger-start automatic services, and trigger-start manual services. Before this release, if you used one of these new service types and an agent computer was restarted, the script raised a false event stating that the service was down when it was actually in the process of starting. With this release, you can use the Service start-type filter parameter in the NT_ServiceDown script to specify which of these new services you want to monitor, and the script will run without raising false events for these services. (ENG326516)

Support for Microsoft Windows Server 2012 and Windows 8. This release supports Windows Server 2012 and Windows 8 installed on the agent computers. For more information, see the System Requirements.

Discovery_NT Knowledge Script makes optional the discovery of .NET CLR objects. The Discovery_NT script includes a new parameter: Discover .NET Common Language Runtime (CLR) objects? You can use this parameter to disable the discovery of .NET CLR objects to prevent excess events caused by delta discovery, as the list of applications that use the CLR can change quite often. (ENG320201)

Discovery_NT Knowledge Script makes optional the discovery of printers. The Discovery_NT script now only discovers printers on an AppManager agent if you enable the new Discover accessible printers? parameter. Unlike previous releases, the default setting for this parameter is to not discover printers. If you enable this parameter and you have a large number of printers for a single AppManager agent, the discovery process might time out while trying to discover the printers. (ENG280049)

NT_NetworkBusy Knowledge Script allows you to specify a list of network interfaces to exclude from monitoring. The NT_NetworkBusy script includes the following new parameter: Network interfaces to exclude. You can use this parameter to exclude one or more network interfaces that do not have performance data available, or to exclude any network interfaces that you do not want to monitor. (ENG323632)

General_AsciiLog Knowledge Script does not support large text files. This release resolves an issue in which the General_Ascii script could not handle ASCII text files that are greater than 2 GB in size. With this release, you can run this script against ASCII text files that are greater than 2GB (up to 12 GB) in total size, and the script correctly reports all relevant character string matches from those ASCII text files. (ENG285471)

General_AsciiLog Knowledge Script does not support file names with Japanese characters. This release resolves an issue where the General_AsciiLog script failed if you ran it in Japanese locales, and if the file names entered in the File name parameter contained Japanese characters. With this release, the script supports the use of Japanese characters when specifying the file name. (ENG323103)