Run the module installer on the Microsoft Windows computers you want to monitor (agents) to install the agent components, and run the module installer on all console computers to install the Help and console extensions.
Access the AM70-WinOS-8x.x.0.msi module installer from the AM70_WinOS_7.x.x.0 self-extracting installation package on the AppManager Module Upgrades & Trials page.
For Windows environments where User Account Control (UAC) is enabled, install the module using an account with administrative privileges. Use one of the following methods:
Log in to the server using the account named Administrator. Then, run the module installer NT.msi file from a command prompt or by double-clicking it.
Log in to the server as a user with administrative privileges and run the module installer NT.msi file as an administrator from a command prompt. To open a command-prompt window at the administrative level, right-click a command-prompt icon or a Windows menu item and select Run as administrator.
You can install the Knowledge Scripts into local or remote AppManager repositories (QDBs). The module installer installs Knowledge Scripts for each module directly into the QDB instead of installing the scripts in the \AppManager\qdb\kp folder as in previous releases of AppManager.
You can install the module manually, or you can use Control Center to deploy the module on a remote computer where an agent is installed. For more information, see Section 2.3, Deploying the Module with Control Center. However, if you do use Control Center to deploy the module, Control Center only installs the agent components of the module. The module installer installs the QDB and console components as well as the agent components on the agent computer.
NetIQ Corporation recommends that you install the agent using the Local System account.
To install the module manually:
Double-click the module installer .msi file.
Accept the license agreement.
Review the results of the pre-installation check. You can expect one of the following three scenarios:
No AppManager agent is present. In this scenario, the pre-installation check fails, and the installer does not install agent components.
An AppManager agent is present, but some other prerequisite fails. In this scenario, the default is to not install agent components because of one or more missing prerequisites. However, you can override the default by selecting Install agent component locally. A missing application server for this particular module often causes this scenario. For example, installing the AppManager for Microsoft SharePoint module requires the presence of a Microsoft SharePoint server on the selected computer.
All prerequisites are met. In this scenario, the installer will install the agent components.
To install the Knowledge Scripts into the QDB:
Select Install Knowledge Scripts to install the repository components, including the Knowledge Scripts, object types, and SQL stored procedures.
Specify the SQL Server name of the server hosting the QDB, as well as the case-sensitive QDB name.
(Conditional) If you use Control Center 7.x, run the module installer for each QDB attached to Control Center.
(Conditional) 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.
Run the module installer on all console computers to install the Help and console extensions.
Run the module installer on the Windows computers you want to monitor (agents) to install the agent components.
Run the module installer on all management server computers to support Action Knowledge Scripts.
(Conditional) If you want to use NetIQ Trap Receiver to check for SNMP traps, install Trap Receiver by running \AppManager\bin\NetIQTrapReceiver_Setup.exe. For more information, see SNMPTrap.
(Conditional) If you have not discovered Windows resources, run the Discovery_NT Knowledge Script on all agent computers where you installed the module.
(Conditional) If your environment contains virtual server applications on clusters, such as Microsoft SQL Server and Microsoft Exchange, run the Discovery_Cluster Knowledge Script to discover applications on clustered servers and the virtual cluster server.
To get the updates provided in this release, upgrade any running Knowledge Script jobs. For more information, see Section 2.5, Upgrading Knowledge Script Jobs.
After the installation has completed, the WinOS_Install.log file, located in the \NetIQ\Temp\NetIQ_Debug\<ServerName> folder, lists any problems that occurred.
NOTE:To view Reports in ServerGroup, install AppManager Microsoft Windows KS on all AM repositories (QDB) using the Install Knowledge Scripts option. This updates the report pack, which is needed to have the construct to query server groups when configuring ReportAM_KS reports.