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.

This release improves usability and resolves previous issues. Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure that our products meet all your needs. You can post feedback in the AppManager forum on NetIQ Communities, our online community that also includes product information, blogs, and links to helpful resources.

The documentation for this product is available on the NetIQ Web site in HTML and PDF formats on a page that does not require you to log in. If you have suggestions for documentation improvements, click comment on this topic at the bottom of any page in the HTML version of the documentation posted at the AppManager Modules page. To download this module, log into the AppManager Module Upgrades & Trials page.

What's New?

This release of AppManager for Microsoft Windows resolves the following issues:

• 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)

To get the updates provided in this release, you must install the module to the repository (QDB) and on the agent computer, and then propagate changes to any running jobs for the Knowledge Scripts that were updated in this release. AppManager 7.x does not automatically update renamed or copied Knowledge Scripts. For more information, see the "Upgrading Knowledge Script Jobs" section in the management guide.

This release of AppManager for Microsoft Windows replaces all Previous Releases.

Return to Top

System Requirements

For the most recently updated list of supported application versions, see the AppManager Supported Products Web site. Unless noted otherwise, this module supports all updates, hotfixes, and service packs for the releases listed below.

AppManager for Microsoft Windows has the following system requirements:

• AppManager version 7.0 or later installed on the AppManager repository (QDB) computer, on all Windows computers you want to monitor (agents), and on all console computers
  Note The following AppManager 7.0 hotfixes are required. For more information, see the AppManager Suite Hotfixes Web site.
  • Control Center hotfix 71781 or later, which is used to display cluster objects in the Servers view
  • Operator Console hotfix 72212 or later, which is used to display cluster objects in the split TreeView pane
  • Repository (QDB) hotfix 72040 or later, for support of cluster virtual server discovery
  • Management server hotfix 72041 or later, for support of cluster virtual server discovery
  • Windows agent hotfix 72616 or later
• One of the following Microsoft operating systems installed on the agent computers:
  • Windows Server 2012 R2
  • Windows Server 2012
  • Windows 8.1 ((32-bit or 64-bit)
  • Windows 8 (32-bit or 64-bit)
  • Windows 7 (32-bit or 64-bit)
  • Windows Server 2008 R2, including the Intel Itanium (IA64) architecture
  • Windows Server 2008 (32-bit or 64-bit), including the Intel Itanium (IA64) architecture
  • Windows Vista (32-bit or 64-bit)
  • Windows Server 2003 R2 (32-bit or 64-bit), including the Intel Itanium (IA64) architecture
  • Windows XP (with Service Pack 3 or later for 32-bit, or with Service Pack 2 or later for 64-bit)
  • Windows 2000 Server with Service Pack 4 or later
• Microsoft Windows PowerShell 1.0 or later installed on the agent computers where you want to execute PowerShell commands
• Microsoft .NET Framework 3.0 or later installed on the agent computers where you want to execute PowerShell commands
  Note Support for Windows PowerShell requires Windows Communication Foundation (WCF), which enables communication between client and server, and is a component of .NET Framework 3.0. You cannot use the PowerShell-related Knowledge Scripts if .NET Framework 3.0 is not installed.

For more information, see the AppManager for Microsoft Windows Management Guide, included in the download package.

Return to Top

Contents of the Download Package

AppManager for Microsoft Windows includes a managed object and Knowledge Scripts to discover and monitor Microsoft Windows resources. The download package includes this release notes file, a management guide, Help for Knowledge Scripts, and several files that are used during installation:

• AM70-WinOS-7.8.130.0.msi, the module installer.
• AM70-WinOS-7.8.130.0.ini, a configuration file used with the AppManager setup program.
• AM70-WinOS-7.8.130.0.xml, a configuration file used for deploying the module with Control Center. This is the file you check into the Control Center Web Depot.
• AM70-WinOS-7.8.130.0-RepositoryFiles.exe, a compressed file that contains the QDB and console files. You do not need to run this file during installation.
• DefaultRule_WinOS.xml, a configuration file used for deploying the module with Control Center.
• ckNT.exe, the pre-installation check used with the AppManager installer.

When you download the module, these files are copied by default to the local folder on the download computer. Consider copying these files to the \windows_installation\setup\Setup Files folder on the same distribution computer on which you saved your main AppManager software and documentation. By doing so, you maintain all AppManager software in one location that is easily accessible when you want to add more repositories, management servers, or agents.

Return to Top

Installing This Module

Run the module installer to install the module components in the following locations:

• On the Windows computers you want to monitor (agents) to install the agent components
• On the agent that resides on the management server computer to support Action Knowledge Scripts
• On all console computers to install the Help and console extensions

Run the module installer only once on each of these computers.

You must also install the Knowledge Scripts. You can install these module components to either local or remote QDBs. When installing to each QDB, select the option to install Knowledge Scripts, and then specify the SQL Server name of the server hosting the QDB, as well as the case-sensitive QDB name.

Important This release provides SQL stored procedures. To ensure module functionality, run the module installer for each QDB attached to Control Center.

Install Knowledge Scripts only once per QDB. The module installer now installs Knowledge Scripts for each module directly into the QDB instead of to the \AppManager\qdb\kp folder as in previous releases.

For more information about installing this module, see the AppManager for Microsoft Windows Management Guide, included in the download package.

Return to Top

Known Issues

NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Technical Support.

• General_AsciiLog and General_AsciiLogRx jobs that are currently running cannot be propagated with this release. Because of a change in the language used by these Knowledge Scripts, you need to stop any running General_AsciiLog and General_AsciiLogRx jobs, or any jobs started from copies of these Knowledge Scripts. After installing this module and stopping the running jobs, create new General_AsciiLog and General_AsciiLogRx jobs. If you try to propagate the new versions of these scripts to existing jobs that are running, you might experience runtime errors. (ENG315667)
• Remote deployment fails on Windows 8, Windows 8.1, Windows Server 2012, and Windows Server 2012 R2 computers with versions of AppManager prior to 8.2. When you remotely deploy this module to a computer running Windows 8, Windows 8.1, Windows Server 2012, or Windows Server 2012 R2, AppManager displays the following error: Unknown operating system detected for machine IPAddress. To work around this issue on these computers that are running versions of AppManager prior to 8.2, install this module manually. If you are using AppManager 8.0.1, you can address this issue by installing Control Center hotfix 7011602. For more information, see the AppManager Suite Hotfixes Web site. (ENG319069, ENG327586)
• On Windows Server 2012 and Windows 8 agent computers, the Discovery_NT Knowledge Script does not discover group policy objects if the AppManager agent services are running under a Domain account. If you run the AppManager agent services under a Domain account on a Windows Server 2012 or a Windows 8 agent computer, the Discovery_NT script does not discover group policy objects. As a workaround, run the AppManager agent services under a Local System account on agent computers running Windows Server 2012 and Windows 8. (ENG318735)
• Action_SMTPMail Knowledge Script changes must be propagated after upgrading to this release of the AppManager for Microsoft Windows module. If existing jobs are running a version of Action_SMTPMail that is older than version 7.6.276, propagate the scripts after upgrading to this latest version of the module. If the changes to the Action_SMTPMail script are not propagated, the job fails with an Invalid Callee error. For more information, see Knowledge Base article 7773101. (ENG311566, DOC311836, DOC316177)
• NT_DiskSpace Knowledge Script cannot monitor network drives when run on the cluster alias object. When the NT_DiskSpace script runs on the cluster alias object, it cannot monitor network drives because the script works against the shared drives only. Monitoring network drives with the NT_DiskSpace script is possible from physical computers, but not from the cluster alias object. (DOC300611)
• The Performance Data Helper (PDH) component fails on non-English computers. To use PDH on computers localized for German or Spanish, the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\CurrentLanguage registry key must contain the localized Object\Counter names. To prevent PDH from failing, add the localized Object\Counter names to the registry key. (DOC304118)
• Action_RebootSystem Knowledge Script includes a parameter that does not work properly. The Force applications with unsaved changes to be closed? parameter does not work. Enabling this parameter does not properly close applications. (ENG238407)
• Action_SMTPMail truncates messages. The Action_SMTPMail Knowledge Script truncates event messages that contain more than 128 lines or are greater than 128K in size. (ENG284072)
• AMAdmin_ConfigAdminEvents Knowledge Script events have invalid severity levels in AppManager 7.x. If you are using AppManager 7.x and you set the severity level for the Event severity when Knowledge Script failures applied to registry parameter to an invalid number (outside the range of 1-40), events are raised with the invalid severity level. Events should retain the default value of 10. This issue was resolved in AppManager 8.0.1. (ENG277193)
• AMAdmin_ConfigAdminEvents Knowledge Script runs more often than scheduled in AppManager 7.x. If you are using AppManager 7.x and the NetIQ AppManager Client Communication Manager (NetIQCCM) service is in maintenance mode, the AMAdmin_ConfigAdminEvents Knowledge Script job keeps running, even if the schedule is set to "Run Once." This issue was resolved in AppManager 8.0.1. (ENG275707)
• Async_SNMPTrap Knowledge Script does not raise events for traps with non-standard varbind characters. The Async_SNMPTrap Knowledge Script does not raise events for SNMP traps with varbinds that contain non-standard characters such as "%." (ENG286199)
• Some event sources do not have associated message files. For General_EventLog, General_EventLogRx, and General_MissingEvent Knowledge Script jobs running on Windows Server 2008 and later, some event sources might not have a message file identified. Without this identification, AppManager cannot return the full description field of a Windows event. One example of this issue is the LoadPerf event source, which does not have an EventMessageFile registry entry. (ENG262912)
• Server reboot dialog box title misleading. The dialog box that informs you of a server reboot is titled You are about to be logged off. (ENG238414)

Return to Top

Previous Releases

This release of AppManager for Microsoft Windows includes enhancements added in previous releases.

Release 7.8.94.0, December 2013

This release of AppManager for Microsoft Windows resolved the following issues:

• 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)

