# Remote Probe Deployment | OpManager Help

OpManager now supports silent probe installation, allowing probes to be deployed on remote machines directly from the central interface. It removes the need to log in to each system, download installers, and configure settings manually. Required inputs such as OS, credentials, and install path are provided once, and the probe is installed, configured, and registered automatically, with status and logs available in the UI.

## Prerequisites

Ensure the following conditions are met before initiating deployment:

- **Network requirements:** Required ports must be open for remote communication and file transfer.
- **Access requirements:**
  - Administrative privileges for Windows systems
  - Root-level access for Linux systems

## How to deploy probes remotely?

Go to OpManager central, and go to settings-> Configuration->Probe details.

Click **Deploy probe**.

Under **Probe Installation Details**, provide the basic configuration for the probe:

- **Probe Name:** Specify a unique name to identify the probe.
- **Central URL:** The URL of the Central Server is auto-populated based on the current server (for example, https://central-server:8064). Verify that the URL is reachable from the target machine; if it is not reachable, update it with the correct Central Server URL before deploying.
- **Customer Name:** The customer identifier is pre-filled from the existing configuration. Update this if deploying for a different customer.
- **Customer Mail ID:** The contact email is pre-filled from the existing configuration. Update this if a different notification address is required.
- **Proxy Required:** Enable this only if the probe must connect to the Central Server via a proxy.

[![Remote Probe Deployment in ManageEngine OpManager: Remote Probe Deployment](https://www.manageengine.com/network-monitoring/help/images/remote-probe-deployment.png)](https://www.manageengine.com/network-monitoring/help/images/remote-probe-deployment.png)

If **Proxy Required** is enabled, provide the following details:

- **Server Name or IP:** Specify the proxy FQDN or IP address (for example, proxy.corp.example.com or `10.0.0.5`).
- **Port Number:** Enter the proxy port (commonly 8080 or 3128).
- **User Name:** Provide the proxy authentication user name (use the required format, such as DOMAIN\user or user@domain).
- **Password:** Enter the password for the proxy user (stored securely).

Under **Probe Server Details**, define the target machine where the probe will be deployed:

- **Select Platform:** Choose the operating system (Windows or Linux).
- **Machine Name:** Enter the hostname or IP address of the target system.
- **File Location:** The installation path is pre-filled with the default location (C:\Program Files\ManageEngine\OpManagerPlus_P... for Windows). Modify this only if you want to install the probe in a non-default directory. Ensure the specified path is writable by the install account.
- **Machine User Name:** Provide an account with sufficient privileges (Administrator for Windows or root for Linux).
- **Machine Password:** Enter the password for the specified account.

In **Database Details** configure the database and communication settings:

- **Select Database:** Choose the database type (PostgreSQL or MSSQL).
- Under **Advanced Settings:**
  - **HTTPS Port:** The port for secure communication (default value is 8061).
  - **HTTP Port:** The port for non-secure communication (default value is 8060).

Click **Deploy** to initiate the remote installation.

Use **Reset** to clear all entered values or **Cancel** to exit before deployment.

After deployment, open the Installation Audit Report to verify the status and review logs.

If deployment fails, recheck credentials, proxy configuration, firewall rules, and file path permissions, then retry deployment. Use the Installation Audit Report and probe logs to identify and resolve specific errors.

**Note:**

- Silent installation requires uninterrupted network connectivity and does not allow manual intervention; if the connection drops or the process is interrupted, the install will fail and must be retried.
- Ensure required firewall ports are open on the target machine: TCP 445 for Windows file transfer, TCP 22 for Linux SSH, and the configured HTTP/HTTPS ports used by the probe/Central Server.
- Use Administrator (Windows) or root (Linux) credentials for deployment; insufficient privileges will cause immediate failure.
- Verify the installation path exists or that the install account can create/write to it; also confirm OS and CPU architecture match the probe installer.
- If a proxy is used, confirm the proxy is reachable from the target, allows CONNECT (or equivalent) to the Central URL and the probe’s HTTP/HTTPS ports, and that the supplied proxy credentials are correct.
- On failure, review the Installation Audit Report and the probe/agent logs to identify errors, correct the root cause (network, credentials, proxy, permissions, path), remove any partially extracted files, and retry the deployment.
- Keep credentials and proxy details accurate and current; update them if password or proxy policies change to avoid unexpected failures.