How to Install HP Insight Manager

— ny_wk

HP Systems Insight Manager (HP SIM) is HP's legacy management console for monitoring ProLiant servers, storage, and network devices from one Windows or Linux host. This guide walks through a clean, reliable HP Systems Insight Manager install on Windows Server — service account, SNMP, SQL Express, OpenSSH, the WMI Mapper, and post-install verification — and points you to the modern replacement so you do not deploy a dead end.

What HP Systems Insight Manager actually does

HP SIM is a central management application that discovers hardware in your environment and reports on health, firmware, and inventory. It collects data through three transports: SNMP (the classic ProLiant agent path), WBEM/WMI (via the WMI Mapper provider on Windows targets), and SSH for command execution. Combined with the HP ProLiant agents on each managed node, it gives you a single pane of glass for fault alerts and inventory.

It is not a hypervisor or a patching tool by itself, but it is the hub that HP's add-on plug-ins (Insight Control, Version Control Repository Manager) attach to.

Important: this is end-of-life software — know the modern path

HP Systems Insight Manager and the broader Insight Control suite reached end of support years ago, and HP's enterprise server business is now HPE. If you are building a new management environment, do not start with HP SIM. The current, supported tools are:

• HPE OneView — the modern infrastructure management platform that replaced HP SIM/Insight Control for Gen8 and newer hardware.
• HPE iLO Amplifier Pack — lightweight firmware and health management at scale, driven by the iLO out-of-band controller (Redfish API).
• HPE Integrated Lights-Out (iLO) — per-server out-of-band management built into the board.

The steps below remain valid for maintaining an existing HP SIM deployment or for legacy Gen6/Gen7 ProLiant fleets that predate OneView support. Treat any internet-facing install as a security liability and isolate it on a management network.

Prerequisites before you install HP Systems Insight Manager

Getting the groundwork right is what separates a five-minute install from a day of troubleshooting. Confirm all of the following first.

• A dedicated service account. Create a local or domain functional ID (the source environment used hpinsight) and grant it local Administrator rights on the management server.
• Set the password to never expire. This is critical: HP SIM stores this credential for its services and database connection. If the password expires or changes, the services fail to start and the console stops working until you re-enter it.
• A supported Windows Server with the latest service pack and a static IP.
• SNMP Service available to add as a Windows feature (covered below).
• A database. HP SIM bundles SQL Server Express; use it for small environments, or point the installer at an external SQL Server for larger fleets.
• Open the management ports in the firewall — notably TCP 50000/50001 (HP SIM web console), TCP 2301/2381 (System Management Homepage), UDP 161/162 (SNMP), and TCP 22 (SSH).

Step 1 — Add the SNMP Service feature in Windows

HP SIM relies on SNMP for ProLiant agent discovery, so install it before the application. Log in with your hpinsight service account.

1. Open Server Manager.
2. Go to Features > Add Features (on newer Windows Server builds this is Manage > Add Roles and Features > Features).
3. Select SNMP Service (include the SNMP WMI Provider if listed), then click Next.
4. Click Install, wait for completion, and click Close.

You can confirm it from an elevated PowerShell prompt:

1. List the feature state: Get-WindowsFeature SNMP-Service
2. Or install it entirely from the command line instead of the GUI: Install-WindowsFeature SNMP-Service -IncludeManagementTools

Step 2 — Configure SNMP community strings and security

SNMP will silently ignore packets from unknown hosts until you configure it, which is the single most common reason discovery fails. Set this before running the main installer.

1. Open the Services snap-in (services.msc) and double-click SNMP Service.
2. Go to the Security tab.
3. Under Accepted community names, click Add and create a community string with at least READ ONLY rights (for example public for read; use a non-default name in production).
4. Select Accept SNMP packets from these hosts and add the IP address of the HP SIM management server (and any monitoring relays).
5. Click OK, then restart the service: Restart-Service SNMP

Security note: SNMPv1/v2c community strings are transmitted in clear text. Never use public/private on a routed network — use a unique string and lock down the accepted-hosts list. Prefer SNMPv3 where the managed devices support it.

Step 3 — Run the HP SIM setup and choose the database

Insert or mount the HP SIM media and launch the installer.

1. Double-click setup.exe. If a prerequisite or .NET prompt appears, accept it.
2. On the launcher, click Install under HP Systems Insight Manager.
3. When asked about the database, select Install and use SQL Server Express if you have no external database server. For a production fleet, choose the external SQL Server option and supply its connection details.
4. Provide the password for the hpinsight service account and click Next. Re-confirm this account's password is set to never expire.
5. Wait several minutes while SQL Server Express installs — this is the longest unattended phase.

If the installer cannot reach or create the database, recheck that the service account has Administrator rights and that no prior SQL instance is conflicting on the default port.

Step 4 — Choose components: HP SIM, OpenSSH, and WMI Mapper

When the component selection screen appears, choose Custom and click Next, then select only what you need.

