Preload and prerequisites options

This topic describes the preload and prerequisites options for installing PATROL for Exchange Servers.

PATROL for Exchange Servers 2003 preload options

PATROL for Exchange Servers provides an easy way to select the components you want to use when you monitor and manage your Exchange environment. When you install PATROL for Exchange Servers, all of the .km files are installed on your computer. However, only the packages you select during installation will be preloaded.

You can select these packages through either the Default or the Custom installation type, and all packages preload the following minimum components:

• MSEXCH_Server
• MSEXCH_Server_Health_Container
• MSEXCH_Connector_Performance
• MSEXCH_Address_List_Container
• MSEXCH_Address_List
• MSEXCH_Cluster_Container
• MSEXCH_Cluster_Res_Container
• MSEXCH_Cluster_Resources
• MSEXCH_DSA_Container
• MSEXCH_DSA_Cache_Container
• MSEXCH_DSA_Context_Container
• MSEXCH_DSA_Process_Container
• MSEXCH_DSAccess_Cache
• MSEXCH_DSAccess_Contexts
• MSEXCH_DSAccess_Processes
• MSEXCH_Network

The following table lists the additional components in the preload packages for PATROL for Exchange Servers.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.If you have a PATROL Agent installed on the computer where you are installing the PATROL for Exchange Servers component, the installation script designates PATROL for Exchange Servers as a preloaded KM in the agent configuration file. Once configured, a KM that is designated as a preloaded KM on a PATROL Agent automatically loads and begins to monitor resources and applications whenever the agent is started.

If you have a PATROL Console installed on the computer where you are installing the PATROL for Exchange Servers component, the installation script loads PATROL for Exchange Servers into the console.

For more information about preloading, including removing KMs from the preload list, see the PATROL Agent Reference Manual.

PATROL for Exchange Servers 2007 prerequisites

Remote monitoring places no restrictions on the target machines or the remote Exchange Servers. However, the computer that hosts the PATROL Agent must comply with the following requirements:

• Microsoft Exchange Server 2007 Management Tools must be installed. Before installing the Exchange management tools, you must first install the necessary prerequisites for Exchange 2007. For more information and instructions, see the technical library for Microsoft Exchange Server (provided online by Microsoft).
• The user account that the PATROL Agent uses to connect to the Exchange Server must be a member of the following groups:
  • Domain user group
  • Exchange Organization Administrators group
  • Administrators group

PATROL for Exchange Servers 2010 and 2013 prerequisites

Remote monitoring places no restrictions on the target machines or the remote Exchange Servers. However, the computer that hosts the PATROL Agent must contain the following:

• Windows PowerShell version 2.0 must be installed.
• WinRM version 2.0 must be installed and running.
• The PATROL Agent must be a part of the domain / forest / exchange organization in order to monitor Exchange Servers.
• The user account that the PATROL Agent uses to connect to the Exchange Server must be a member of the following groups:
  • Domain user group

  • Administrators group

    Note

    Ensure that the Windows PowerShell and WinRM installations are architecturally synchronized with the PATROL Agent host computer operating system--whether 32-bit or 64-bit. On the computer that hosts the PATROL Agent and also on the computer that hosts the Exchange Server, verify that the WinRM service is set to start automatically or start it manually. To configure the WinRM listener with the default settings, run the Winrm quickconfig command as administrator.

PATROL for Exchange Servers 2007, 2010 and 2013 preload options

PATROL for Exchange Servers provides an easy way to select the components that you want to use when you monitor and manage your Exchange environment. When you install PATROL for Exchange Servers, all of the .km files are installed on your computer. However, only the packages that you select during installation will be preloaded. 

You can select these packages during installation and all packages preload the following components, at a minimum:

• MSEXCH_Server
• MSEXCH_Server_Health_Container
• MSEXCH_Connector_Performance
• MSEXCH_Cluster_Container
• MSEXCH_Cluster_Res_Container
• MSEXCH_Cluster_Resources
• MSEXCH_DSAccess_Cache
• MSEXCH_DSAccess_Processes
• MSEXCH_Network

The package for PATROL for Exchange Servers contains the MSEXCH_EdgeServer.kml file. 

If you have a PATROL Agent installed on the computer where you are installing the PATROL for Exchange Servers component, the installation script designates PATROL for Exchange Servers as a preloaded KM in the agent configuration file. After it is configured, a KM that is designated as a preloaded KM on a PATROL Agent automatically loads and begins to monitor resources and applications whenever the agent is started. 

If you have a PATROL Console installed on the computer where you are installing the PATROL for Exchange Servers component, the installation script loads PATROL for Exchange Servers into the console.

For more information about preloading, including removing KMs from the preload list, see the PATROL Agent Reference Manual.