Because the agent does not run as a virtual application, you must install it on the local disk of each cluster node, and not the shared cluster disk. Also install the same set of modules on each cluster node.
Before installing the AppManager agent and modules, determine whether the virtual server is active on the cluster node where you are performing the installation. If the virtual server is not active on the cluster node, some resource objects will not be discovered. To avoid this issue, move the virtual server to each node before you install the agent. If it is not possible to move the virtual server before you install the agent on the cluster node, you can move it later and use the Control Center console to run the appropriate operating system Discovery Knowledge Script to discover the agent.
Before you install the agent, ensure you have a Windows account for the agent services to use. For more information about the account, see Reviewing Required Accounts and Permissions. For more information about installing the agent locally on each cluster node, see Installing the Windows Agent Locally. For more information about installing modules, see Installing Modules.
You can remotely deploy agents to cluster nodes as long as you deploy to physical nodes and not the virtual server. For more information about remotely deploying agents, see Installing Agents Remotely.
After you install the agent and modules, you can run a combination of application-specific, MSCS, and NT Knowledge Scripts to monitor a virtual server.