Installing OpManager agent in your devices

OpManager's agent-based monitoring feature allows you to deploy an agent on your end-device. The agent comprehensively collects the data from your end-device and sends it to OpManager for further inspection and analysis. Furthermore, even if the connection between OpManager and the end-device is lost, the agent stores the data locally and then sends it to OpManager the moment the connection is reestablished.

You can install the OpManager agent in your network devices in 3 different ways. Before you proceed with the installation, make sure that all the prerequisites for agent installation have been taken care of.

In case there are any errors displayed during the installation, visit this page to know more about possible error messages during agent deployment and how you can resolve them.

2. Manual installation:

You can manually download the Agent installation file from Settings → Discovery → Deploy Agent, and tapping the "Download" button on the top of the page. OpManager Agent zip file will then be downloaded. Extract the zip file and paste the extracted OpManagerAgent.msi and OPMServerInfo.json files under the local directory. This can be used to manually install the OpManager agent on any windows device.

Once installed, the agent automatically syncs the device details to OpManager, and the device is listed under the Inventory page.

Note: Place the extracted OpManagerAgent.msi and OPMServerInfo.json files under the same directory before initiating the installation of the agent.

3. Using Active Directory (bulk installation):

You can also push the agent to multiple devices in your network by using Windows GPO in your Active Directory server.

Installation using GPO can be done in two methods:

• Using GPO scheduler: Agent can be instantly pushed to devices in the domain. Fastest method of installation.
• Using GPO startup script: Agent will be installed during next refresh cycle.

Installation for Unix

1. Manual Installation

To manually install the Unix agent for your network, follow the steps provided.

1. Go to Settings -> Discovery -> Deploy Agent. Select the appropriate Unix system section.



2. To download the Unix Monitoring Agent archive file, click on the Download button or access the appropriate version from the download page
3. Follow the steps provided in the file integrity page to verify the integrity of the downloaded file.
4. After successfully verifying the integrity, copy the downloaded Agent Archive file to the OpManager Application Installer Server and extract it to the OpManager Home\agent\resources\unix directory



5. After extraction of the Archive file, verify that the listed folders and files are present and properly extracted.
   • Folders
     • \agent\resources\unix\installer\arm
   • Files
     • Under unix folder
       1. version.properties
     • Under unix\installer folder
       1. OpManagerFullStackAgent_x86Linux.install
       2. OpManagerFullStackAgent_x64Linux.install
       3. OpManagerFullStackAgent_CrossPlatform.install
       4. OpManagerFullStackAgent_LinuxIns.sh
     • Under unix\installer\arm folder
       1. OpManagerFullStackAgent_x64Linux.install
6. Reload the OpManager web client once to cross-verify that all files and their integrity are in the proper state.
7. If it's in the proper state, you will see only two steps listed under the appropriate Unix flavor section.



8. If the file is in an improper state, an error message like "file not found" or "file integrity failed" will appear. Resolve the issue using the provided details, then reload the OpManager web client to confirm that no error messages are shown under the Deploy Agent → Appropriate Unix Flavor section.



Note: You don’t need to download the files every time you visit the Deploy Agent section—this is a one-time setup. Once the required files are properly placed, you’re all set to start using the Unix Server Monitoring Agent.
9. Then, connect the target Monitoring server in the terminal for Agent Installation.
10. Copy and run the download command in the terminal to transfer the Agent Installer script file OpManagerFullStackAgent_LinuxIns.sh to the target end server.



Note: In the above command, ensure that the OpManager server's host details are reachable from the target server. If not, modify the command with the correct and reachable host information.
11. Ensure that the installer script file OpManagerFullStackAgent_LinuxIns.sh has been fully downloaded without any interruptions.
12. Copy and run the install command to begin Agent Installation.



Note: In the above install command, verify that the OpManager server's host details—such as Hostname, IP Address, or NAT Server details—are correct and reachable. If not, update them accordingly and run the modified command in the terminal.
13. After successful installation, you will find the agent listed under Settings → ITOM Agents → Monitoring Agents section
14. If the respective device is already being monitored using credentials in OpManager, you need to associate the agent with that device by clicking the Associate option available.
15. If the device is not previously monitored and is being added for the first time, it will be auto-added and monitoring will begin automatically.

2. As a Non-Root User

• Append -nr / -nr=<Custom Installation Path where to install> argument to the install command while performing the installation.

Example install command:

bash

OpManagerFullStackAgent_Linux.sh -i -nr=/home/test/ManageEngine/OpManager-agent_type=server .....

OR

bash

OpManagerFullStackAgent_Linux.sh -i -nr -agent_type=server .....

3. Using Organizational Proxy

• Add the proxy argument to the Install command as like below:

bash OpManagerFullStackAgent_LinuxIns.sh ..........

proxy=user:password@proxyhost:proxyport

OR

bash OpManagerFullStackAgent_LinuxIns.sh .......... -proxy=host:port