AppManager for Microsoft Active Directory optimizes Microsoft Active Directory performance and ensures availability through automated event detection and correction. These advances help you to lower support costs associated with managing Microsoft Active Directory deployment. The module ensures that critical information pertaining to user accounts is available to network users and administrators.
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 website in HTML and PDF formats on a page that does not require you to log in. If you have suggestions for documentation improvements, click AppManager Modules page. To download this product, see the AppManager Module Upgrades & Trials website.to the right of each section of any page in the HTML version of the documentation posted at the
This release of AppManager for Microsoft Active Directory provides the following enhancement:
Support for Windows Server 2019: This release now supports computers running Microsoft Windows Server 2019. For more information, see the System Requirements.
To get the updates provided in this release, you must install the module to the AppManager 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 Active Directory replaces all Previous Releases.
For the most recently updated list of supported application versions, see the AppManager Supported Products page. Unless noted otherwise, this module supports all updates, hotfixes, and service packs for the releases listed below.
AppManager for Microsoft Active Directory has the following system requirements:
NetIQ AppManager installed on the AppManager repository (QDB) computers, on the Active Directory computers you want to monitor (agents), and on all console computers
8.0.3, 8.2, 9.1, 9.2, 9.5, or later
One of the following AppManager agents are required:
Microsoft Windows operating system on the agent computers
One of the following:
AppManager for Microsoft Windows module installed on the AppManager repository (QDB) computer, on the Active Directory computers you want to monitor (agents), and on all console computers
Support for Windows Server 2008 R2 on AppManager 7.x requires the AppManager for Windows module, version 18.104.22.168 or later. For more information, see the AppManager Module Upgrades & Trials Web page.
Microsoft SQL Server Native Client 11.0
(for TLS 1.2 support)
11.3.6538.0 or later
NOTE:The SQL Server Native client can be installed from this Microsoft download link.
For more information on hardware requirements and supported operating systems and browsers, see the AppManager for Microsoft Active Directory Management Guide, included in the download package.
NOTE:If you want TLS 1.2 support and are running AppManager 9.1 or 9.2, then you are required to perform some additional steps. To know about the steps, see the article.
AppManager for Microsoft Active Directory includes a managed object, qactivedsa4.dll, and Knowledge Scripts to discover and monitor AppManager for Microsoft Active Directory resources. The download package includes this release notes, a management guide, Help for Knowledge Scripts, and several files that are used during installation:
AM70-AD-22.214.171.124.msi the module installer.
AM70-AD-126.96.36.199.ini, a configuration file used with the AppManager setup program.
AM70-AD-188.8.131.52.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-AD-184.108.40.206-RepositoryFiles.exe, a compressed file that contains the QDB and console files. You do not need to run this file during installation.
ckAD.exe, the pre-installation check used with the AppManager setup program.
DefaultRule_AD.xml, a configuration file used for deploying the module with Control Center.
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.
Run the module installer to install the module components in the following locations:
On the Active Directory computers you want to monitor (agents) to install the agent components
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 components into local or remote QDBs. When installing to the primary 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:If you use Control Center 7.x, run the module installer for each QDB attached to Control Center. If you use Control Center 8.x or later, run the module installer only for the primary QDB, and Control Center will automatically replicate this module to secondary QDBs.
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 Active Directory Management Guide, included in the download package.
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.
Remote deployment fails on Microsoft Windows Server 2012 computers. When you remotely deploy this module to a computer running Windows Server 2012, AppManager displays the following error: Unknown operating system detected for machine IPAddress. To work around this issue, install this module manually. (ENG319069)
Some Knowledge Scripts do not work properly for read-only domain controllers (RODCs). The following Knowledge Scripts incorrectly categorize RODCs as bridgehead servers and either do not raise events when they should or do not retrieve correct data for RODCs:
Reports viewed in IE6 may contain incomplete data. When viewed in Internet Explorer version 6, some fields for the following reports may be empty:
The fields in the reports are populated properly when viewed in Internet Explorer version 7 or later.
ServerHealth Knowledge Script performance affected. The Microsoft WMI replication provider, ReplProv, affects the ability of the ServerHealth Knowledge Script to monitor replication health. To resolve the issue, apply Windows Server 2003 Service Pack 1 or the ReplProv hotfix from Microsoft. To obtain the hotfix, contact Microsoft technical support.
Updated Action_SMTPMailRpt Action Knowledge Script required for use with ReportADSI reports. To use the Action_SMTPMailRpt Action Knowledge Script with the ReportADSI reports after you install this update, you will need an updated version. To obtain the update, contact Technical Support.
ReplicationLatency report object change requires re-discovery of Report Agent. To use the ReportADSI_ReplicationLatency report after installation of this update, you must run the Discovery_ReportAgent Knowledge Script to re-discover the AppManager repository on all Report Agent computers where you want to run the ReplicationLatency report.
CacheHitRatio Knowledge Script removed from the Recommended Knowledge Script Groups. Because of inconsistent reliability of the DS Name Cache hit rate NTDS counter, the CacheHitRatio Knowledge Script was removed from the RECOMMENDED AD and RECOMMENDED AD (all DCs) Knowledge Script Groups. This Knowledge Script is still available in the AD Knowledge Script category but is not recommended for monitoring Windows Server 2003 Domain Controllers.
Default settings not applied at check-in. The default settings for Advanced Properties are not applied to Knowledge Scripts within a Knowledge Script Group when you perform Knowledge Script check-in. This issue affects the Active Directory RECOMMENDED Knowledge Script Groups.
Some Knowledge Scripts fail when using McAfee VirusScan Enterprise 8.0i or later. If you are using McAfee VirusScan Enterprise 8.0i or later with the Script Scanner feature enabled, several of the Active Directory Knowledge Scripts might be blocked and fail to run properly. As a result, you might see irrelevant events. To prevent the blocking, disable the Script Scanner feature of VSE8i. Contact McAfee technical support if you need assistance disabling the Script Scanner feature.
ReplicationLatency Knowledge Script fails when the DNS hostname of the domain controller exceeds 64 characters. The ReplicationLatency Knowledge Script does not support a domain controller acting as an Injector if the fully qualified DNS hostname of the domain controller exceeds 64 characters. Before running this script, ensure the DNS hostname does not exceed 64 characters.
This release of AppManager for Microsoft Active Directory includes enhancements added in previous releases.
This release of AppManager for Microsoft Active Directory provides the following enhancements:
Support for Transport Layer Security 1.2 (TLS): This release of AppManager for Microsoft Active Directory provides support for TLS 1.2.
This release of AppManager for Microsoft Active Directory resolves the following issue:
Discovery_ActiveDS causes Windows agents to stop unexpectedly: An agent crash occurs when discovery is run on an agent computer (Discovery_ActiveDS KS). This release of AppManager for Microsoft Active Directory resolves this issue. (ENG340319)
This release provided the following enhancement:
This release of AppManager for Microsoft Active Directory supports Windows Server 2016.
This release provided the following enhancement:
Support for Windows Server 2012 and Windows Server 2008 R2. This release now supports computers running Microsoft Windows Server 2012 and Microsoft Windows Server 2008 R2. For more information, see the System Requirements.
This release provided the following enhancements:
Support for Microsoft Windows Server 2008. All of the services and Performance Counters that this module supports for Windows Server 2003 are supported for Windows Server 2008. No new functionality has been added.
Improvement to GlobalCatalogHealth script. The Site list parameter now allows lists of up to 4096 characters. In previous releases, this parameter allowed only 256 characters. (ENG239251)
Changes to event behavior in DCInSiteConnectivity script. The event behavior for this script now raises an event if the event condition occurs once within one job iteration, which is the default behavior for events. In previous releases, this script raised an event if the event condition occurred twice within two job iterations. The corrected behavior allows this script to function properly with the job delegation feature of the module. (ENG244430)
Removal of MSDN URLs for path, class, property, and schema information. Previous releases of this module provided parameters that allowed you to specify the MSDN (Microsoft Developer Network) URL for path, class, property, and link information that would be displayed in the results of three Report Knowledge Scripts. Because new MSDN URLs no longer contain path, class, property, and link information, the parameters have been removed from the following scripts. (ENG245626)
Support for IPv6. This release adds support for Internet Protocol version 6 (IPv6). AppManager for Microsoft Active Directory recognizes and displays IPv6 addresses in the Operator Console and Control Center Console.
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 website.
For general corporate and product information, see the NetIQ Corporate website.
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.
For information about NetIQ legal notices, trademarks, disclaimers, warranties, export and other use restrictions, U.S. Government restricted rights, patent policy, and FIPS compliance, see https://www.netiq.com/company/legal/.
Copyright (C) 2019 NetIQ Corporation. All rights reserved.