This release also includes the following support:

• 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.

Release 7.8.72.0, August 2013

This release of AppManager for Microsoft Windows resolved the following issues:

• 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)

Release 7.8.60.0, February 2013

This release of AppManager for Microsoft Windows added the following support:

• 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.

This release included the following enhancements:

• 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)

This release also resolved the following issues:

• 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)

Release 7.7.69.0, August 2012

This release of AppManager for Microsoft Windows resolved the following issues:

• Action_SMTPMail Knowledge Script sends an email with a blank body if you select a custom message option but do not define the custom subject. This release resolves an issue in which the Action_SMTPMail Knowledge Script sent an email with no content in its body when you specified text or keywords for the Custom message body parameter, but you left the Custom message subject parameter blank. With this release, an update to the logic of the script allows Action_SMTPMail to send a complete email with a custom message body even if you do not specify the custom message subject text. (ENG317525)
• NT_FileSizeSum Knowledge Script fails to generate an event when the sum of the monitored files exceeds the threshold. This release resolves an issue in which the NT_FileSizeSum script did not generate an event when you set the Sum size threshold parameter to a value higher than 2 GB, and the combined file size of both monitored files exceeded 2 GB. With this release, the script generates an event if this threshold is crossed, regardless of the combined file size. (ENG320981)

Release 7.7.62.0, May 2012

This release of AppManager for Microsoft Windows resolved the following issues:

• Action_SMTPMail Knowledge Script sometimes sends an empty email if more than one SMTP action is configured. This release resolves an issue where the Action_SMTPMail script sometimes sent a blank email if you configured more than one SMTP action with the script. (ENG310426)
• Action_SMTPMailRpt Knowledge Script email contains a broken link for the footer image. This release resolves an issue in which the Action_SMTPMailRpt script did not properly display graphics with a shared file path if the shared file path used a different case from the path specified in the script. With this release, the Action_SMTPMailRpt script locates the shared file path regardless of the case of the path. (ENG222834)
• Action_SNMPTrap Knowledge Script provides insufficient information about objects in the event message. This release resolves an issue in which the Action_SNMPTrap script sometimes incorrectly labeled the object information in a trap, or the results of the trap did not contain enough specific information about the object. With this release, the object that was evented on for the trap is correctly identified by the Action_SNMPTrap script. (ENG270777)
• Action_StopServices Knowledge Script writes an inconsistent message when a service has stopped. This release resolves an issue in which the Action_StopServices job generated an event stating that the action completed with errors whenever the Action_StopServices job stopped at least one service successfully. With this release, the error message no longer displays when the job stops a service. (ENG197654)
• Action_UpdateEventStatus Knowledge Script event filtering is not working. This release resolves an issue in which the Action_UpdateEventStatus script did not properly acknowledge events when you listed two or more Knowledge Scripts for the Filter by these Knowledge Scripts parameter. With this release, the Action_UpdateEventStatus script works properly on Knowledge Scripts for which you want to filter events. (ENG312227)
• AMAdmin_GreyMachines Knowledge Script leaves temporary XML files when a threshold is exceeded. This release resolves an issue in which the AMAdmin_GreyMachines script generated XML files in the /temp folder that were not deleted after you ran the script and the Maximum number of agents that are not responding parameter exceeded the threshold. With this release, the temporary XML files are properly deleted. (ENG310363)
• Async_FilesChanged Knowledge Script does not monitor files in the \Windows\System32 folder. This release resolves an issue in which the Async_FilesChanged Knowledge Script did not properly monitor changes to files located in the \Windows\System32 folder, as specified by the File path parameter. (ENG312382)
• Async_NTEventLog Knowledge Script cannot find logs. This release resolves an issue in which the Async_NTEventLog script generated the following error when trying to locate and monitor event logs: These event logs do not exist: System. With this release, the Async_NTEventLog script is able to locate and monitor the specified event logs. (ENG313688)
• Async_NTEventLog Knowledge Script causes NetIQmc to stop unexpectedly on the Domain Controller. This release resolves an issue in which the Async_NTEventLog script caused the Client Resource Monitor service (NetIQmc.exe) to stop unexpectedly on the Domain Controller. With this release, a change to the code of the script prevents the agents on the Domain Controller from crashing. (ENG303908)
• Discovery_NT Knowledge Script does not discover shared disks and clustered drives on a virtual host. This release resolves an issue in which after discovery, a two-node cluster displayed shared disks under the physical nodes rather than the virtual node. This release also resolves an issue in which running the Discovery_NT Knowledge Script on the virtual node created by the Discovery_Cluster Knowledge Script discovered only part of the clustered drives. With this release, you can now identify primary cluster nodes by nodes that own a physical disk type and a file share type, and not just a network name resource type that is a core resource. As a result, you can discover shared disks and clustered drives on nodes that may not own the cluster name or other core objects. (ENG301007, ENG299912)
• General_AsciiLog Knowledge Script causes a Microsoft VBScript runtime error. This release resolves an issue that occurred when you used invalid wildcards for the File name parameter in the General_AsciiLog script, which generated the following error event message: Microsoft VBScript runtime error [Line: 1241] Unexpected quantifier. With this release, the script generates a relevant event if you use wildcards that are not valid in the file name. (ENG316023)
• General_AsciiLog Knowledge Script causes high CPU and memory usage over time. This release resolves an issue in which monitoring a large number of log files caused high CPU and memory usage over time. (ENG291317)
• General_AsciiLog Knowledge Script sometimes removes the last character in the event message. This release resolves an issue in which the General_AsciiLog inadvertently removed the last character in the event message, which gave inaccurate search results when the search criteria included the missing character. With this release, the last character of the event message is no longer removed, making the search results accurate. (ENG308696)
• General_EventLog and General_EventLogRx Knowledge Scripts are unable to monitor reboots. This release resolves an issue in which the General_EventLog and the General_EventLogRx scripts did not accurately read all event log entries if the job was stopped and restarted, or if the agent was stopped. With this release, an update to the General_EventLog and General_EventLogRx scripts enable them to correctly monitor all events generated during server reboots. (ENG285041, ENG289432)
• General_EventLog Knowledge Script shows incorrect event description. This release resolves an issue in which the General_EventLog job did not translate the system error code in the description of the event record into the event message. With this release, the event log descriptions display properly on the event message for the General_EventLog job. (ENG312484)
• General_MachineDown Knowledge Script does not notify you if there are no longer any objects to check. This release resolves an issue in which the General_MachineDown script did not notify you if you deleted all the objects from a view that you were using for this script. With this release, the following event message displays in this situation: No computers were found while querying the AppManager repository with the parameters selected. (ENG264374)
• General_MachineDown Knowledge Script failed to compile a complete list of machines. This release resolves an issue in which the General_MachineDown script failed to list all machines after the script was restarted. With this release, this script compiles the list of machines if you run the script on multiple computers, or if you open the script to make parameter changes and then run it on a machine. (ENG278977)
• General_MachineDown Knowledge Script generates inaccurate events about ping failures. This release resolves an issue in which the General_MachineDown script generated events indicating ping failures or timeouts for active servers. This release prevents ping failures and timeouts from occurring for active servers with the General_MachineDown script. (ENG301479)
• General_PingMachine Knowledge Script does not collect data for the PingMachine_RespTime legend in Analysis Center. This release resolves an issue in which the General_PingMachine script did not properly gather data for the PingMachine_RespTime legend in Analysis Center. With this release, the General_PingMachine script generates response time data correctly for reports and charts in Analysis Center. (ENG307706)
• NTAdmin_RestartService Knowledge Script does not properly restart a service that has a specified delay. This release resolves an issue in which the NTAdmin_RestartService script did not restart a service that had a long delay set in the script parameters. For example, if you set the Service start/stop delay parameter to 900 seconds, the script restarted the service after only 90 seconds, not 900 seconds. With this release, an update to the code of this script allows the script to restart a service that has a long delay. (ENG277026)
• NT_FilesCompare Knowledge Script cannot find files to compare on 64-bit computers. This release resolves an issue that occurred when you ran the NT_FilesCompare script to compare files in the \Windows\System32\Config folder on a 64-bit computer, resulting in a File not found event message because the files were incorrectly redirected. With this release, the script successfully locates files on 64-bit computers. (ENG289289)
• NT_DiskSpace Knowledge Script does not display the mount point object under the NT virtual object. This release resolves an issue in which the NT_DiskSpace script detected all shared drives but did not show the mount point under the NT virtual object. With this release, the mount point object displays properly under the NT virtual object. (ENG311407)
• NT_DiskSpace Knowledge Script does not exclude mount points when an asterisk is used. This release resolves an issue in which mount points were not excluded if you used an asterisk (*) as a wildcard in the Drives to exclude parameter for the NT_DiskSpace script. With this release, using the asterisk as a wildcard in the parameter properly excludes the specified mount points. (ENG311086)
• NT_DiskSpace Knowledge Script does not monitor mount points with special characters in their names. This release resolves an issue in which you could not monitor mount points that had special characters in their names, such as an ampersand (&) or a hyphen (-). With this release, you can monitor mount points with those characters in their names, such as the following paths: C:\test\path&one or C:\test\file-1. (ENG281445)
• NT_DiskSpace Knowledge Script generates an event when a threshold is crossed on a cluster that contains resources without drive letters. This release resolves an issue in which the NT_DiskSpace script incorrectly generated events when a disk space threshold was crossed on a cluster that had resources without drive letters. With this release, the script no longer generates inaccurate threshold events in this situation. (ENG314282)
• NT_MemByProcess Knowledge Script stops when a monitored process quits or fails. This release resolves an issue in which you set the NT_MemByProcess Knowledge Script to monitor specific processes, but the job stopped when one or more of those processes quit or failed. With this release, NT_MemByProcess jobs do not stop if the monitored processes quit or fail. (ENG295750)
• NT_MemUtil Knowledge Script fails with a faulting application error. This release resolves an issue in which the NT_MemUtil script failed if you ran it on a virtual machine that was upgraded from Windows 2000 Server to Windows Server 2003. The event message stated the following: Faulting application NetIQmc.exe, version 7.0.25020.0, faulting module rpcrt4.dll, version 5.2.3790.0, fault address 0x000370d0. With this release, an update to the script prevents the error from occurring. (ENG307696)
• NT_ServiceDownLR Knowledge Script does not raise an event if the NT_ConfigServiceDown Knowledge Script was not run first. This release resolves an issue in which the NT_ServiceDownLR script did not generate an event if you did not first run the NT_ConfigServiceDown script. With this release, the NT_ServiceDownLR script generates an event to remind you to first run the NT_ConfigServiceDown script. (ENG306407)
• NT_SystemUptime Knowledge Script fails to specify the monitored object when generating an event. This release resolves an issue in which the NT_SystemUptime script did not correctly identify the object being monitored when events were generated. (ENG307663)
• PowerShell_RunCommand Knowledge Script remains in a running state on non-English operating systems. This release resolves an issue in which the PowerShell_RunCommand script continued running on a non-English system because the name of the Administrators group was not properly identified on the non-English system, which led to an error. With this release, a change in the way the script determines the name of the Administrators group prevents the error from occurring. (ENG306565)
• ReportAM_SystemUpTime Knowledge Script incorrectly calculates uptime and downtime. This release resolves an issue in which the ReportAM_SystemUpTime script used the gap between the last collected system uptime counter and the beginning of scheduled maintenance for that system, and then it calculated that gap as downtime. With this release, the ReportAM_SystemUpTime report script always considers the time between the last collected system uptime and the beginning of scheduled maintenance as uptime. (ENG300186)
• Variable type mismatch causes a property or method not found error. This release resolves an issue in which the following error message displayed on some agent machines: RErr423(L1639):Property or method not found. This issue affects the following Knowledge Scripts: Async_NTEventLog, General_AsciiLog, NT_DiskSpace, NT_LogicalDiskStats, NT_MemByProcess, and NT_ServiceDownLR. With this release, a change to the variable types prevents the error from occurring in these scripts. (ENG304433)

This release of AppManager for Microsoft Windows included the following enhancements:

