ManageEngine OpManager Setup Guide (Full Step-By-Step Tutorial!)

Download OpManager from the Official Site

OpManager is ManageEngine's network and server monitoring tool — it watches routers, switches, firewalls, servers and virtual machines and raises an alarm when something goes down or crosses a limit. Download the Windows installer only from ManageEngine's official website (manageengine.com, Network Monitoring / OpManager section), and install it on a Windows PC or server that stays powered on and can reach every device you want to monitor.

Install OpManager on Windows

Run the downloaded installer and follow the wizard: accept the licence agreement, choose the edition (30-day trial or Free) and the installation folder, and keep the default web server port 8060 unless something else on that machine already uses it. OpManager bundles its own PostgreSQL database, so there is no separate database setup for a normal installation. Let the wizard finish — OpManager installs and runs as a Windows service, so it keeps monitoring even when nobody is logged in.

Open the Console and Log In

Open a browser and go to the OpManager web console. On the OpManager server itself the address is:

http://localhost:8060

From another PC on the network, replace localhost with the OpManager server's name or IP address. Log in with the default user name and password — both are admin — and then change the admin password immediately from the user profile. A monitoring server that still uses its default password is an open door into your whole network map.

Add SNMP and WMI Credentials

Discovery only finds devices — credentials are what let OpManager actually read them. Add your credentials first, under Settings → Discovery → Credentials. For routers, switches, firewalls and printers, create an SNMP credential: version 1/2c uses the device's community string, and SNMP v3 uses a user name with authentication (and optionally privacy) — the device itself must have SNMP enabled, and UDP port 161 must not be blocked between OpManager and the device.

For Windows servers and PCs, create a WMI credential. The user name goes in domain format — exactly the format the video highlights:

DOMAIN\username

Use an account with administrator rights on the target machines, and make sure the Windows Management Instrumentation (WMI) and RPC services are running on them. CLI credentials (SSH/Telnet) can be added the same way for devices you want to poll over the command line.

Discover Your Devices

Now run discovery: open the Discovery section and add a discovery for a single IP address, an IP range, or a whole subnet. Select the credentials you created in Step 4 so OpManager can classify each device properly the moment it finds it. OpManager first checks reachability (ICMP ping), then uses the credentials and device templates to sort what it finds into categories — servers, routers, switches, firewalls, printers, workstations and more.

Confirm the Monitors Are Reporting

Do not stop at "device discovered". Open a few discovered devices and open their snapshot pages: you should see availability status plus performance monitors — CPU, memory and disk for servers, and interface traffic/utilisation for network devices — actually polling and updating. The device template matched during discovery decides which monitors get attached, so a correctly classified device gets the right monitors automatically.

If a device shows as unknown or its monitors return no data, the cause is almost always one of three things: SNMP is not enabled on the device, the community/credential is wrong, or a firewall is blocking the polling (UDP 161 for SNMP, TCP 135/445 for WMI). Fix the credential or the device-side setting, re-test the credential, and rediscover that device.

Check Thresholds and Alarms

Monitors raise alarms when a value crosses its threshold — for example CPU staying above a set percentage, a disk filling up, or a device stopping responding. Alarms carry severities (Service Down, Critical, Trouble, Attention and Clear), so the loudest alarms mean a device is down and the quieter ones are early warnings. Review the default thresholds on your important devices and adjust the noisy ones now, while the system is new — an alarm list full of false alarms teaches everyone to ignore alarms, including the real ones.

Turn On Notifications That Reach You

An alarm that only sits inside the console helps nobody at 2 AM. Finish the setup with a Notification Profile: configure your mail server settings in OpManager, create a profile that emails you (and your team) when alarms of the severities you choose are raised, and attach it to your critical devices. Then test it end to end — trigger a harmless test condition, such as shutting down a test device or unplugging a non-critical one, and confirm the alarm appears in the console and the email actually arrives. Only after that test is your OpManager setup genuinely complete.