Frequently asked questions

    • General

      Q. Are there any restrictions on the 30-day trial?

      A. No, the trial edition comes with all functionalities and you can monitor unlimited number of devices. If you need to extend your evaluation beyond 30 days, please request a license.

      Q. What are the system requirements for OpManager?

      A. Please refer to the System Requirements page.

      Q. Am I eligible for technical support during evaluation?

      A. Yes absolutely. Install a 30-day trial version and register yourself during installation to avail free technical support during evaluation period.

      Q. How is OpManager licensed?

      A. OpManager is licensed based on the number of monitored devices. Any device that responds to an ICMP ping can be monitored using OpManager e.g. Routers, Switches, Firewalls, Servers, UPS, printers. In a virtualized environment, every virtual instance is considered as a separate device for both monitoring and licensing purposes.

      Q. Do I need to rebuild OpManager from scratch after purchasing?

      A. No, all ManageEngine products are licensed through a registered XML file. One can simply apply the license and use the same OpManager instance in production environments. One can even move the data to a different server if needed.

      Q. Does upgrading to a newer OpManager version cost me?

      A. No, it is absolutely free. All you need to do is, ensure you have paid the Annual Maintenance and Support fee. 

      Q. If I buy more devices or add-ons or plug-ins in future, how does it work?

      A. Absolutely, you can upgrade OpManager at any point of time. For instance, if you wish to upgrade OpManager 250 devices to 500 devices pack, you have to pay only the difference between these price slabs. Similarly for add-ons and plugins, you have to pay only the cost pertaining to it as per the current pricing.

      The newly obtained license file has to be applied on your existing OpManager installation to enable the purchased devices pack or modules. It is not necessary to start things from scratch.

      Q. Can I buy a single 250 devices OpManager license and monitor in two different locations?

      A. No. The license is restricted to a single installation of OpManager and not a consolidated license for the enterprise. In such a case you have to buy OpManager Enterprise Edition for remote network monitoring or separate license for each locations. 

      Q. How does OpManager monitor the devices?

      A. OpManager is an agent-less monitoring and management tool that uses a wide variety of protocols and technologies: ICMP, SNMP, WMI, CLI (Telnet/ SSH), TFTP, SCP. OpManager also includes a Syslog demon, SNMP Trap listener and Flow collectors for NetFlow, sFlow etc.. All these and more bring together many network performance monitoring and management capabilities within OpManager.

      Q. Which vendors are supported by OpManager?

      A. OpManager supports out-of-the-box over 100 vendors. To list a few: 3Com, Cisco, DELL, HP, D-Link, Extreme, Fortigate, Foundry, Juniper, Netgear, Netscreen, Nortel, Linux, Solaris, HP-UX, IBM-AIX, Microsoft Windows, APC, Libert. 

      Q. How many devices can I monitor with OpManager?

      A. The OpManager polling engine can monitor upto 10,000 Interfaces. However this depends on the system hardware, polling frequency and type of devices. The OpManager Enterprise Edition can monitor upto 50,000 interfaces. To know the exact number of interfaces monitored by your OpManager installation, refer to the "About" page in the product (top right-hand side).

      Q. Does OpManager integrate with 3rd party tools?

      A. Yes through API. More about REST API here. Further OpManager integrates with ManageEngine products viz. ServiceDesk Plus On-Premise, Firewall Analyzer, Applications Manager, NetFlow Analyzer and Device Expert. See more on OpManager Integration

      Q. Can I Install OpManager on Linux? Is there any limitation?

      A. Yes, you can install OpManager on any Linux server viz. RedHat 7.x and above, Debian 3.0, Suse, Fedora, Mandrake. However NCM plug–in supports only Windows OS and doesn’t support Linux.

      Note: Installing OpManager on a Linux server will disable all WMI based monitors.

      Q. Is OpManager using 'Apache Struts' framework?

      A. Apache Struts was used in OpManager till version 11600. Latest version of OpManager doesn't use 'Apache Struts'.


      The following CVE id's are not applicable to OpManager:

      • CVE-2013-2251
      • CVE-2017-5638
      • CVE-2018-11776

      Q. What’s the difference between OpManager standalone version and enterprise edition?

      A. There’s no difference in the functionality. OpManager Enterprise Edition is designed to scale the network monitoring and management needs of large enterprises managing more than 500 servers or 5000 interfaces. The Enterprise Edition lets you deploy Probes for scalability on the LAN or in the remote locations to manage distributed networks.

      Q. Can the enterprise edition manage distributed networks?

      A. Yes. Its Central-Probe architecture helps you manage distributed networks from a central location.

      Q. What are the system requirements to install Enterprise Edition?

      A. Refer the detailed system requirements specified here.

      Q. I’m an existing user of OpManager standalone version, can I switch to Enterprise Edition for better scalability?

      A. Yes, if you are managing more than 500 servers or 5000 interfaces, the Enterprise Edition is the best fit for you. Please sign-up using this form. Our support engineers will call and assist you.

      Q. How the Enterprise Edition is licensed?

      A. OpManager is licensed based on the number of monitored devices. Any device that responds to an ICMP ping can be monitored using OpManager e.g. Routers, Switches, Firewalls, Servers, UPS, printers. In a virtualized environment, every virtual instance is considered as a separate device for both monitoring and licensing purposes.

      Q. Is it possible to run the Central and Probe on the same machine?

      A. Yes, it is possible provided you meet the system requirements of both the Central and Probe.

      Q. Is the data communication between the Central and Probe secured?

      A. Yes it is secured. The Central and Probe communicate xml over HTTPS/HTTP connection.

      Q. Does the Enterprise Edition run on MSSQL?

      A. Yes, the Enterprise Edition runs on MSSQL. However it also includes PostgreSQL bundled.

      Q. My Central Server runs on a server in which two ports (port1-main, port2- for failover)work off of different ISPs. Is it possible set up the Central server to fail-over from port1 to the other?

      A. Ideally, OpManager will bind to both the IPs and can be accessed via both the addresses. In the Enterprise Edition deployment, you would have specified the Central Server address in the Probe. If both the IPs resolve to the address you have configured, there should not be any problem. If you have configured one of the IP addresses as the Central Server address, then you must take care to see that it automatically resolves/redirects to the other port that is available to effect the fail-over.

      Q. I'm a service provider and have more than 100 remote sites to monitor. Each site has approximately 10 devices to monitor. Will OpManager Enterprise Edition (EE) suit me?

      A. Yes, OpManager EE is built for scaling to the monitoring needs of emerging and large organizations.

      Q. How can I migrate to Standard edition from v12.3?

      A. You need to migrate to version 124015  or above to apply Standard license.

      Q. Can I downgrade from OpManager Professional edition to OpManager Standard edition?

      A. No. You can only upgrade from OpManager Standard edition to OpManager Professional or OpManager Enterprise edition. Downgrade is not supported.

      Q. Is OpManager Professional edition the same as OpManager Essential edition?

      A. Yes. OpManager Essential edition has now been renamed as OpManager Professional edition.

      I still have some questions which needs clarification!

      If you have any questions about OpManager, feel free to raise a support request and we’ll get back to you.

      Q. Based on what condition are interfaces listed as subinterfaces?

      Subinterfaces are listed based on two criteria

      • When two or more IP Addresses have the same ifIndex in the same device. (You can check it in ipAdEntifIndex (. in RFC1213-MIB)
      • When two or more interfaces have the same IP address in the same device or different devices.

      Q. Why are interfaces not rediscovered in my device?

      • Check whether the SNMP Credential is passed in the device.
      • Check whether the ifTable returns an output in the MIB browser (Both Standalone and in OpManager)

      Q. Why is there no data collection at my interfaces?

      • Check whether the SNMP Credential is passed in the device.
      • Check whether the ifTable returns an output in the MIB browser (Both Standalone and in OpManager)

      Q. Why are the interface traffic values displayed as zero?

      Check ifInOctects (. and ifOutOctects (. for the specified interface in the MIB Browser (RFC1213-MIB)

      Q. Why do traffic values differ from the real-time interface values in my interface graphs?

      Traffic values are different in these Interface Graphs because, data collection happened at a different time. When you check real-time traffic during the interface's next poll, you may find that the real time traffic values and the interface graph values are the same.

      Interface related reports are based on an hourly table. You can check these reports after an hour from when these interfaces were added.

      Q. Why the Ping/Availability status failed for the device even the device is up?

      The following may be the reasons for the ping option to fail even when the device is Up and running.

      1. ICMP agent is not enabled in the destination device. server 

      By default, OpManager checks the availability of a device with the help of ICMP ping function. But some business environment may only use the TCP agent in their devices as per their business functionality. In such cases, you can choose any of the alternate protocols (TCP or SNMP) to monitor the availability of those devices.  

      To change the monitoring method,

      • Go to the Device Snapshot page of that particular device. 
      • Click on the three horizontal lines on the top right corner and select Edit Device details.
      • Select TCP as the method under Availability Monitored via and save the changes. 

      2. The device may not be reachable from the OpManager server.

      The following may be the reasons for a device to be Up and not reachable.

      • Communication port may have been blocked by the Firewall
      • Network latency 
      • ICMP traffic may have been disabled in that particular device.

      User personality identifiable information like an email id/ phone number may be used multiple times in OpManager for various reasons across modules. The Personality Identifiable Information Search in OpManager allows you to locate the modules and view the total number of times a particular identity is used.

      Q. What are the different types of Personality Identifiable Information in OpManager?

      • Email ID
      • Name 
      • Phone Number
      • Mac Address
      • IP Address

      Q. Will deleting a Nutanix cluster delete all the devices/entities under it?

      If a Nutanix cluster is directly deleted from OpManager, all the hosts and VMs under it will be monitored as individual physical devices if that cluster is still intact. But if the cluster itself has been dissociated from the network and is also deleted from OpManager, all devices under it will be reported as "Down" and will be raised as alerts in OpManager.

      Q. Why is the 'invalid address case' error displayed when 'Test Mail' is clicked?

      This error is shown when the mail server credentials are not configured (i.e. the 'User Name' and 'Password' fields under 'Authentication Details' in Settings -> General Settings -> Mail Server Settings are left blank), but the mail server used has a mandatory requirement for credentials to be configured.

      Q. Why does OpManager appear to be using a lot of postgres processes?

      OpManager will use only one postgres process but it may appear to be using more because, multiple products like Applications Manager and Service Desk Plus etc. might be installed in the same server. This is regular and expected behavior for postgress and is harmless.

      Q. Why does the product UI appear to load slowly in the Central Server?

      This is mostly caused due to high latency between the Probe Server and the Central Server.

      Open command prompt in the Probe Server and ping the Central Server, the ping response should be less than 100 ms, else the page loading in the Central Server might take time to load.

      Q. What are the Cisco router/switch models supported for IPSLA monitoring in OpManager?

      As of now, OpManager only supports Cisco IOS and Cisco IOS-XE type swithces and routers for IP SLA monitoring in OpManager.

      Q. Why are SNMP traps not being forwarded to OpManager?

      Follow these steps to check for potential issues:

      1. The SNMP traps in OpManager listen on port 162, so check whether port 162 is available on the server.

      2. Please use a real-time packet capture tool to see if there is a response to the destination.

      3. Check the SNMP trap settings on OpManager to see if the device is listed on the 'selected' list.

      4. Finally, check for possible blockage issues due to firewall.

      Q. What is "Product promotions" under Settings -> System Settings -> Client Settings?

      All promotions/advertisements related to the product will be shown in the product UI if this option is enabled.

      What is "Product Assistance Notification" under Settings -> System Settings -> Client Settings?

      Product related help will be shown in the product UI if this is enabled.

    • Inventory

      Q. Why the discovered devices are classified as Unknown?

      The discovered device status is marked as 'Unknown' in the following conditions

      1. The credentials are invalid.
      2. A matching device template is not found. (You can create a custom template or import custom-templates from third party website or forums)


      Q. Why is the status of a device shown as 'Not Monitored'?

      The device status is classified as 'Not Monitored' when

      1. The credentials are invalid or outdated.
      2. The device is not pingable from OpManager server.
      3. The device has been unmanaged by the network administrator.


      Q. Why are interfaces not rediscovered for the devices?

      It maybe due to the following reasons:

      1. Check if the interface discovery is enabled in the discovery profile.
      2. SNMP credential failure
      3. SNMP timeout due to large number of interfaces


      Q. Why do I see new devices being added to OpManager automatically?

      OpManager will add new devices automatically in the following scenarios:  

      1. Scheduled discovery (scheduled by the admin/operator)
      2. Auto VM discovery is enabled
      3. Devices discovered via SNMP traps (Settings > Discover Settings > discover devices via trap)


      Q. I have created a custom category, but the same is not listed in Inventory category list. Why?

      After creating a custom category, the operator must associate devices to this category. If not, the newly created category will not be displayed.

      Q. Why are interfaces not discovered for my device?

      1. Discovery - Interface is disabled in the Discovery Profile
      2. Interface type is not selected in the Discovery - Interface page


      Q. How to configure multiple threshold severity for interfaces?

      1. Go to Inventory>Interfaces
      2. Choose the required interface from the list
      3. Click on the menu icon on the top right corner of the interface summary page
      4. Click on Threshold Settings and assign the threshold values for attention, trouble, critical for Utilization, Error Rate & Discard Rate
      5. Click on Save


      Q. How to view interface graphs for multiple interfaces in a single page?

      1. Go to Inventory > Interfaces
      2. Select the required interfaces by ticking the appropriate check boxes and click on Generate Reports button on the top right corner.
      3. Choose the time frame, monitoring parameters and click on Generate Report.

      Q. Why am I receiving wrong interface alerts?

      Ifindex is an unique number that identifies each and every interface. When an interface is changed physically, the ifindex also changes. But, in OpManager, that interface will still have its old ifindex value. This directly affects the monitoring and data collection of that particular interface and triggers wrong alerts. You can either persist using the same ifIndex or enable schedule rediscovery for those interfaces in particular. 

      Q. Why there is no data when I choose custom time less than 1 day?

      Reason: OpManager archives and maintains data from different performance tables regularly. 
      Likewise, the data collected at that very instance is stored in the Statsdata table. This is known as raw or current data. This table is created every 24 hours, which means the backup of the previous day's data is carried out at the end of the day. So, when the custom time period mentioned is less than a day, OpManager will not have any data to display. 
      Solution: Since the backup takes place between 23.55 hrs to 23.58 hrs every day, specifying the duration from that day's midnight to the next day's midnight will fetch the necessary information.To know more about generic data archiving behaviour in OpManager, visit

      Q. Why does the real time graph values differ from the interface snapshot graph values?

      The primary reason for this mismatch is the fact that both the graphs fetch data in two different ways. In the real time graph, the refresh rate is set to 1 second by default and the polling happens every 10 seconds. Concurrently, in the interface snapshot graph, the default polling interval is 15 minutes, but can be customized to a minimum of 30 seconds. Here, the polling happens for the time interval that is specified by the user. Clearly, both the graphs fetch data at different polling intervals and operates differently. 

      Q. Why are some criteria for Notification Profiles missing from the Notification Profile section of device snap shot page?

      In the device snap shot page, the criteria for Notification Profiles will only be listed based on the device type and applications installed in the device.

      Example: MSSQL related threshold criteria will only be available in the Notification Profile section of the device snap shot page if MSSQL is installed in the device.

    • Alarms

      Q. What is Alarm Escalation?

      Alarm Escalation is an automated process, used to notify crucial issues to a higher authority when alarms are not cleared in a specified time period, through e-Mail and SMS. To know about configuration, click here.

      Q. When should I use Alarm Escalation?

      When an alarm is raised corresponding to a business critical device (for e.g, a Web Server), the issue must be resolved immediately. In that case, Alarm Escalation Rules can be defined for the web server to notify the concerned person. To know more, click here.

      Q. How to create a trap processor using vendor MIBs?

      • Go to Settings > Monitoring > SNMP Trap processors.
      • Click the 'Load from MIBs' button and select the relevant MIB.
      • Select the trap processors that you want to enable, and click 'Save' to apply the changes.
      • If you wish to add additional mibs from vendors, you can place those mibs under <opm_home>/mibs.

      Q. How can I check whether traps received in OpManager or not?

      • Go to the directory where OpManager was installed and navigate to OpManager/Bin/MibBrowser.
      • In the MiBBrowser, choose Trap viewer under View.
      • Press Start to turn on the Trap viewer. All the traps entering OpManager will be displayed.

      Q. How to forward trap(s) from OpManager to other NMS servers?

      Go to Settings -> Tools -> Forward Trap. Click on Add Destination to add a destination host & port number to which the traps must be forwarded. Click on Start Forwarder to begin forwarding the traps to the desired host.

      Please note that traps cannot be forwarded to selective destinations.

      Q. How to change SNMP trap port?

      To change the SNMP trap port follow these steps:

      • Navigate to Monitoring-->SNMP Trap Processors
      • Click Trap Settings, change the Trap Port and Save.

      Q. Why am I not receiving any traps?

      Traps might not be received in OpManager because of connectivity or port availability issues. If you're not receiving any traps in OpManager, check the following:

      • Check if the device that sends the trap is discovered and is not in 'unmanaged' state in OpManager.
      • Check if the port specified for traps is not being blocked by your firewall.
      • Try pinging the OpManager server from the concerned device to see if it's reachable.
      • Also, check if the port assigned for receiving traps is available in OpManager and not being used by any other processes.

      Q. What happens when an SNMP trap processor is disabled?

      When a SNMP trap processor is disabled, the corresponding SNMP traps that are received will not be processed.

      Q. Why should I suppress an alarm?

      When a device is under planned maintenance, alarms will be generated for the device. In that case, alarm suppression can be used.

      Q. Can I suppress alarm for custom time period?

      Yes, alarms can be suppressed for custom time period. To know more about how to configure it, click here: How to suppress alarms?

      Q.What is the default SNMP Trap port?

       The default SNMP Trap port number is 162.

      Q. How to find if a Trap port is blocked?

      When a Trap port is blocked, it will be notified as a message on the top in Alarms -> Trap Alarms page in OpManager's UI.

      Q. Where can I view traps in OpManager?

      Traps received in OpManager can be viewed lively using the Trap Viewer. The Trap Viewer can be accessed by the following ways:

      1. Navigate to Alarms--> Trap Alarms and click on Trap Viewer icon on the right corner.
      2. Navigate to Monitoring-->SNMP Trap Processors  and click on Trap Viewer icon on the right corner.
      3. Click on Tools --> Trap Viewer.

      Q. Why am I unable to view Trap Alarms in OpManager?

      OpManager processes only the traps that have suitable Trap Processors. The reasons as to why you are unable to view Trap Alarms in OpManager and their solutions can be checked here.

      Q. What are the alarm actions available?

      The alarm actions available in OpManager are: Add Note, Clear, Acknowledge, UnAcknowledge and Delete.

      Q. Why is Syslog alarm not raised if consecutive time and number of occurrences is enabled?

      Syslog alarm wont be raised if:

      a. The same syslog message is not generated for the number of consecutive times within the time interval as configured.

      Example: Consider the consecutive times to be '2' and the time interval to be 300 seconds. An alarm will be raised only if the syslog message is received twice within a time interval of 300 seconds.

      b. The received syslog does not match the below conditions in the rule created:

      • Syslog Facility
      • Syslog Severity
      • Match Text
      • Host


      Q. Does OpManager archive the syslog messages after processing? If so, where do I see and search for the received Syslog messages?

      No, syslog messages received are not normally stored after they are processed. However, syslog messages when received in the form of alarms are stored and can be accessed by going to Alarms -> Syslog Alarms in the OpManager UI.

      Q. Can I push events from my Cisco UCS device to OpManager as alerts?

      It is possible to push events from Cisco UCS Manager to OpManager as alerts. This can be enabled using the "Fault Settings" option in the hamburger menu of the UCS Snapshot page. You can choose one of two modes to raise alerts:

      1. By Query (Recommended option): Fetches events from the UCS Manager at a specific interval. Optimum interval is 300 seconds.
      2. Management API: Enables a dedicated event listener for the UCS device in OpManager, raising alerts in real-time. (Note: This is a resource-intensive option)

    • Notifications

      Q. What is the difference between "Run System Command" and "Run Program" notification profiles?

      In "Run System Command" profile, execution error or output can be selected to be appended in the alarm message by the user.

      In the "Run Program" profile, execution error or output is appended by default to the alarm message.

      Q. How to change the receiver Email ID for all notification profiles?

      Please follow the below steps to update the receiver email address in a bulk manner for all the notifications profiles:

      Go to Settings --> General Settings --> Privacy Settings --> PII Search --> Choose the search type as 'Email ID' --> Enter the old Email ID which you want to change --> It will list all the places where this Email ID is used --> Click on the three dots and enter the new Email ID and click on Update --> This will update the new Email ID in the all the places where the old Email ID was used.

      Q. Why is the Alert Notification SMS not received when 'Test SMS' is working?

      This happens when the alert notification message is more than 255 characters (which is as per SMPP v3.4 standard) but the target SMPP server is unable to retrieve the message with more than 255 characters from payload and deliver to recipient.

      Q. What is Delayed and Recurring trigger in notification profiles?

      Recurring Trigger : This option helps you delay the trigger for the notification profile by a an amount of time in order to provide a buffer time for the alarm to be cleared. If you do not want to trigger the notification profile if the alarm has been acknowledged in the meantime, you can select the 'Do not trigger if alarm is acknowledged' checkbox.

      Delayed Trigger : This option helps you re-trigger the notification profile at regular intervals, till the alarm is cleared. For instance, if you set trigger interval as 10 mins and restrict the number of triggers as 5 times, an alert will be notified every 10 mins, for 5 times or till alarm is cleared (whichever is earliest). If the number of triggers is set as empty, then alert will be notified for given interval, till the alarm is cleared. If you do not want to trigger the notification profile repeatedly if the alarm has been acknowledged, you can select the 'Do not trigger if alarm is acknowledged' checkbox.

      Q. What is the difference between Email based SMS and SMS?

      Email based SMS converts Emails into SMS messages. For example, OpManager sends an email to your SMS service provider ( They will convert your Email alert into an SMS compatible format and will push the notification to your intended recipient. This is not the case with SMS as there is no conversion involved and the alert is directly pushed as a text message.

      Note: To use these notification profiles, the Mail Server settings and the SMS server settings must be configured.

    • Workflows

      Q. What is Workflow?

      Workflow is a framework used to automate tasks. It lets the users define conditions, variables and actions for performing tasks. Workflow helps in hassle-free network management and it is completely code-free. To know more, click here.

      Q. What are workflow variables?

      Workflow Variables are used to append dynamic values in a field of task. For e.g, let us consider a workflow variable $[DeviceName].

          • When an alarm is triggered by the unavailability of a device, we can automate troubleshooting process with Ping Device command in workflow.
          • Using the DeviceName (for e.g, Windows-7187), the action Ping Device can be automated for that particular device.
          • On the other hand, by using the variable $[DeviceName], the same action can be automated for any device, as defined by the user.

      Click here for the list of workflow variables and their functions.

      Q. What are the types of triggers available in workflow?

          • Alarm Trigger - Workflows are triggered based on generated alarms
          • Schedule Trigger - Workflows are triggered on a specific time as defined by the user. To know more, click here.

      Q. Is there any workflow action available for add-on products?

      Workflow actions are available for Network Configuration Management (NCM) add-on. To know more, Click here.

      Q. What should I do when Ping task fails in a Linux machine and says "Device not Reachable"?

      Perform the following steps on your Linux machine:
      • Open OpManager, click on the Workflow tab.
      • Open the Workflow from the given list.
      • Click on the Ping Task and click on the edit icon.
      • Update the packet size value as 56 bytes.
      • Save the Workflow and execute it once again.

      Q. How can I automate the VM snapshot process of VMware using OpManager?

      In OpManager's workflows, there is a separate 'Take Snapshot'task available to make the process of getting VM snapshots much easier, without the help of any third-party tools. Simply go to Workflows → New Workflow, and the 'Take Snapshot' task will be available under the VMware section. You can configure an alarm or a time period as the trigger, to keep making snapshots at particular intervals.

    • Business Views

      A. Before checking the link connectivity status and traffic GUI in Business View, make sure:

      • There is active signal transmission between the devices present in the Business View.
      • There is an active physical connection between the devices that have been connected in the Business View using the connection link.

      In Business View, click on the link connecting the various devices to know the connectivity status and traffic. For the sake of simplification, prefer creating a layer 2 map with your devices and then converting them to Business View using the Save as Business View option in Layer2 Maps.

      Calculating the speed of the interface link in OpManager's business view:
      The interface link's speed is the average of InSpeed and OutSpeed of the interface. i.e, Speed = (InSpeed + OutSpeed)/2
      For Example:
      If InSpeed = 200 Mbps; OutSpeed = 300 Mbps.
      Then, Speed = (InSpeed + OutSpeed)/2 = (200 + 300)/2 = 500/2 = 250 Mbps.

      Q. Why the device icons in my BV are displayed in very smaller/negligible size?

      A. Business view is set to Fit to screen by default. Change this option to Normal Screen by clicking on the square icon near the zooming option. To magnify the view even further, press the "+" icon until a satisfactory size is achieved.

      Q. How can I edit multiple links, devices or shortcuts in a Business view?

      A. Select a Business View and click on the edit button. Now, press ctrl and choose multiple devices. Click on the Properties icon near the Grid icon and open the Bulk edit option. You can now edit multiple devices and links at once.

      Q. How to view the status of multiple site maps?

      A. A Business view can be embedded within a business view using Shortcuts. To create a shortcut, 

      • Create a new Business view or open an existing one and click on Edit.
      • Click on Add Shortcut icon on the toolbar, configure shortcut properties by assigning the Business view this shortcut icon should represent and click on Save.
      • Clicking on this shortcut will open the Business view that it is linked to. You can create multiple shortcuts in a single Business view.


      A. Connections between devices and shortcuts can be made by Links. To establish connection between devices/shortcuts, select a device and choose the Add Link icon from the toolbar.
        An alternate option is to drag the link button present at the top right corner of the source device's icon and drop it on the destination device's icon.

      A. To view the traffic/link arrow, open a Business view and click on Edit. Double click on a link connection and enable the Show Arrow option and press Save. Ensure there is traffic in the link for the arrow to be displayed.

      Q. Why am I not seeing Traffic Load Legend in a few Business view maps?

      A. The absence of a map legend can be attributed to the following reasons:

      1. Absence of link connection.
      2. when there is no traffic available
      3. The devices in the business view should not be in an unmanaged state.

      Q. How to provide user access only to the devices of a particular business view?

      A. Go to Settings > Basic Settings > User Management. If you wish to add a new user, click on Add User and fill the role and credentials listed under the User Details tab. If not, select an existing user from the list below.  Click on Scope tab. Here, a list of all the existing Business views can be found. Click on Selected Business Views and choose the business views that the user can access. 

    • Add-ons and Products Integration

      Q. How do I choose the version of ServiceDesk Plus (SDP) On-Premise to be integrated with my OpManager installation? Are there any restrictions on version compatibility between SDP and OpManager?

      There are a few version-related restrictions when it comes to integrating ServiceDesk Plus On-Premise with OpManager. Please refer the table below to know the compatible version of OpManager and SDP.

      SDP On-Premise version Suggested OpManager version Compatibility status
      10513 and below 11600-124096 Compatible
      11000 - 11127 124097 and above Compatible
      11128 - 11137 125214 and above Compatible
      11138 - 11206 125410 and above Compatible
      11300 and above 125452 and above Compatible

      On a general note, it is HIGHLY RECOMMENDED for users with SDP version 11.3 and above to integrate it with OpManager version 125452 and above to ensure the integration runs smoothly and to avoid any sort of compatibility issues.

      Known compatibility issues:

      OpManager version SDP On-Premise version Compatibility status Reason for incompatibility
      11600-124096 11000 and above Incompatible Issue with technician names in "Log a ticket" notification profile
      124097-125213 11128 and above Incompatible Internal issue with "Log a ticket" notification profile
      125214-125158 11138 and above Incompatible Configuration fails, "Internal server error" will be displayed
      Versions below 125392 (except 125367) 11200 and above Incompatible Configuration failure
      Any version below 125452 11300 and above Incompatible Request failure if integration uses v1 REST API version.

      Q. Can I send alerts to private channels on Slack via the OpManager-Slack Integration?

      You can send alerts to your private channels via the OpManager-Slack Integration if your OpManager build number is 125340 or greater, since this feature was introduced only in the mentioned version.

      If you use older versions of OpManager, you can enable this feature in your installation by upgrading to the latest build.

      Q. Why are some of the channels from my Slack workspace not being displayed in the Workflow/Notification Profile drop-down lists?

      Administrator users in OpManager can control which channels from Slack should be listed under the Workflow/Notification Profile window.

      • If you are an Administrator in OpManager, navigate to Settings → General Settings → Third-Party Integrations → Slack, click 'Configure Channels', select the channels you want to list and click Save.

        You can also access the Third-Party Integrations page by clicking on the Plug icon in the top-right corner of the web client.

      • If you are an Operator, contact your admin to get the necessary channel listed.

      Q. Why are some of my private channels not being displayed in OpManager?

      Once the Slack workspace is integrated with OpManager, all available public channels will be listed automatically under the 'Configure Channels' window. But in case of private channels, only those channels that have invited the OpManager-Slack app will be listed.

      Q. I have enabled a proxy server in my network, how can I configure the OpManager-Slack integration?

      In case you use a proxy server in your network to access the Internet, you need to configure the proxy server details in OpManager too since an Internet connection is needed for the OpManager-Slack Integration to work properly.

      Once you have the proxy server settings, navigate to Settings → General Settings → Proxy Server Settings in OpManager, click 'Enable' and provide the server details. Once done, you can proceed to configure and use the Slack Integration.

    • Security

      Q. Why is intermediate/root certificate required when I import the certificate?

      A. The intermediate and root certificates are needed to validate the server certificate provided. The server Certificate along with the intermediate and root certificates forms a complete chain, termed as 'Chain of trust', which establishes the authenticity of the certificate.

      Q.Why is the URL 'Not trusted', even after importing valid certificate?

      A. The URL shown as 'Not Trusted' is a browser specific feature. The reasons for a URL not shown as trusted can be one or both of the following:
      - You are using a Self-signed certificate (or) and internal organization CA issued certificate, which is not trusted by the browser, unless you manually import it into the browser's certificate store.
      -You are accessing the product with a Hostname or IP that is not specified in the Certificate's Common Name or the Subject Alternate Name (SAN) fields.

      Q. Is a self-signed certificate safe to use?

      A. Self signed certificate works the same way just like any CA issued certificate. The only downside to it is that it will not be trusted by the browsers as it is created by us and not issued by a valid CA, to make this trusted, the certificate can be added to the browser's certificate manager or added to all computers via Windows Group policy. This can be used if you are planning to access the application only within your organization.

      Q. How to change the self-signed certificate after server migration?

      To change the self-signed certificate after server migration:

      1. Please go to OpManager\conf and check if there is a file named "ITOMSelfSigned.pfx". If so, please delete or move the file to a different location.

      2. Now go to Settings -> General Settings -> Security Settings -> and click on "Create" under the "Self-Signed" option. This will create a new Self-Signed certificate with the new host name.

Video Zone
OpManager Customer Videos
Altaleb Alshenqiti - Ministry of National Guard - Health Affairs
  •  IT Admin from "Royal flying doctor service", Australia
     Jonathan ManageEngine Customer
  •  Michael - Network & Tech, ManageEngine Customer
     Altaleb Alshenqiti - Ministry of National Guard - Health Affairs
  •  David Tremont, Associate Directory of Infrastructure,USA
     Todd Haverstock Administrative Director
  •  Donald Stewart, IT Manager from Crest Industries
     John Rosser, MIS Manager - Yale Chase Equipment & Services
 Pricing  Get Quote