• Action_SMTPMail Knowledge Script includes improved spacing and formatting commands to ensure messages display properly. This release includes enhancements to the way in which carriage-return line feeds are handled in SMTP mail messages, as well as improvements to the way in which short and detailed messages display specific text. Also, the script no longer counts control characters as a word when the control characters are present in between words. (ENG314627)
• Action_SNMPTrap Knowledge Script includes a new port parameter. The new Destination port parameter lets you specify the number of the port where you want the trap sent. (ENG294258)
• Action_WriteMsgToFile Knowledge Script now accepts line feeds and carriage returns in custom messages. You can now include carriage returns and line feeds to better format the custom messages you create with the Action_WriteMsgToFile script. (ENG300884)
• AMAdmin_ConfigAdminEvents Knowledge Script allows you to edit event severity for "Fail to Fetch Job Request" events. (ENG210212)
• AMAdmin_GreyMachines Knowledge Script includes option to raise an event for each greyed-out machine added. A new parameter for the AMAdmin_GreyMachines script, Raise individual events for agents that are not responding, enables you to generate an individual event for each unresponsive (or "greyed-out") machine in the TreeView. (ENG257335)
• AMAdmin_SetPrimaryMS Knowledge Script includes a new event severity parameter. Using the new parameter, you can specify the severity of the event if the registration of the management server fails. (ENG294999)
• Async_NTEventLog Knowledge Script includes ability to filter unclassified events. The Async_NTEventLog script lets you filter entries that are considered unclassified, such as "Success (none)." These entries do not match the error, warning, information, success audit, or failure audit filter criteria. (ENG300087)
• Async_SNMPTrap Knowledge Script contains exclude and include filter options. Filters for the Async_SNMPTrap script can contain criteria used to include entries, exclude entries, or both. Separate the include and exclude criteria with a colon (:). If you specify only include criteria, the colon is not necessary. (ENG303345)
• General_Counter Knowledge Script includes new parameters for when a counter equals a specific value. You can now raise an event when a counter equals a specific value. The script also includes new parameters that allow you to set the event severity and the value to match for this situation. (ENG280510)
• General_EventLog and General_EventLogRx Knowledge Scripts include new log availability parameters. New parameters were added to these two scripts that allow you to raise or suppress an event when the log file cannot be read or reached. (ENG254781)
• General_EventLog Knowledge Script now allows spaces between the list of event logs to monitor. This release allows you to include spaces between multiple entries in the comma-separated list of logs in the Event logs to monitor parameter on the General_EventLog script. (ENG286822)
• General_PingMachine Knowledge Script includes updated event message and data detail. The General_PingMachine script now includes additional output gathered by the ping command, which is displayed in the data detail for the response time datastream. (ENG286465)
• NT_DiskSpace Knowledge Script includes two new parameters. The first parameter is Do not raise events if disk growth thresholds are crossed, and you can use this parameter if you do not want to raise events when the disk growth exceeds a default value. The second parameter, Only raise events when both disk space and disk utilization thresholds are crossed, limits the number of events by requiring both thresholds are crossed before raising an event. (ENG293984, ENG283194)
• NT_ProcessUp Knowledge Script now contains a new default value of No for the Kill the running process? parameter. If you are using AppManager 8.x or later, this change will not get picked up due to the default Knowledge Script merge functionality. As a result, you will need to manually review this parameter when configuring NT_ProcessUp jobs. (ENG307522)
• NT_ProcessUp Knowledge Script tab delimiter now includes additional special characters . The NT_ProcessUp script can now handle a tilde (~), hyphen (-), and an underscore (_) when monitoring specific process names. (ENG204137)

Release 7.6.276.0, April 2011

This release of AppManager for Microsoft Windows resolved the following issues:

• The NQPerfProvider4 process ends unexpectedly when running some AMPP Knowledge Scripts. This release resolves an issue in which the latest version of the NQPerfProvider4.exe service failed unexpectedly on a computer running Windows Server 2008 and with some AppManager Performance Profiler (AMPP) environments. With this release, changes to the module prevent the access violation that caused the NQPerfProvider4.exe service to crash. (ENG306975)
• Gathering data from performance counters might cause long delays in running jobs. This release resolves an issue in which data collection not only caused delays, but the data collection process sometimes had missing data or gaps in data. With this release, an update to the process that gathers data from performance counters prevents the long delays and other data collection problems you may have previously experienced. (ENG296282)
• The Action_ExtendedSNMPTrap Knowledge Script generates a different set of events on each iteration. This release resolves an issue in which running the Action_ExtendedSNMPTrap script on an agent or a proxy agent resulted in an undefined value in the Event ID, Repository Name, and Repository Server fields. With this release, the Action_ExtendedSNMPTrap script automatically completes those three fields with the word unknown or unavailable where needed, instead of leaving them undefined. As a result, the Action_ExtendedSNMPTrap script generates events as expected. (ENG301536)
• You cannot monitor the available disk space of a network drive. This release resolves an issue in which the NT_LogicalDiskSpace script, which let you monitor the available disk space of a network drive, was no longer available. With this release, you can now use the NT_DiskSpace Knowledge Script to monitor the disk space for network drives and other types of shared drives. (ENG294465)
• The Async_NTEventLog Knowledge Script causes the Client Resource Monitor service to stop unexpectedly. This release resolves an issue in which running the Async_NTEventLog Knowledge Script unexpectedly caused the Client Resource Monitor service (NetIQmc.exe) to stop because of a low buffer size setting in the event logs. With this release, a change to the code prevents the NetIQmc.exe from crashing because of the size of the event log. (ENG286900)
• Running the Discovery_Cluster Knowledge Script creates invalid objects. This release resolves an issue in which new physical nodes appeared with the wrong fully qualified domain name (FQDN) when you ran the Discovery_Cluster script. With this release, an update to the code in the Discovery_Cluster Knowledge Script enables the script to retrieve the proper DNS name, preventing the creation of any invalid objects. (ENG294064)
• The remote deployment process generates an error about failing to register a file. This release resolves an issue in which a Failed to register file error message displayed during remote deployment. This release includes the relevant files needed for a successful remote deployment. (ENG298769)
• Running the AMAdmin_AgentHealth Knowledge Script generates an error event. This release resolves an issue in which the AMAdmin_AgentHealth script generated the following error message: WaitForObject error: 6. (ENG300494)
• Some NT Knowledge Script jobs fail, leaving gaps in the chart console. This release resolves an issue in which NT Knowledge Script jobs, including NT_MemUtil and NT_SystemUptime jobs, failed with the following error message: Can’t find System UptimeCounter. With this release, the NT Knowledge Script jobs do not fail, and the chart console does not contain any gaps in data. (ENG302580)
• When you set up two or more SMTP actions with the Action_SMTPMail Knowledge Script, an empty email might be sent with the second action. This release resolves an issue in which if you set up two or more separate SMTP actions with the Action_SMTPMail Knowledge Script and the script generated an event, the Action_SMTPMail script sent emails for each action, but sometimes one of the emails was blank instead of including the relevant text in the body of the email. With this release, all emails that result from events for the Action_SMTPMail Knowledge Script contain the expected data, with no blank emails sent. (ENG300322)
• The word count for a custom message created with the Action_SMTPMail Knowledge Script ignores line feeds and tabs. This release resolves an issue in which the word count for a custom message created with the Action_SMTPMail Knowledge Script only counted spaces at the end of words, and ignored carriage-return line feeds and tabs at the end of a word. With this release, Action_SMTPMail correctly calculates word count. (ENG295735)
• An action triggered by an Action_SMTPMail Knowledge Script job does not send the SMTP email containing the event information. This release resolves an issue in which an action triggered by an Action_SMTPMail Knowledge Script job stated that a local action is in progress, but the email with the event information did not get sent. With this release, the Action_SMTPMail script successfully sends the SMTP email for the event. (ENG300487)
• Jobs that make calls to the Remote Registry service can cause a handle leak on Windows Server 2008 agents. This release resolves an issue in which any servers running jobs that required a Remote Registry call to gather data or to perform monitoring sometimes caused a handle leak for the SVCHost.exe -k regsvc process. With this release, the handle leak does not occur on Windows Server 2008 agents. (ENG297772)
• Jobs take much longer to execute than expected. This release resolves an issue in which jobs seemed to take much longer to execute than expected, and at times the jobs did not execute at all. (ENG297991)
• The NQPerfProvider4.exe process consumes an excessive amount of resources. With this release, the NQPerfProvider4.exe service no longer consumes such a large amount of resources, and the agent is much more responsive as a result. (ENG301659, ENG304016)
• Charts do not display properly in emails generated by the Action_SMTPMailRpt Knowledge Script. This release resolves an issue in which an email generated by the Action_SMTPMailRpt script did not properly display charts in the emails generated by the script. With this release, the charts in the emails from the Action_SMTPMailRpt script display as expected. (ENG303980)
• A type mismatch error occurs when you change the language preferences. This release resolves an issue in which a type mismatch error occurred if you changed the language preferences to a language that uses a comma instead of a period for the decimal placeholder. This situation occurred with the NT_TopCPUProcs Knowledge Script. With this release, the type mismatch error no longer occurs with the NT_TopCPUProcs script. (ENG302497)

This release of AppManager for Microsoft Windows included the following enhancements:

• The NT_DiskSpace Knowledge Script allows regular expressions in the Drives to exclude parameter. This release allows you to add regular expressions to the Drives to exclude parameter of the NT_DiskSpace Knowledge Script. (ENG295678)
• The English name-index search is case-sensitive. This release allows you to perform a case-sensitive search through the counter name-index map to get the translated Object\Counter names on non-English, localized computers. (ENG304173)

