Solarwinds Npm Offline Installer __top__

Here’s a concise review of the SolarWinds Network Performance Monitor (NPM) Offline Installer, based on common admin use cases and feedback.

Part 9: Security Best Practices for Offline npm Deployments

Deploying an offline npm installer does not automatically make you secure. Follow these rules:

1. Source Integrity: Always verify the digital signature of the offline installer. Right-click > Digital Signatures > highlight SolarWinds, Inc. > Details – ensure "The digital signature is OK."
2. Antivirus Scan Before Execution: Scan the installer on a jump box using updated definitions (e.g., Windows Defender offline scan). In air-gapped networks, use a dedicated malware scanning station.
3. Service Account Hardening: Use a Managed Service Account (gMSA) rather than a standard domain user. The offline installer supports gMSA if the server can contact a domain controller (does not require internet).
4. Database Encryption: Enable TDE (Transparent Data Encryption) on the SQL database post-installation. The offline installer does not do this by default.
5. Audit Logging: Configure Windows Event Forwarding (WEF) to send SolarWinds service logs to a central SIEM. Since you’re offline, use a local collector.

Option 4: Internal IT / Documentation Blurb (e.g., Confluence, Slack)

Title: SolarWinds NPM Offline Installer – Quick Reference

Content: If you're setting up SolarWinds NPM in a restricted environment, use the offline installer to avoid dependency on internet access during installation.

📍 Where to get it:

• Log into the SolarWinds Customer Portal
• Go to Downloads > Network Performance Monitor
• Select the version → Download Offline Installer (executable)

⚠️ Note: The offline installer is large (2.5–4 GB). Use a USB drive or internal share to transfer it to your target server. Run as Administrator.

The SolarWinds Network Performance Monitor (NPM) Offline Installer is a comprehensive package designed for environments with limited or no internet connectivity (dark sites). This report details the acquisition, requirements, and deployment process for the offline installer. 1. Executive Summary

SolarWinds NPM is a network monitoring solution that provides visibility into device health and performance. The offline installer is an all-in-one executable that includes the necessary SolarWinds Platform (formerly Orion) components and the NPM module, eliminating the need for the server to download files during the installation process. 2. Procurement and Acquisition

The offline installer is not available on public download pages and must be accessed through the SolarWinds Customer Portal. solarwinds npm offline installer

Step 1: Log in to the Customer Portal with valid credentials.

Step 2: Navigate to Downloads > Active Maintenance & Downloads.

Step 3: Select Network Performance Monitor (NPM) from the product list. Step 4: Choose the Offline Installer option.

Note: The file size is significantly larger (typically several GBs) compared to the lightweight online installer because it contains all prerequisites and MSI files. 3. Pre-Installation Requirements

Before running the installer, ensure the destination server meets the following criteria:

Operating System: Windows Server 2016, 2019, or 2022 (latest service packs recommended).

Hardware: Minimum 4 CPU cores and 16GB RAM for small environments; requirements scale with the number of polled nodes.

Database: A dedicated instance of Microsoft SQL Server (2016 SP1 or later) is required. Here’s a concise review of the SolarWinds Network

Permissions: Local Administrator rights on the server and db_owner privileges on the SQL instance.

Security: Passwords for the SolarWinds Platform must be at least 12 characters and include uppercase, lowercase, and special characters. 4. Installation Procedure

The offline installation follows a specific workflow to ensure the platform is correctly initialized:

Transfer: Move the downloaded .exe file to the offline server via secure media (e.g., USB or internal file transfer). Execution: Run the installer as an Administrator.

Product Selection: Select Network Performance Monitor and any additional modules you are licensed for.

Prerequisite Check: The installer will scan the system for missing components (like .NET Framework or IIS). Since this is the offline version, it will install these from the local package.

Configuration Wizard: After the files are extracted, the wizard will prompt for: Database Settings: Connection details for your SQL Server.

Website Settings: Binding to specific IP addresses or ports (default is 80/443). Source Integrity: Always verify the digital signature of

Service Settings: Configuration of the SolarWinds Information Service and Job Engine. 5. Post-Installation and Maintenance

Licensing: Because the server is offline, you must perform offline activation. This involves generating a unique machine key, uploading it to the Customer Portal from an internet-connected device, and downloading a license file to import back into the NPM server.

Reporting: Once installed, users can create custom table or chart reports via Settings > All Settings > Manage Reports to visualize network data.

Troubleshooting: Logs are primarily located in C:\ProgramData\SolarWinds\Logs. If services fail to start, the SolarWinds Orion Core Services can be repaired via the Windows Control Panel. Install SolarWinds Platform products in a new environment

4. Disaster Recovery Speed

If your primary npm server crashes, restoring from backup is one option. But sometimes you need a clean, bare-metal rebuild. An offline installer on a USB key can restore a monitoring environment in 30 minutes without waiting for gigabytes to download over a constrained WAN link.

Step 8: Complete Installation

After activation, proceed. The installation will take 15–30 minutes. Once finished, reboot the server, and access the NPM web console at https://yourserver:port.

Phase 1: Pre-Installation (Local Machine)

1. Copy the SolarWinds-NPM-Offline.exe to C:\Temp\ on the target server.
2. Right-click the file > Properties > check "Unblock" (for files copied from a network share).
3. Run as Administrator to launch the installer. (Or use command line for silent install – see Part 6).

Troubleshooting Common Offline Issues

Even with careful planning, offline installations can fail. Common errors include:

• "Unable to connect to the database": Often caused by the SQL Server Browser service being disabled or firewall rules blocking the dynamic ports.
• Certificate Errors: SolarWinds uses self-signed certificates for internal communication. If your organization pushes a strict Group Policy Object (GPO) regarding SSL/TLS protocols, the installer might fail to configure the website. Ensure your IIS SSL settings are compatible with the default Orion configurations.
• The "Stuck" Extraction: If the installer hangs during the "Extracting files" phase, it is usually due to antivirus scanning every file as it unzips. Temporarily disabling real-time protection during the extraction (and re-enabling it immediately after) is a standard troubleshooting step.

Part 10: Frequently Asked Questions (FAQ)