6.3

Because of a known issue with Windows, on Windows Server 2008 R2 and 2012 R2, Windows services might
keep old values of system variables, even though they have been updated or removed. As a result, updates
or removal of the HQ_JAVA_HOME system variable might not be propagated to the
Endpoint Operations Management Agent service. In this event, the Endpoint Operations Management agent
might use an obsolete value for HQ_JAVA_HOME, which will cause it to use the wrong JRE version.
System Prerequisites for the Endpoint Operations Management Agent
If you do not dene localhost as the loopback address, the Endpoint Operations Management agent does
not register and the following error appears: Connection failed. Server may be down (or wrong IP/port
were used). Waiting for 10 seconds before retrying.
As a workaround, complete the following steps:
Procedure
1 Open the hosts le /etc/hosts on Linux or C:\Windows\System32\Drivers\etc\hosts on Windows.
2 Modify the le to include a localhost mapping to the IPv4 127.0.0.1 loopback address, using
127.0.0.1 localhost.
3 Save the le.
Configure the Endpoint Operations Management Agent to
vRealize Operations Manager Server Communication Properties
Before rst agent startup, you can dene the properties that enable the agent to communicate with the
vRealize Operations Manager server, and other agent properties, in the agent.properties le of an agent.
When you congure the agent in the properties le you can streamline the deployment for multiple agents.
If a properties le exists, back it up before you make conguration changes. If the agent does not have a
properties le, create one.
An agent looks for its properties le in AgentHome/conf. This is the default location of agent.properties.
If the agent does not nd the required properties for establishing communications with the
vRealize Operations Manager server in either of these locations, it prompts for the property values at initial
start up of the agent.
A number of steps are required to complete the conguration.
You can dene some agent properties before or after the initial startup. You must always congure
properties that control the following behaviors before initial startup.
n
When the agent must use an SSL keystore that you manage, rather than a keystore that
vRealize Operations Manager generates.
n
When the agent must connect to the vRealize Operations Manager server through a proxy server.
Prerequisites
Verify that the vRealize Operations Manager server is running.
Procedure
1 Activate Endpoint Operations Management Agent to vRealize Operations Manager Server Setup
Properties on page 48
In the agent.properties le, properties relating to communication between the
Endpoint Operations Management agent and the vRealize Operations Manager server are inactive by
default. You must activate them.
2 Specify the Endpoint Operations Management Agent Setup Properties on page 49
The agent.properties le contains properties that you can congure to manage communication.
Chapter 7 Connecting vRealize Operations Manager to Data Sources
VMware, Inc. 47