Release 7.6.209.0, September 2010

This release resolved the following issues:

• Scripts return zero values. This release resolves an issue where some Knowledge Scripts report data values of zero when the associated performance counters are not zero. (ENG296148, ENG295848, ENG297056)
• Error incorrectly reported when no data is available. This release resolves an issue where the General_MachineDown Knowledge Script reports an error when the Knowledge Script creates and opens a record set that does not contain data. (ENG293966)
• NetIQmc service stops on Windows 2000 Server SP4. This release resolves an issue on agent computers running Windows 2000 Server SP4 where the NetIQmc service stops when the Discovery_NT Knowledge Script tries to discover an SNMP service. (ENG296066)
• Overrides not applied to the "per disk threshold" parameters. This release resolves an issue where the DiskSpace Knowledge Script Overrides does not apply overrides to Per Disk Threshold parameters. (ENG296072)

This release provided the following enhancement:

• Filter by enterprise and sub-tree. The Async_SnmpTrap Knowledge Script now allows you to limit the reported events to a specific enterprise or MIB sub-tree. (ENG291894)

Release 7.6.194.0, August 2010

This release resolved the following issues:

• Action scripts parse event text incorrectly. This release resolves an issue in which two Knowledge Scripts, Action_SNMPTrap and Action_WriteMsgToFile, incorrectly parse event message fields when the $DetailMsg$ keyword is used. The scripts incorrectly parse the blank spaces between components (or tokens) of the event text string. With this release, a code change allows each script to correctly parse blank spaces and tokens, and to write the correct string of an event detail message into a text file. (ENG286396)
• EventLog scripts rescan event logs during each iteration. This release resolves an issue in which the General_EventLog and General_EventLogRx Knowledge Scripts rescan old entries in the Windows event logs when the Previous hours to scan parameter is set to 0. The problem occurs when the record number in the event logs exceeds 32,000. With this release, a code change corrects the behavior of the Knowledge Scripts and prohibits the scripts from scanning log entries not specified by the Previous hours to scan parameter. (ENG287524)
• AsciiLog scripts scan entire log during each iteration. This release resolves an issue in which duplicate events are raised because the General_AsciiLog and General_AsciiLogRx Knowledge Scripts scan the entire log each time the scripts run if the jobs are unable to store a unique identifier of the file's size. With this release, a code change corrects the behavior of the Knowledge Scripts. (ENG288165)
• General_MachineDown job fails to read list of computers. This release resolves an issue in which the General_MachineDown Knowledge Script job does not monitor the computers specified in an external text file. Attempts to read the text file generate the following error message, Failed to compile list, because the filehandle used to open the text file is not closed between job iterations. With this release, a code change allows filehandles to be closed between jobs, enabling the script to read external text files. (ENG289090)
• Installing version 7.6.170.0 does not update NQPerfProvider. This release resolves an issue in which installation of version 7.6.170.0 of the module fails to update NQPerfProvider processes. Installation continues successfully and does not indicate a failure to update the processes. With this release, the installation process stops all instances of the NQPerfProvider process before updating the NQPerfProvider4.exe executable file. (ENG291821)
• AMAdmin_LRReadParameters job fails if parameter contains an asterisk. This release resolves an issue in which the AMAdmin_LRReadParameters Knowledge Script job fails if an asterisk (*) is specified in parameters in the General_AsciiLog Knowledge Script. The failure raises an event with the following message: Failed to load XML format details. With this release, a code change allows the LRReadParameters job to correctly interpret the asterisk and to successfully load XML format details. (ENG291893)
• NQPerfProvider never stops. This release resolves an issue in which the NQPerfProvider process never stops, even when not in use, causing excessive handle and memory usage. With this release, a code change forces all instances of the NQPerfProvider process to stop when not in use. (ENG292495, ENG293073)
• Security Manager upgrade fails if NQPerfProvider is running. This release resolves an issue in which an upgrade of NetIQ Security Manager fails because it cannot update performance counters. With this release, a code change in this module forces all instances of the NQPerfProvider process to stop when not actively querying Performance Monitor. (ENG292759)
• ReportAM_Inventory job fails for SQL Server. This release resolves an issue in which the ReportAM_Inventory Knowledge Script job fails when attempting to report on the SQL Server application. The job fails with the following error: 1280437618 [5068] onScriptError: Microsoft OLE DB Provider for SQL Server [Line: 603] Invalid column name 'Nam'. With this release, a code change in a stored procedure corrects the problem. (ENG293849)

Release 7.6.170.0, May 2010

This release provided the following enhancements:

• Discovery and management of the virtual server cluster alias. The Discovery_Cluster Knowledge Script now discovers the virtual server cluster alias and allows you to manage virtual servers as you would physical servers. Events and data collection are tied to the virtual server object, and cluster failover has no negative impact on events and data collection.
• Support for new and updated operating systems. This release provides support for monitoring Microsoft Windows 7 and Microsoft Windows Server 2008 R2.
• Events for missing event log entries. The new General_MissingEvent Knowledge Script raises an event when a Windows event log does not contain an expected log entry.
• Support for Windows PowerShell. Two new Knowledge Scripts provide support for Microsoft Windows PowerShell: PowerShell_RunCommand and Action_RunPowerShell. These new scripts run any command you can run from PowerShell, such as PowerShell cmdlets, PowerShell scripts, or any command that can be run from a PowerShell command prompt.
• Collection of ICMP response-time data. The improved General_PingMachine Knowledge Script now collects average ICMP response-time data for every computer the script monitors.
• Greater control over agent and Management Server registry settings. The new AMAdmin_ConfigAdminEvents Knowledge Script automatically updates the registry with severity settings for AppManager agent and Management Service events. Before the introduction of this script, updating the registry with severity settings was a manual process. The script raises events when severity settings are applied to the registry and when the Management Service is not installed. For more information, see the Help for AMAdmin_ConfigAdminEvents.
• Support for NetIQ SNMP Trap Receiver. The revised Async_SNMPTrap Knowledge Script checks for SNMP traps (versions 1, 2, and 3) forwarded from NetIQ SNMP Trap Receiver. Trap Receiver can forward incoming traps to AppManager or a second destination IP address and port. Trap Receiver also includes different levels of logging, including trace and debug messages. For more information, see the Help for Async_SNMPTrap.
  Note Trap Receiver is not automatically installed when you install the AppManager for Microsoft Windows module. You can install Trap Receiver manually by running NetIQTrapReceiver_setup.exe, which you can find in the \AppManager\bin folder.
• Consolidated monitoring of logical disk space statistics. For all logical disks on a server and all shared drives in a cluster, the new NT_DiskSpace Knowledge Script monitors percentage of disk space used, the amount of free space in megabytes, and the percentage of disk growth between iterations. The script also allows the monitoring of mount points, and can raise events based on global or per-disk thresholds. It replaces NT_LogicalDiskSpace and NT_DynamicLogicalDiskSpace, which are now obsolete.
• Consolidated monitoring of logical disk statistics. The new NT_LogicalDiskStats Knowledge Script combines the functionality of the NT_LogicalDiskIO and NT_LogicalDiskBusy Knowledge Scripts, which are now obsolete. For more information, see the Help for NT_LogicalDiskStats.
• Consolidated monitoring of physical disk statistics. The new NT_PhysicalDiskStats Knowledge Script combines the functionality of the NT_PhysicalDiskIO, NT_PhysicalDiskQLen, and NT_PhysicalDiskBusy Knowledge Scripts, which are now obsolete.
• Measurement of virtual machine processor and memory data. The NT_CpuLoaded and NT_MemUtil Knowledge Scripts now monitor virtual CPU and memory performance counters when available. The scripts enable monitoring of either physical or virtual performance data, providing greater control over the accuracy of collected data. For more information, see the Help for each Knowledge Script.
• Improvements to Action_SMTPMail. The enhanced Action_SMTPMail Knowledge Script pings the SMTP server before attempting to send e-mail to specified recipients. In addition, the script now allows you to include special characters in a custom message. These characters insert whitespace, line feeds, and carriage returns. For more information, see the Help for Action_SMTPMail.
• Improved counter instance identification in General_Counter. The General_Counter Knowledge Script now allows you to use the asterisk (*) wildcard in instance name definitions to monitor all instances of the same counter name. For more information, see the Help for General_Counter.
• Improved process identification in NT_ProcessDown. The NT_ProcessDown Knowledge Script now allows you to use the asterisk (*) wildcard in process name definitions to identify processes that might include PIDs (process IDs) and to identify sub-processes with the same or similar names. For more information, see the Help for NT_ProcessDown.

