Run the module installer only once on any computer. The module installer automatically identifies and updates all relevant AppManager components on a computer.
Access the AM70-SharePoint-7.x.x.0.msi module installer from the AM70_SharePoint_7.x.x.0 self-extracting installation package on the AppManager Module Upgrades & Trials page.
If you are upgrading from version 7.2, uninstall version 7.2 and perform additional steps to install version 7.4 or later correctly. For more information, see Section 2.3.2, Upgrading from Version 7.2 or later versions of the Module.
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 AM70-SharePoint-7.x.x.0.msi from a command prompt or by double-clicking it.
Log in to the server as a user with administrative privileges and run AM70-SharePoint.x.x.0.msi 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). Install these components only once per QDB.
The module installer now 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.11, 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.
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 installs 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, 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 Microsoft SharePoint computers you want to monitor (agents) to install the agent components.
Perform all required post-installation tasks, such as verifying services and enabling logging. For more information, see Section 2.5, Post-installation Considerations.
(Conditional) If you have not discovered Microsoft SharePoint resources, run the Discovery_SharePoint Knowledge Script on all agent computers where you installed the module. For more information, see Section 2.10, Discovering SharePoint Resources.
After the installation has completed, the SharePoint_Install.log file, located in the \NetIQ\Temp\NetIQ_Debug\ServerName folder, lists any problems that occurred.
If you are upgrading from version 7.2 to a more recent version of the module, you need to uninstall version 7.2 and then install the recent version of the module on each SharePoint agent, AppManager repository (QDB), and console.
If you are upgrading from version 7.4 to the recent version of the module, install the recent version on each SharePoint Server agent, AppManager repository (QDB), and console.
Version 7.4 and later versions of the module use PowerShell scripts throughout the module, so you must set the PowerShell execution policy. For more information, see Section 2.6, Configuring the PowerShell Execution Policy.
This section describes the tasks required to upgrade from version 7.2 or later to version 7.4 or later of the module.
To upgrade from version 7.2 or later to recent version:
Stop the ad hoc jobs and remove all SharePoint monitoring policies.
(Conditional) To upgrade from version 7.2 to version 7.4 or later, uninstall version 7.2 of the module from agent computers.
Install the latest version of the module on all AppManager repositories (QDBs), consoles, and agents. For more information about running the installer, see Section 2.3, Installing the Module.
The module installer automatically runs the Discovery Knowledge Script. If it does not, manually run Discovery_SharePoint. For more information about the Discovery Knowledge Script, see Section 2.10, Discovering SharePoint Resources.
Re-create the ad hoc jobs and create new SharePoint monitoring policies.