# OpManager - System Requirements The system requirements mentioned below are minimum requirements for the specified number of devices. The sizing requirements may vary based on the load. - [Hardware requirements](https://www.manageengine.com/network-monitoring/help/hardware-and-software-requirements.html#hardware_requirements) - [Software requirements](https://www.manageengine.com/network-monitoring/help/hardware-and-software-requirements.html#software_requirements) - [Port requirements](https://www.manageengine.com/network-monitoring/help/hardware-and-software-requirements.html#port_requirements) - [External URLs to allow](https://www.manageengine.com/network-monitoring/help/hardware-and-software-requirements.html#external_urls_to_allow) - [PostgreSQL](https://www.manageengine.com/network-monitoring/help/hardware-and-software-requirements.html#postgresql) - [Microsoft SQL](https://www.manageengine.com/network-monitoring/help/hardware-and-software-requirements.html#microsoftsql) ## Hardware requirements **Note:** - CPU recommendation for deployments use the ®PassMark score. To learn more, click [here](https://www.cpubenchmark.net/high_end_cpus.html). - We strongly recommend assigning a dedicated machine for OpManager. - For 1000 devices, 5000 monitors and 5000 interfaces with default monitoring interval and default database retention, OpManager utilizes about 1 GB/day of disk space. The number may vary based on the entities monitored in your environment and other factors like events generated, Syslogs, Traps etc. - For customized Hardware requirements, click [here](https://www.manageengine.com/network-monitoring/help/opmanager_system_requirements_calculator.html). - For customized disk space requirements, click [here](https://www.manageengine.com/network-monitoring/help/opmanager_disk_space_calculator.html). - For Scalability Recommendations, click [here](https://www.manageengine.com/network-monitoring/help/scalability-recommendations.html). - [Click here](https://www.manageengine.com/network-monitoring/help/scalability-recommendations.html#scaling) for recommendations when monitoring up to 2500 devices. - For MSSQL User requirements, click [here](https://www.manageengine.com/network-monitoring/help/mssql-configuration.html#configmssql). ## Software Requirements The following table lists the recommended software requirements for an OpManager installation. | Software | Version requirements for Evaluation | Version requirements for Production | |---|---|---| | **Windows OS** | Windows 11 | Windows Server 2025/ 2022/ 2019/ 2016 | | **Linux OS** | Ubuntu 18 to 24, 26 and above; Fedora 43 and above; Red Hat 7 and above; Opensuse 16; Debian 12 and above; Rocky 10 and above; BOSS 10 | Ubuntu 18 to 24, 26 and above; Red Hat 7 and above; CentOS Stream 9 and above; Rocky 10 and above; BOSS 10 | | **Browsers** | Google Chrome/ Mozilla Firefox/ Microsoft Edge/ Safari, Other Chromium-based browsers | Google Chrome/ Mozilla Firefox/ Microsoft Edge/ Safari, Other Chromium-based browsers | **Note:** - **User Privilege:** Local administrator privileges required for OpManager installation. - Recommended screen resolution: **1920 × 1080** or higher. - For improved security and the best experience, please use the latest version of your browser. - We support the latest 10 major versions of each browser. ## Port Requirements This table details the network ports used by OpManager for various monitoring and communication functions. **Note:** - To learn more about changing port numbers, click [here](https://www.manageengine.com/network-monitoring/help/changing-port-numbers.html). - To ensure OpManager functions properly, configure the firewall to allow traffic through all the ports listed in the table, as these ports are required for communication between OpManager, its agents, devices, and integrated services. - **Connection:** Specifies the direction of communication for each port, such as "Outbound" (from OpManager to external systems), "Inbound" (from external systems to OpManager), or "Internal" (within the OpManager server itself). - OpManager uses ICMP (no TCP/UDP ports) for device discovery; refer to the table for the default ports used for each protocol. It is recommended to associate [credentials](https://www.manageengine.com/it-operations-management/help/add-credentials.html) for accurate classification and data collection. - OpManager uses ICMP for initial device discovery. If ICMP is unsupported, use the 'Add Device' or 'CSV file' options instead. - **Agent:** For proper functioning of agent-based monitoring in OpManager, ensure that the OpManager webserver port (HTTPS, 8061 by default) is allowed for outbound requests from each agent-monitored device. - Use **WinRM** when a single, well-known port (5985 for HTTP or 5986 for HTTPS) is preferred instead of configuring multiple dynamic RPC ports, or when DCOM/RPC ports are blocked or restricted by the network. ### External URLs to allow OpManager communicates with the following internet-facing endpoints for in-product chat support, maps, licensing, knowledge base links, and third-party integrations. Allow these URLs in your firewall or proxy to ensure uninterrupted access to the corresponding features. ### SalesIQ (in-product chat support) - [https://salesiq.zohopublic.com](https://salesiq.zohopublic.com) - [https://salesiq.zohopublic.in](https://salesiq.zohopublic.in) - [https://static.zohocdn.com](https://static.zohocdn.com) - [https://css.zohostatic.com](https://css.zohostatic.com) - [https://css.zohocdn.com](https://css.zohocdn.com) - [https://js.zohocdn.com](https://js.zohocdn.com) - [https://salesiq.zoho.com](https://salesiq.zoho.com) ### General - [https://maps.gstatic.com](https://maps.gstatic.com) - Serves Google Maps static assets. - [https://maps.zoho.eu](https://maps.zoho.eu) - Provides Zoho Maps services. - [https://maps.googleapis.com](https://maps.googleapis.com) - Provides Google Maps APIs. - [https://www.manageengine.com](https://www.manageengine.com) - Hosts ManageEngine website and resources. - [https://cdnjs.cloudflare.com](https://cdnjs.cloudflare.com) - Delivers third-party static libraries. - [https://creator.zohopublic.com](https://creator.zohopublic.com) - Hosts public Zoho Creator apps. - [https://creator.zoho.in](https://creator.zoho.in) - Hosts Zoho Creator services. - [https://ncm.nimbuspop.com](https://ncm.nimbuspop.com) - Required to retrieve firmware vulnerability database updates for Network Configuration Manager. - [https://creatorapp.zohopublic.in](https://creatorapp.zohopublic.in) - Hosts public Zoho Creator apps. - [https://maps.zoho.com](https://maps.zoho.com) - Provides Zoho Maps services. - [https://js.zohostatic.com](https://js.zohostatic.com) - Serves Zoho static assets. - [https://desk.zoho.com](https://desk.zoho.com) - Provides Zoho Desk support services. - [https://itom.nimbuspop.com](https://itom.nimbuspop.com) - Supports ITOM services. - [https://fcm.googleapis.com](https://fcm.googleapis.com) - Provides Firebase push notification services. - [https://updates.manageengine.com/](https://updates.manageengine.com/) - Required to download product updates, patches, and security updates. - [https://oauth2.googleapis.com](https://oauth2.googleapis.com) - Provides OAuth 2.0 authentication and token services for Google APIs. - [https://firebaseinstallations.googleapis.com](https://firebaseinstallations.googleapis.com) - Provides Firebase Installation IDs and authentication tokens for app instances used by Firebase services. ### Integrations - [https://www.manageengine.com](https://www.manageengine.com) - [https://accounts.zoho.com](https://accounts.zoho.com) — Use the corresponding regional domain (.in, .eu, .jp, etc.) - [https://sdpondemand.manageengine.in](https://sdpondemand.manageengine.in) — Use the corresponding regional domain (.in, .eu, .jp, etc.) - [https://www.servicenow.com](https://www.servicenow.com) - [https://slack.com](https://slack.com) - [https://demo.appmanager.com](https://demo.appmanager.com) - [https://alarmsone.manageengine.com](https://alarmsone.manageengine.com) - [https://www.pagerduty.com](https://www.pagerduty.com) - [https://www.atlassian.com](https://www.atlassian.com) - [https://login.microsoftonline.com](https://login.microsoftonline.com) - [https://forum.ansible.com](https://forum.ansible.com) - [https://www.splunk.com](https://www.splunk.com) - [https://www.freshworks.com](https://www.freshworks.com) - [https://api.openai.com/v1](https://api.openai.com/v1) **Note:** - These are outbound HTTPS endpoints; ensure your firewall or proxy allows outbound access from the OpManager server (and end-user browsers, for SalesIQ and Maps) to the URLs above. - Integration endpoints are only required if the corresponding integration is enabled. ## Database Requirements The following table lists the basic requirements for your OpManager database server. ### PostgreSQL Comes bundled with the product (PostgreSQL version 17.10). For Remote PostgreSQL, OpManager supports PostgreSQL versions 17.10 to 17.x. In case of failover, use MSSQL or Remote PostgreSQL. ### Microsoft SQL #### 1. Supported versions: **Note:** The MSSQL backend has been tested for OpManager with the following cloud services: [AWS RDS](https://www.manageengine.com/network-monitoring/help/installing-opmanager-with-amazon-rds-mssql.html), Google Cloud Platform SQL, Azure SQL and Azure SQL Managed Instance. **SQL 2025 (from build 12.9.148) | SQL 2022 (from build 12.8.452) | SQL 2019 | SQL 2017 | SQL 2016** #### 2. Important Notices: 1. For production use 64 bit versions of SQL. 2. Recovery mode should be set to SIMPLE. 3. SQL and OpManager should be in the same LAN. Currently WAN based SQL installations are not supported. 4. Developer edition of SQL Server is not supported. #### 3. Collation: - English with collation setting (SQL_Latin1_General_CP1_CI_AS) - Norwegian with collation setting (Danish_Norwegian_CI_AS) - Simplified Chinese with collation setting (Chinese_PRC_CI_AS) - Japanese with collation setting (Japanese_CI_AS) - German with collation setting (German_PhoneBook_CI_AS) #### 4. Authentication: Mixed mode (MSSQL and Windows Authentication). #### 5. BCP: The "**bcp.exe**" (Windows)/"**bcp**" (Linux) and "**bcp.rll**" must be available in the OpManager bin directory (applicable only for OpManager Enterprise Edition). The BCP utility provided with Microsoft SQL Server is a command line utility that allows you to import and export large amounts of data in and out of SQL server databases quickly. **For Windows:** The **bcp.exe** and **bcp.rll** will be available in the MSSQL installation directory. If MSSQL is in a remote machine, copy **bcp.exe** and **bcp.rll** files and paste them in the `<\OpManager\bin>` directory. The SQL server version compliant with the SQL Native Client must be installed in the same Server. **For Linux:** For BCP utility in Linux, mssql-tools (Microsoft ODBC driver for Linux) should be installed on an OpManager installed machine. Please follow the steps in the document provided below to install Microsoft ODBC driver on Linux servers. [https://learn.microsoft.com/en-us/sql/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server](https://learn.microsoft.com/en-us/sql/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server) The command to install ODBC driver is different for every Linux flavor. Please choose the correct Linux flavor and install the ODBC driver. - **Steps to move BCP utility to OpManager:** - After the ODBC driver is installed in Linux servers, the bcp utility files can be found in the below mentioned path. Copy both bcp and bcp.rll files to `/bin` and start OpManager once. - **For ODBC driver version 18:** bcp file in `/opt/mssql-tools18/bin/` and bcp.rll file in `/opt/mssql-tools18/share/resources/en_US/` - **For other versions of ODBC:** bcp file in `/opt/mssql-tools/bin/` and bcp.rll file in `/opt/mssql-tools/share/resources/en_US/` #### 6. User-role requirement: Server roles - "dbcreator", "public" and "sysadmin". User Mapping - Map this login to "master" with database role ownership as "db_owner" and "public". Click [here](https://www.manageengine.com/network-monitoring/help/mssql-configuration.html) to learn more.