Knowledge Scripts available in previous releases of the module are no longer available:

• Action_WMIEvent
• AMAdmin_AddManagedObject
• AMAdmin_AddManagedObjectProxy
• AMAdmin_AgentInstall
• AMAdmin_AgentInstallProxy
• AMAdmin_AgentUpdate
• AMAdmin_AgentUpdateProxy
• AMAdmin_AppManagerUninstall
• AMAdmin_AppManagerUninstallProxy
• AMAdmin_MaintenanceInstall
• AMAdmin_UnixAgentInstallProxy
• Discovery_Proxy
• General_LogicalDiskSpace
• NT_ConfigLogicalDisks
• NT_DynamicLogicalDiskSpace
• NT_LogicalDiskIO
• NT_LogicalDiskIOLR
• NT_LogicalDiskBusy
• NT_LogicalDiskSpace
• NT_LogicalDiskSpaceLR
• NT_PhysicalDiskIO
• NT_PhysicalDiskBusy
• NT_PhysicalDiskQLen
• All StartPoint Knowledge Scripts

However, if you are already using these obsolete scripts, you can continue to use them.

Release 7.5.208.0, August 2009

This release resolved the following issues:

• NT_DynamicLogicalDiskSpace Knowledge Script job does not run. Before you install this release, the NT_DynamicLogicalDiskSpace Knowledge Script job fails to load the WScript.Shell interface and returns the following error: NT_DynamicLogicalDiskSpace not running. Error null line : 1130 null. After you install this release, a version upgrade in the code used to create the script allows it to run successfully. (ENG265527)
• Async_NTEventLogRX Knowledge Script job causes memory leak. Before you install this release, the Async_NTEventLogRX Knowledge Script job causes a memory leak in the NetIQ Client Resource Monitor (NetIQmc) service. The leak is caused by open handles created, but not deleted, with each job iteration, resulting in Event logs that exceed the size recommended by Microsoft. After you install this release, a change in the script's code allows for the proper deletion of handles, which prevents Event logs from exceeding recommended limits, as well as the resulting memory leak. (ENG266368)
• NT_SystemUpTime fails with counter error. Before you install this release, the NT_SystemUpTime Knowledge Script job fails to find the systemuptime Performance Monitor counter. After you install this release, a change in the script's code allows it to find and monitor the systemuptime perfmon counter. (ENG266844)
• Action_SNMPTrap Knowledge Script job ignores community string input. Before you install this release, the Action_SNMPTrap Knowledge Script job outputs "public" as the SNMP community string, regardless of the community string you configured in the script's parameters. After you install this release, a change in the script's code allows it to recognize the community string you configured in the script's parameters. (ENG268513)
• NT_DynamicLogicalDisk Knowledge Script job fails on a B: drive. Before you install this release, the NT_DynamicLogicalDisk Knowledge Script recognizes only drives c: through z:. After you install this release, a change in the script's code allows it to recognize drives a: through z:. (ENG269565)

Release 7.5.198.0, June 2009

This release resolved the following issues:

• Cluster shared disks are not discovered. Before you install this release, shared disks for a cluster are not discovered when you run the Discovery_NT Knowledge Script. After you install this release, the following new parameter in the Discovery_NT Knowledge Script allows you to discover shared physical and logical disks for a cluster and display them in the Operator Console TreeView pane. (ENG264273)
  • Discover cluster disks? Set this parameter to "y" to discover all shared physical and logical disks for a cluster.
• Action_DosCommand incorrectly writes event message to text file. Before you install this release, the Action_DosCommand Knowledge Script, when launched by the Async_NTEventLogRX Knowledge Script, writes event messages incorrectly. For example, if you instruct the Action_DosCommand Knowledge Script to run echo $DetailMessage$[8*] > C:\Temp\log.txt, you expect the command to write the event detail message (a text string) into the log.txt file, starting from the eighth word in the message. However, the Action_DosCommand Knowledge Script writes the event detail message into the log file starting from the fourth word in the message because it incorrectly parses the blank spaces between components (or tokens) of the text string. After you install this release, a change in the code for the Action_DosCommand Knowledge Script allows it to correctly parse blank spaces and tokens, and to write the correct string of an event detail message into a text file. (ENG267531)

Hotfix 71458, March 2009

This release resolved the following issues:

• E-mail from Action script prints one line of message per page. Before you install this release, when you print e-mail sent from the Action_SMTPMail Knowledge Script, each line of the error message is printed on a separate page. Microsoft Outlook reads the "tabs" in the message detail as "page breaks." After you install this release, a change in the code for this Knowledge Script allows the entire error message to be printed on one page. (ENG232872)
• Discovery_NT Knowledge Script job may never stop running on 64-bit Windows Server 2003. Before you install this release, the Discovery job may never stop running, causing the Discovery job to appear to hang on 64-bit Microsoft Windows Server 2003. After you install this release, a change in the way the Discovery job accesses the registry allows the Discovery job to finish successfully and prevents the agent from running out of memory. (ENG253773)
• General_AsciiLog jobs run too long. Before you install this release, a General_AsciiLog Knowledge Script job runs longer than anticipated when monitoring a set of files whose filenames change regularly. The Data Dictionary table, which contains context information such as the last line read for each file, grows larger with each Knowledge Script job, causing each subsequent job to take longer to complete. After you install this release, the Data Dictionary table is purged of values that were not monitored during a job iteration. With a smaller Data Dictionary table to monitor, General_AsciiLog Knowledge Script jobs do not run so long as to overlap each other. (ENG259245)
• Windows2000_DFSLink does not monitor multiple DFS roots. Before you install this release, the Windows2000_DFSLink Knowledge Script does not monitor Distributed File System (DFS) roots that are hosted on multiple servers. When you run the Knowledge Script job on a DFS configured with several roots, the job returns data for only one of the roots. After you install this release, the Windows2000_DFSLink Knowledge Script job successfully returns data for all roots configured for a DFS. (ENG259325)
• Module continually tries to deploy after it is already installed. Before you install this release, the AppManager for Windows module cannot verify that the package is already installed and continually creates tasks for deployment. The problem exists in version 7.5 and in two subsequent hotfixes: 71360 and 71271. After you install this release, the module correctly determines that the package is installed and creates only one deployment task. (ENG260323)

Hotfix 71360, January 2009

This release resolved the following issues:

