Platform support information changes regularly. For up-to-date information, see the support matrix at HP Software Support Online.
Before installing the agent on a supported Windows system, make sure that the system meets the following hardware requirements:
Agent Processes - At least 15 MB memory for agent processes.
Local Drive - 40 MB hard disk space required for installation.
NOTE:
Up to 40MB may be required for the performance database, depending
on the configured collections. The actual disk space used depends
on which packages and policies are installed on the managed node
and the amount of performance data collected.
The following section contains requirements for Windows managed nodes Windows 2000, XP, Windows Server 2003, and Novell NetWare.
You can run without NetBIOS as part of your Windows 2000 and XP managed node networking environments as long as Active Directory Service (ADS) client software is installed.
Running the management server in a Microsoft® Cluster HA package is possible. You should note the following requirements and limitations when installing on a node in a cluster:
Observe the following restrictions if you are installing to an Active Directory domain controller. If your agent is running under the Local System account, you can disregard these instructions.
If you want to install agents on Active Directory domain controllers (DC) and if you cannot use the default Local System account (your agent is running as an HP ITO account) follow the sequence described:
All Windows managed nodes must meet these SNMP requirements to collect SNMP events and discover node properties:
Windows 2000 Professional, Server Edition, Advanced Server Edition or Data Center Edition, Service Pack 1, 2, 3, and 4. Windows 2000 without any service packs is not supported.
Recommended: Windows 2000 SP4.
Microsoft recommends that users accept all critical updates from Windows Update, available from the top of your Start menu. Click Windows Update to reach the Microsoft Windows Update web page, where you can scan for recent updates of critical and lesser severity. A list of critical updates is returned and you can select those you want to download. HP Operations Manager for the Windows operating system was tested with Microsoft's critical updates.
Microsoft recommends that users accept all critical updates from Windows Update, available from the Admin dialog. Select All Programs -> Windows Update to reach the Microsoft Windows Update web page, where you can scan for recent updates of critical and lesser severity. A list of critical updates is returned and you can select those you want to download. HPOM for Windows was tested with Microsoft's critical updates.
All Windows Server 2003 managed nodes must meet the requirements for the SNMP service for all Windows managed nodes, as described above.
Microsoft recommends that users accept all critical updates from Windows Update, available from the Admin dialog.
To reach the Microsoft Windows Update web page, where you can scan for recent updates of critical and lesser severity, select:
All Programs -> Windows Update
A list of critical updates is returned and you can select those you want to download. HPOM for Windows was tested with Microsoft's critical updates.
HPOM for Windows provides a set of binary files for Windows managed nodes, located in the following directory on the management server.
%OvShareDir%\Packages\Windows\Windows_manual\<language>
For example:
C:\Documents and Settings\All Users\Application Data\HP\HP
BTO Software\shared\Packages\Windows\Windows_manual\en
To manually install the agent on a non-English language system, use the Japanese language version of the agent for Japanese systems, and the English language version for all other languages (for example, Spanish, Korean, or Chinese).
Although the agent is usually installed using the management server console, there are some circumstances when installing the agent manually on the Windows node is advantageous or essential, for example:
The HPOM package is a mechanism for deploying an agent without using an HPOM management server.
This installation installs the agent and the configfile policy type (which is used by some Smart Plug-ins).
New
A first time install. No previous manual agent package is installed on the target machine.
Maintenance
Reinvoking the install program for a manual agent package that is already installed places the installer in "maintenance mode". In this mode, three operations are available (as selected in the maintenance mode screen displayed when the install program starts). These modes are:
Maintenance mode is invoked by either rerunning setup.exe or selecting the Change button for the manual agent in Add/Remove Programs.
Similar to a Modify install, except that existing agent data is preserved during the upgrade process. During installation, the install program determines automatically if an upgrade is needed.
Alternatively, if the console users do not have permission to add and remove programs on the managed node, you can add the policy management and deployment (PMAD) user to the local administrators group. By default, in an Active Directory environment, the management server installation creates the PMAD user with the name HP-OVE-Deleg-User (but the administrator who installs the management server can specify a different user name).
You can add the PMAD user to the local administrators group
using Computer Management in Windows. Alternatively, you can start
the Windows Node Security Setup on the management server. Log in to
the management server as a user with administrative rights on the
node (for example, a member of the domain administrators group) and
then start OveConfig.exe from a command prompt:
<installation directory>\bin\OveConfig.exe
<management server host name> <unique ID of
node>
To copy the unique ID of a node:
Check to ensure that the managed node meets all hardware and software requirements specified above. Update the node as necessary before continuing.
Prerequisites can be checked automatically with the ovoreqcheckagt tool, with the command:
Windows_manual\<language>\ovoreqcheckagt.exe
For detailed information about the ovoreqcheckagt
tool, refer to the HPOM for Windows online help.
On the management server, go to the directory:
%OvShareDir%\Packages\Windows\Windows_manual\<language>
Copy the directory to your managed node system or to some portable media.
On the node, start setup.exe.
In the Destination Folders screen you can use the default destination folder or select a destination folder where you want to install the agent. The destination location you select here will be used as the default folder for other HP BTO Software products and once set cannot be changed without first uninstalling all HP BTO Software products using it. This includes the agent.
The default destination folders are:
<ProgramFilesFolder>\HP OpenView\
and
<ProgramFilesFolder>\HP OpenView\Data
where <ProgramFilesFolder> is the default program files parent folder on the target machine.
In the Agent Configuration screen, set the host name of the agent's management server and the name of the account that the agent service will use.
In Hostname, type the fully qualified name of the management server that you want to manage this node, for example, "potato.veg.com".
In the Run Agent service as radio group, select either HP ITO Account or LocalSystem.
In previous releases, the two local user accounts (HP ITO Account and opc_op account) were created on the node and random passwords were generated. Since the OVO for Windows 7.20 release, the HP ITO Account and opc_op account are no longer created on the node. Instead, the Local System account is used as the default.
If you are upgrading from a previous release that used the HP ITO Account, you can continue to use this account. Upgrades keep the existing user on the node. See the HP Operations Manager for Windows Installation Guide for further details on the HP ITO Account and Local System accounts.
NOTE:
After the agent is installed, you can change the management server
host name and agent service account by invoking Modify mode (see
Installation Types).
Check the status of the completed installation operation by viewing the install log file. Log files reside in <TempFolder> (where <TempFolder> is the name of the target machine's "temp" folder. This is typically:
C:\Temp or C:\Documents and
Settings\<user name>\Local Settings\Temp
A log file is created for every install operation (see Installation Types below) using the following naming rules:
Any previous log file is saved by appending a number to its file name before the new log file is created.
If you want to check to see if the agent is running, open a command shell and enter:
opcagt -status
To restart the agent, enter:
opcagt -start
You can install agents in unattended mode by using a configuration file and some command line parameters. In addition, you can use the configuration file in an interactive installation to offer different default values in the install wizard. In the configuration file you can specify all the configuration values that you can specify during an interactive install.
The default configuration file is named AgentConfig.ini and resides in the same location as the installation files. The installation uses this file automatically. You can also specify an alternative configuration file on the install command line (see below). For instructions on how to edit configuration parameters read the information contained in the AgentConfig.ini file.
There are three methods for launching an unattended install:
Command Line Options
/qr - runs the install in "reduced" UI mode. No
user input needed. Only modeless status dialogs are displayed./qb - runs in install in "basic" UI mode. Similar
to reduced mode, but adding a "+" to the option (/qb+) displays a
modal dialog at the end of the installation session./qn - runs the install with no visual indicators.
Adding a "+" to the option (/qn+) displays a modal dialog at the
end of the installation session.CONFIGFILE=<config filename><config filename> is the fully qualified
name of the configuration file.Unattended Install Examples
Run an install completely silently. This example shows all three launch methods.
setup.exe /v"/qn"
or
"HP Operations Manager Manual Agent.msi" /qn
or
msiexec.exe /I "HP Operations Manager Manual Agent.msi"
/qn
Run an install completely silently, and display a modal dialog signifying that the installation is complete.
setup.exe /v"/qn+"
Run an install showing a progress dialog, and display a modal dialog signifying that the installation is complete.
setup.exe /v"/qb+"
Run a completely silent install and use the custom configuration
file "c:\temp\myconfig.ini".
setup.exe /v"/qn CONFIGFILE=c:\temp\myconfig.ini"
It is possible to use the third-party tool NetInstall to perform the manual installation of the Windows agent. If you own the NetInstall software (which is not provided with HPOM for Windows) you can use it to install the Windows agent providing you meet the preconditions described below and the correct patches are applied.
If you do not want to accept the defaults in the AgentConfig.ini file, you need to change the file in these areas: (You must at least modify the management server host name section.)
You will find the AgentConfig.ini file with the rest of the agent package in the following folder on the management server:
%OvShareDir%\Packages\Windows\Windows_manual\en
To use NetInstall to manually install the Windows agent, follow these steps:
HP Operations Manager Manual Agent.msi file.When the computer is connected to the network, it will begin to broadcast its presence to the management server. Use the procedure below to begin to manage the node.
To manage a Windows node with a manually installed agent, complete the following steps:
After performing the installation procedure above, you need to indicate the character set that the node is using by adding an entry to the nodeinfo file on the node.
Open the file %ovagentdir%\conf\opc\nodeinfo in a
text editor.
Add the line:
OPC_NODE_CHARSET <character set>
Where <character set> is one of the following:
big5gb2312acp932eucKRacp1250acp1251acp1255utf8 or asciiIf you use utf8 or ascii as codeset in the nodeinfo file, the data is not converted but is sent "as is" to the management server. Therefore the data must be in a codeset the management server can handle.
With OVO for UNIX®, the management server cannot communicate with a managed node that uses the codeset utf8. If the managed node reports to both an HPOM for Windows and an OVO for UNIX management server, use ascii instead of utf8.
NOTE:
If for some reason the node does not appear under unmanaged nodes,
you can add it as if it were a new node.
© Copyright 2001-2008 Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Microsoft and Windows are U.S. registered trademarks of
Microsoft Corporation.
UNIX is a registered trademark of The Open Group.