I cant believe how this is happening in the modern age. My heart goes out to Gaza.


Blimey! Dont know how I feel about this.


Administrator privilege while installing agents

OMU – 8.x
Agent version – 8.60
Agent OS – Windows 2008 Standard Edition x64 R2
While installing agents on managed node, following error might prompt stating that agent is unable to set MANAGER
Info: Setting Manager to: abc.example.com
opcactivate Error: Error while setting MANAGER to abc.example.com
opc_inst Info: OVO Agent successfully installed.
opc_inst Info: OVO Maintenance script ends
opc_inst Info: Executing cmd /c change user /query > “C:\Windows\Temp\radF1CB0.t
mp” …
opc_inst Info: We have Terminal Server INSTALL mode (or compatible).
opc_inst Info: Moving install log file to C:\ProgramData\HP\HP BTO Software\log\
opc_inst Error: Could not move installation log file to C:\ProgramData\HP\HP BTO
Software\log\opc_inst.log. See C:\Windows\Temp\opc_inst.log
Also, when you try to start the agent, below error will be displayed.
c:\Program Files\HP\HP BTO Software\bin\win64>ovc
(ctrl-111) Ovcd is not yet started.
c:\Program Files\HP\HP BTO Software\bin\win64>ovc -start
Unable to start service OvCtrl
The handle is invalid. (6)
Above error is due to installation of agent with less privileged account. You can install the agent either by logging into the server with Administrator account or local admin account.
If you still face this issue, open the command prompt with “Run as administrator” option by right clicking the command prompt and execute installation script. Now, the agents will be installed properly.
If you are looking for agent installation steps, please follow “A Complete Guide to enroll a node in OMU”

I. Enrolling a node – A Complete Guide

In this part, I am going to discuss how to install agents manually on a node
1. Port 383 must be opened bi-directional between management server and managed node.
A. On Management server:
1. Identify the agent’s binaries. Usually, agent’s binaries will be located under vendor directory.
Format of the agent’s binaries location under vendor:
2. Read OVO-Agent.xml file under RPC_BBC directory, to check the agent’s current version.
Above line states agent’s current version is 8.60
3. Compress RPC_BBC directory and name it as below (depending on OS and Agent version)  and give required permission using chmod.
Example: Linux-8.60.tar.gz
4. Transfer the compressed agent’s binaries to managed node using scp, ftp, telnet, etc. whichever is feasible.
B. On Managed Node:
1. Extract the copied agent’s compressed binaries using tar or winrar to /tmp (Unix) or C:\temp (Windows)
2. Navigate to extracted location. In case of Windows, use command prompt.
3. Add the management server’s entry in host file or in DNS server to resolve the name resolution.
4. Execute installation script
# ./opc_inst.sh -s
In Windows
# cscript opc_inst.vbs -s
where is the name of the primary management server
Here, I am assuming that certificate server is same as primary management server and agent need to be installed on default path.
5. Check the agents status by executing
# ./ovc -status
# ovc -status
If PATH environment variable is not set for OVO agents, you can either set the PATH or you can navigate to install directory of agents
In UNIX: /opt/OV/bin
In Windows : C:\Program Files\HP OpenView\bin or C:\Program Files\HP\HP BTO Software\bin
All the agent’s processes should be running.
6. Check the certificate status from install directory
# ./ovcert -status
In Windows
# ovcert -status
If the status is pending, You can skip the next step
7. Request new certificate, if status is not pending
# ./ovcert -certreq
In Windows
# ovcert -certreq
In next part, I will discuss how to add a node in OMU from command line.