• Discovery_NT Knowledge Script job fails. Before you install this release, the Discovery_NT Knowledge Script jobs fails without indicating an error. After you install this release, a change in the script's code from BasicScript to VBScript prevents the script from failing without indicating an error. (ENG246907)
• Action_SNMPTrap Knowledge Script does not recognize double quotation marks. Before you install this release, if double quotation marks ("") are found in an event detail message, Action_SNMPTrap sends an invalid message to NetIQSnmpTrap.exe and no trap is sent. After you install this release, double quotation marks are delimited with a backslash, so that Action_SNMPTrap correctly interprets the double quotes and sends a valid command to NetIQSnmpTrap.exe. (ENG254604)
• Action_SendReportToPrinter prints only first page of report. Before you install this release, the Action_SendReportToPrinter Knowledge Script prints only the first page of a report (default.htm). After you install this release, the script prints every page in the report. (ENG255611)
• Insufficient character limit for Action_SMTPMail. Before you install this release, the Subject and Body parameters are limited to 160 characters each. After you install this release, the Subject parameter has a limit of 500 characters and the Body parameter has a limit of 1000 characters. (ENG255740)
• General_SnmpGet Knowledge Script does not work on 64-bit Microsoft Windows Server 2008. Before you install this release, General_SnmpGet Knowledge Script jobs running on 64-bit Windows Server 2008 raise the following event: "SNMP not functional. Failed to get OID=system.sysUpTime.0: errcode = 40." After you install this release, a corrected snmputil.dll allows General_SnmpGet to function properly on 64-bit Windows Server 2008. (ENG257798)
• NT_DynamicLogicalDiskSpace Knowledge Script does not monitor mount points. Before you install this release, the NT_DynamicLogicalDiskSpace Knowledge Script does not enumerate or monitor mount points (mapped drives) even if their objects appear in the TreeView pane of the Operator Console. After you install this release, an enhancement to the script allows it to recognize and monitor mount points. (ENG258287)
• NT_Servicedown Knowledge Script fails when no service matches criteria. Before you install this release, the NT_ServiceDown Knowledge Script job fails when it returns a value of 0 (zero) for the number of services found, meaning that no services matched the criteria you specified. After you install this release, the job does not fail when it returns 0 (zero) for the number of services found. (ENG258346)

Hotfix 71271, December 2008

This release resolved the following issues:

• The Discovery_NT Knowledge Script fails to properly associate logical disks to physical disks. Before you install this release, the Discovery_NT Knowledge Script sometimes fails to properly associate logical disks to physical disks. After you install this release, the knowledge script always associates each physical disk with the appropriate logical disk. (ENG247995)
• When the AppManager agent computer is in maintenance mode, the agent allows events to be raised. Before you install this release, when an AppManager agent computer is in maintenance mode, the agent allows the NT_SystemUpTime job to raise an event if the system is down. After you install this release, when you reboot an AppManager agent computer in maintenance mode, the agent does not allow events to be raised. (ENG234468)
• The General_AsciiLog Knowledge Script returns an error message when lines exceed 255 characters. Before you install this release, the General_AsciiLog Knowledge Script fails to properly parse log files and returns an Out of string space error message when lines exceed 255 characters. After you install this release, the General_AsciiLog Knowledge Script does not fail. (ENG255305)
• The NT_CpuLoaded Knowledge Script fails when it attempts to retrieve CPU performance data. Before you install this release, after upgrading to AppManager for Microsoft Windows 7.5.82.0, the NT_CpuLoaded Knowledge Script is unable to retrieve CPU performance data. After you install this release, the Knowledge Script no longer fails while attempting to retrieve the CPU performance data. (ENG255506)
• The General_AsciiLog Knowledge Script passes the parameter by reference instead of by value. Before you install this release, in function AdjustForDateSelection, the date mask is overwritten with the current date, which is not updated in subsequent iterations. After you install this release, the Knowledge Script passes the parameter by value, which is updated in subsequent iterations. (ENG253555)
• The NT_CpuByProcess Knowledge Script reports high CPU utilization on a dual processor computer. Before you install this release, the NT_CpuByProcess Knowledge Script reports high CPU utilization on a dual processor computer. After installing this release, the Knowledge Script properly reports CPU utilization on a dual processor computer. (ENG253843)
• The NT_CpuResource Knowledge Script fails. Before installing this release, after upgrading to AppManager for Microsoft Windows 7.5.82.0, the NT_CpuResource Knowledge Script fails, showing the error, RErr410(L101) failed on CPU MO. After installing this release, the Knowledge Script does not fail. (ENG255030)
• Message tab blank in event properties for General_AsciiLog Knowledge Script. Before you install this release, when you run the General_AsciiLog Knowledge Script, the Message tab in Event Properties is blank. After you install this release, when you run the Knowledge Script, the Message tab in Event Properties displays the proper information. (ENG256376 and ENG256377)
• The WIN2000_DFSLinkDown Knowledge Script does not run on Windows 2003 SP1 or SP2. Before you install this version, an error in the Win2000_DDFSLinkDown Knowledge Script prevents the Knowledge Script from running on Windows 2003 or Windows 2008 with a service pack installed. After installing this version, the Knowledge Script runs on Windows 2003 and Windows 2008 with a service pack installed. (ENG255600)

Release 7.5, September 2008

This release provided the following enhancements:

• Support for Internet Protocol version 6 (IPv6). AppManager for Microsoft Windows recognizes and displays IPv6 addresses in the Operator Console and Control Center Console.
• Support for 64-bit Windows Server 2003. This release adds support for monitoring 64-bit Windows Server 2003, SP2.
• The installation process for the AppManager for Microsoft Windows module is independent of the installation of the AppManager agent. For more information, see the "Installing AppManager for Microsoft Windows" chapter of the AppManager for Microsoft Windows Management Guide, included in the module's download package.
• The EventLog Knowledge Script includes a new parameter to let you raise an event when the EventLog job cannot access or read the Windows Event log. (ENG247922)

Return to Top

Third-Party Software

NetIQ AppManager® for Microsoft Windows, as well as any and all adapters, modules, updates, modifications thereto (“Software”) is distributed with certain Third Party Software and Open Source Software (as may be defined in the license agreement between you and NetIQ).

The following Third Party and Open Source Software are included with the Software and are licensed for distribution according to the terms described in this document and any use thereof must be in accordance with such terms, solely in conjunction with your use internal use of the Software, and – unless explicitly contradicted below - consistent with the terms and conditions set forth in the applicable license agreement for the software. No further licenses are granted.

• Microsoft SNMP Management API for Windows NT
  Microsoft Windows Media Technologies. Copyright © 1999-2005 Microsoft Corporation. All Rights Reserved.
• MDAC, VisualStudio C++ Runtime, © Microsoft Corporation
• Microsoft ATL (Active Template Library) © Microsoft Corporation
  Licensed under the Microsoft Limited Permissive License (Ms-LPL)
  This license governs use of the accompanying software. If you use the software, you accept this license. If you do not accept the license, do not use the software.
  1. Definitions
     The terms “reproduce,” “reproduction,” “derivative works,” and “distribution” have the same meaning here as under U.S. copyright law.
     A “contribution” is the original software, or any additions or changes to the software.
     A “contributor” is any person that distributes its contribution under this license. “Licensed patents” are a contributor’s patent claims that read directly on its contribution.
  2. Grant of Rights
     (A) Copyright Grant- Subject to the terms of this license, including the license conditions and limitations in section 3, each contributor grants you a non-exclusive, worldwide, royalty-free copyright license to reproduce its contribution, prepare derivative works of its contribution, and distribute its contribution or any derivative works that you create.
     (B) Patent Grant- Subject to the terms of this license, including the license conditions and limitations in section 3, each contributor grants you a non-exclusive, worldwide, royalty-free license under its licensed patents to make, have made, use, sell, offer for sale, import, and/or otherwise dispose of its contribution in the software or derivative works of the contribution in the software.
  3. Conditions and Limitations
     (A) No Trademark License- This license does not grant you rights to use any contributors’ name, logo, or trademarks.
     (B) If you bring a patent claim against any contributor over patents that you claim are infringed by the software, your patent license from such contributor to the software ends automatically.
     © If you distribute any portion of the software, you must retain all copyright, patent, trademark, and attribution notices that are present in the software.
     (D) If you distribute any portion of the software in source code form, you may do so only under this license by including a complete copy of this license with your distribution. If you distribute any portion of the software in compiled or object code form, you may only do so under a license that complies with this license.
     (E) The software is licensed “as-is.” You bear the risk of using it. The contributors give no express warranties, guarantees or conditions. You may have additional consumer rights under your local laws which this license cannot change. To the extent permitted under your local laws, the contributors exclude the implied warranties of merchantability, fitness for a particular purpose and non-infringement.
     (F) Platform Limitation- The licenses granted in sections 2(A) & 2(B) extend only to the software or derivative works that you create that run on a Microsoft Windows operating system product.