1. Ensure HP Systems Insight Manager, OpenSSH, and WMI Mapper are selected. Deselect anything you do not require to keep the footprint small.
2. Supply the service account password again when prompted and click Next, then Install.
3. On the access-rights screens, leave the explicit user box blank if Administrators already have access, and grant Local Access to Administrators for both secure and unsecured pages. Confirm port 2301 is enabled for the System Management Homepage.
4. For the certificate trust prompt, select Trust All for an isolated lab, or the stricter Trust by Certificate option in production.
5. Review the configuration summary and click Next, then let the core installer finish (several minutes). Click Finish.

Step 5 — Complete the OpenSSH and WMI Mapper installs

HP SIM chains its dependency installers. Work through them in order.

1. OpenSSH: click Next, enter the service ID password when asked, click Install, then Finish. This enables SSH-based actions against managed nodes.
2. WMI Mapper: click Next, accept the license agreement, choose the Complete setup type, click Install, wait, then Finish. The WMI Mapper translates WBEM queries into WMI so HP SIM can inventory Windows targets.
3. Proceed with the final HP SIM configuration: click Next through the screens, click Install, and wait while the installer runs — this stage can take several minutes.
4. Confirm every component shows installed successfully, then click Next.
5. Click Register Later at the registration prompt.
6. Select the Reboot option and click Finish. A restart is required for all services to initialize cleanly.

Common pitfalls when installing HP Systems Insight Manager

These are the issues that trip up most administrators. Knowing them in advance saves a reinstall.

• Expiring service-account password. The number-one cause of a console that worked yesterday and is dead today. Set Password never expires and exempt the account from any domain rotation policy, or back it with a managed service account.
• SNMP not accepting packets. If discovery returns nothing, you almost always forgot to add the management server's IP under Accept SNMP packets from these hosts, or the community string does not match the agents.
• Firewall blocking ports. Console unreachable usually means TCP 50000/50001 is closed; missing agent pages mean 2301/2381 is blocked.
• SQL Express conflicts. A pre-existing SQL instance or a leftover failed install can block the bundled Express setup. Remove orphaned instances first.
• Installing as the wrong user. Always run setup logged in as the service account with Administrator rights; running as a different admin can mismatch the service identity.
• Skipping the reboot. Several services only register after a restart — do not skip it.

Step 6 — Verify the HP Systems Insight Manager installation

After the reboot, confirm the platform is actually healthy rather than assuming the installer succeeded.

1. Check the services are running. In services.msc confirm the HP SIM service and the WMI Mapper / OpenSSH services show Started / Automatic. From PowerShell: Get-Service | Where-Object {$_.DisplayName -like "*Insight*"}
2. Open the web console. Browse to https://localhost:50000 (or the server name) and log in with the hpinsight account. The dashboard should load without a certificate or service error.
3. Confirm the ports are listening: netstat -ano | findstr "50000 2301"
4. Run a test discovery. Go to Options > Discovery, add a known ProLiant node's IP, and run it. A successful discovery returns the system type, health status, and inventory.
5. Validate SNMP end to end from the management server: snmpwalk -v2c -c <community> <target-ip> (or use the bundled SNMP test tool). A response confirms the community string and accepted-hosts list are correct.

If discovery succeeds and the dashboard shows green health on a managed node, your HP Systems Insight Manager install is complete and functional.

Key Takeaways

• Create a dedicated service account (for example hpinsight) with local Administrator rights and a non-expiring password — this is the most common cause of failures.
• Install and configure the SNMP Service first, adding the correct community string and the management server's IP to the accepted-hosts list.
• Use bundled SQL Express for small environments or an external SQL Server for larger fleets, and install OpenSSH plus the WMI Mapper for full target coverage.
• Open the right ports (50000/50001, 2301/2381, 161/162, 22), reboot after install, and verify with a test discovery and the web console.
• HP SIM is end-of-life — keep legacy fleets running with it, but plan migrations to HPE OneView, iLO Amplifier Pack, or iLO/Redfish for current hardware.

Frequently Asked Questions

Why does HP SIM stop working after a password change?

HP SIM stores the service account credential for its Windows services and its database connection. When that password expires or is changed, the services can no longer authenticate and the console fails. Set the account's password to never expire and exclude it from rotation policies, or re-enter the new password in the service and database configuration immediately after any change.

What ports does HP Systems Insight Manager use?

The web console listens on TCP 50000/50001, the System Management Homepage on 2301/2381, SNMP on UDP 161 (queries) and 162 (traps), SSH on TCP 22, and WBEM/WMI on 5988/5989. Open these in the firewall and restrict them to your management network.

Is HP Systems Insight Manager still supported?

No. HP SIM and the Insight Control suite are end-of-life, and HP's server line is now HPE. For current hardware use HPE OneView for infrastructure management, HPE iLO Amplifier Pack for firmware and health at scale, and iLO/Redfish for out-of-band control. Use HP SIM only to maintain existing legacy ProLiant deployments.

Do I need SQL Server to install HP SIM?

Yes — HP SIM requires a database. The installer can deploy SQL Server Express automatically, which is fine for small environments. For larger fleets or where you already run SQL Server, point the installer at an external instance for better performance and centralized backups.

For more system administration walkthroughs and server tutorials, subscribe to @explorenystream on YouTube.