2.2 Installing the Module

Run the module installer on the Exchange servers 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-Exchange2007-7.x.x.0.msi module installer from the AM70-Exchange2007-7.x.x.0 self-extracting installation package on the AppManager Module Upgrades & Trials page.

If you are upgrading from the previous version of this module, version 7.5, you need to perform additional steps to install version 7.6 correctly. For more information, see Section 2.2.2, Upgrading 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 the module installer .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 .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 and the Analysis Center reports 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.

2.2.1 Manually Installing the Module

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 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:

  1. Double-click the module installer .msi file.

  2. Accept the license agreement.

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

  4. To install the Knowledge Scripts into the QDB and to install the Analysis Center reports into the Analysis Center Configuration Database:

    1. Select Install Knowledge Scripts to install the repository components.

    2. Select Install report package to install the Analysis Center reports.

    3. Specify the SQL Server name of the server hosting the QDB, as well as the case-sensitive QDB name.

    4. Specify the SQL Server name of the server hosting the Analysis Center Configuration Database.

  5. (Conditional) If you use Control Center 7.x, run the module installer for each QDB attached to Control Center.

  6. (Conditional) If you use Control Center 8.x or later, run the module installer only for the primary QDB, and Control Center automatically replicates this module to secondary QDBs.

  7. Run the module installer on all console computers to install the Help and console extensions.

  8. Run the module installer on the Exchange computers you want to monitor (agents) to install the agent components.

  9. Configure the PowerShell Execution policy, and, if necessary, establish a trust relationship between NetIQ Corporation and the user accounts that will run the Exchange2007 category of Knowledge Scripts. For more information, see Section 2.13, Configuring the PowerShell Execution Policy.

  10. Ensure proper permissions and memberships are set before discovering Exchange Server resources. For more information, see Section 2.5, Permissions for Discovering Exchange Server Resources.

  11. (Conditional) If you have not discovered Exchange resources, run the Discovery_Exchange2007 Knowledge Script on all agent computers where you installed the module. For more information, see Section 2.6, Discovering Exchange Server Resources.

  12. To get the updates provided in this release, upgrade any running Knowledge Script jobs. For more information, see Section 2.12, Upgrading Knowledge Script Jobs.

After the installation has completed, the Exchange2007_Install.log and PowerShellHost_Install.log files, located in the \NetIQ\Temp\NetIQ_Debug\<ServerName> folder, lists any problems that occurred.

2.2.2 Upgrading the Module

If you are upgrading from a previous release to this version, 7.6.0.1, install the version 7.6.0.1 on each Exchange Server agent, AppManager repository (QDB), and console.

AppManager for Microsoft Exchange Server and Exchange Online uses PowerShell scripts throughout the module, so you must set the PowerShell execution policy. For more information, see Section 2.13, Configuring the PowerShell Execution Policy.

To upgrade from a previous version to version 7.6.0.1:

  1. Stop the ad hoc jobs of the previous version and remove all Exchange Server and Exchange Online monitoring policies.

  2. (Conditional) If you have Exchange Online objects discovered in TreeView, then delete all the Exchange Online objects from the TreeView.

  3. Install version 7.6.0.1 of the module on all AppManager repositories (QDBs), consoles, and agents. For more information about running the installer, see Section 2.2, Installing the Module.

  4. The module installer automatically runs the Discovery Knowledge Script. If it does not, manually run Discovery_Exchange2007. For more information about the Discovery Knowledge Script, see Section 2.6, Discovering Exchange Server Resources.

  5. (Conditional) Run the Discovery_ExchangeOnline Knowledge Script to discover the Exchange Online objects. For more information about Discovery_ExchangeOnline Knowledge Script, see Section 2.9, Discovering Exchange Online.

  6. Recreate the ad hoc jobs and create new Exchange Server and Exchange Online monitoring policies.