• WFC (The Win32 Foundation Classes) Copyright, 2000, Samuel R. Blackburn
  Author: Samuel R. Blackburn
  Internet: wfc@pobox.com
  You can use it any way you like as long as you don't try to sell it.
  Any attempt to sell WFC in source code form must have the permission of the original author. You can produce commercial executables with WFC but you can't sell WFC.
• UUCODE. Copyright © 1983, 1993 The Regents of the University of California. All rights reserved.
  Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
  
  
  1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
  3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by the University of California, Berkeley and its contributors.
  4. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
  THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
• RegExp. Copyright © 1986, 1993, 1995 by University of Toronto. Written by Henry Spencer. Not derived from licensed software.
  Permission is granted to anyone to use this software for any purpose on any computer system, and to redistribute it in any way, subject to the following restrictions:
  1. The author is not responsible for the consequences of use of this software, no matter how awful, even if they arise from defects in it.
  2. The origin of this software must not be misrepresented, either by explicit claim or by omission.
  3. Altered versions must be plainly marked as such, and must not be misrepresented (by explicit claim or omission) as being the original software.
  4. This notice must not be removed or altered.
• Xerces. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
• Net-SNMP. Various copyrights apply to this package, listed in various separate parts below. Please make sure that you read all the parts. Up until 2001, the project was based at UC Davis, and the first part covers all code written during this time. From 2001 onwards, the project has been based at SourceForge, and Networks Associates Technology, Inc hold the copyright on behalf of the wider Net-SNMP community, covering all derivative work done since then. An additional copyright section has been added as Part 3 below also under a BSD license for the work contributed by Cambridge Broadband Ltd. to the project since 2001. An additional copyright section has been added as Part 4 below also under a BSD license for the work contributed by Sun Microsystems, Inc. to the project since 2003.
  Code has been contributed to this project by many people over the years it has been in development, and a full list of contributors can be found in the README file under the THANKS section.
  • ---- Part 1: CMU/UCD copyright notice: (BSD like) -----
    Copyright 1989, 1991, 1992 by Carnegie Mellon University
    Derivative Work - 1996, 1998-2000
    Copyright 1996, 1998-2000 The Regents of the University of California
    All Rights Reserved
    Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of CMU and The Regents of the University of California not be used in advertising or publicity pertaining to distribution of the software without specific written permission.
    CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL CMU OR THE REGENTS OF THE UNIVERSITY OF CALIFORNIA BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
  • ---- Part 2: Networks Associates Technology, Inc copyright notice (BSD) -----
    Copyright © 2001-2003, Networks Associates Technology, Inc
    All rights reserved.
    Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
    • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
    • Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
    • Neither the name of the Networks Associates Technology, Inc nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
    THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  • ---- Part 3: Cambridge Broadband Ltd. copyright notice (BSD) -----
    Portions of this code are Copyright © 2001-2003, Cambridge Broadband Ltd.
    All rights reserved.
    Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
    • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
    • Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
    • The name of Cambridge Broadband Ltd. may not be used to endorse or promote products derived from this software without specific prior written permission.
    THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  • ---- Part 4: Sun Microsystems, Inc. copyright notice (BSD) -----
    Copyright © 2003 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved.
    Use is subject to license terms below.
    This distribution may include materials developed by third parties.
    Sun, Sun Microsystems, the Sun logo and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.
    Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
    • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
    • Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
    • Neither the name of the Sun Microsystems, Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
    THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  • ---- Part 5: Sparta, Inc copyright notice (BSD) -----
    Copyright © 2003-2006, Sparta, Inc
    All rights reserved.
    Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
    • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
    • Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
    • Neither the name of Sparta, Inc nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
    THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  • ---- Part 6: Cisco/BUPTNIC copyright notice (BSD) -----
    Copyright © 2004, Cisco, Inc and Information Network Center of Beijing University of Posts and Telecommunications.
    All rights reserved.
    Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
    • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
    • Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
    • Neither the name of Cisco, Inc, Beijing University of Posts and Telecommunications, nor the names of their contributors may be used to endorse or promote products derived from this software without specific prior written permission.
    THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  • ---- Part 7: Fabasoft R&D Software GmbH & Co KG copyright notice (BSD) -----
    Copyright © Fabasoft R&D Software GmbH & Co KG, 2003
    oss@fabasoft.com
    Author: Bernhard Penz
    Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
    • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
    • Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
    • The name of Fabasoft R&D Software GmbH & Co KG or any of its subsidiaries, brand or product names may not be used to endorse or promote products derived from this software without specific prior written permission.
    THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
• OpenSSL License. The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.
  Copyright © 1998-2006 The OpenSSL Project. All rights reserved.
  Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
  1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
  3. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)."
  4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org.
  5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.
  6. Redistributions of any form whatsoever must retain the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)."
  THIS SOFTWARE IS PROVIDED BY THE OPENSSL PROJECT "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OPENSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
  This product includes software written by Tim Hudson (tjh@cryptsoft.com).
• SSLeay License. Copyright © 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.
  This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).
  The implementation was written so as to conform with Netscape's SSL. This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).
  Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.
  Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
  1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
  3. All advertising materials mentioning features or use of this software must display the following acknowledgement: "This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). The word 'cryptographic' can be left out if the routines from the library being used are not cryptographic related :-)."
  4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft.com)."
  THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license (including the GNU Public License).

Last Modified March, 2010
AppManager for Microsoft Windows 7.6

Return to Top

Contact Information

Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you.

For detailed contact information, see the Support Contact Information page.

For general corporate and product information, see the NetIQ Corporate Web site.

For interactive conversations with your peers and NetIQ experts, become an active member of our community. The NetIQ online community provides product information, useful links to helpful resources, blogs, and social media channels.

Return to Top

Legal Notice

THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FURNISHED UNDER AND ARE SUBJECT TO THE TERMS OF A LICENSE AGREEMENT OR A NON-DISCLOSURE AGREEMENT. EXCEPT AS EXPRESSLY SET FORTH IN SUCH LICENSE AGREEMENT OR NON-DISCLOSURE AGREEMENT, NETIQ CORPORATION PROVIDES THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT ALLOW DISCLAIMERS OF EXPRESS OR IMPLIED WARRANTIES IN CERTAIN TRANSACTIONS; THEREFORE, THIS STATEMENT MAY NOT APPLY TO YOU.

For purposes of clarity, any module, adapter or other similar material ("Module") is licensed under the terms and conditions of the End User License Agreement for the applicable version of the NetIQ product or software to which it relates or interoperates with, and by accessing, copying or using a Module you agree to be bound by such terms. If you do not agree to the terms of the End User License Agreement you are not authorized to use, access or copy a Module and you must destroy all copies of the Module and contact NetIQ for further instructions.

This document and the software described in this document may not be lent, sold, or given away without the prior written permission of NetIQ Corporation, except as otherwise permitted by law. Except as expressly set forth in such license agreement or non-disclosure agreement, no part of this document or the software described in this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, or otherwise, without the prior written consent of NetIQ Corporation. Some companies, names, and data in this document are used for illustration purposes and may not represent real companies, individuals, or data.

This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. NetIQ Corporation may make improvements in or changes to the software described in this document at any time.

U.S. Government Restricted Rights: If the software and documentation are being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), in accordance with 48 C.F.R. 227.7202-4 (for Department of Defense (DOD) acquisitions) and 48 C.F.R. 2.101 and 12.212 (for non-DOD acquisitions), the government's rights in the software and documentation, including its rights to use, modify, reproduce, release, perform, display or disclose the software or documentation, will be subject in all respects to the commercial license rights and restrictions provided in the license agreement.

© 2014 NetIQ Corporation. All Rights Reserved.

For information about NetIQ trademarks, see http://www.netiq.com/company/legal/.

Return to Top