SolarWinds recommends that SolarWinds Platform administrators have local administrator privileges on the SolarWinds Platform server to ensure full functionality of local SolarWinds Platform tools. SolarWinds Platform user accounts limited to the SolarWinds Platform Web Console do not require local administrator privileges.

To use WPM recordings for Transaction Monitoring in Pingdom, you'll need an active Pingdom account to generate Pingdom API tokens for Web Transaction Recorders. See the WPM Getting Started Guide for details.

Not using Pingdom yet? Click here to start your free trial.

• x64 systems only
• Windows 10, 11
• Windows Server 2016 and 2019
  
  • WPM uses Electron 28.2.0 with Chromium 120.0.6099.227 and Node.js 18.18.2, which support only the operating systems listed above.

  • Keep Windows scale and layout settings set to 100% to support image validation.

The following macOS versions are supported:

• Sonoma
• Ventura
• Monterey
• Big Sur
• Catalina

• 80, for HTTP traffic
• 443, for HTTPS traffic
• 445, for automated remote deployment to target systems by the Agent installer via Microsoft-DS SMB file sharing.
• 17777, for SolarWinds traffic
• Two random ports between 1024—65535 for inter-process communication between recorders, probes, and drivers

  Configure firewalls to support binding for random ports 127.0.0.1:1024—127.0.0.1:65535.

• x64 systems only
• Windows 10*, 11*
• Windows Server 2016*, and 2019*

*SSL certificate authentication is not supported on some OS.

• 80, for HTTP traffic
• 443, for HTTPS traffic
• 17777, for SolarWinds traffic

Internet Explorer 11

If your organization requires an earlier IE version, use IE 11 Document Mode to emulate earlier versions.

• Windows 10*, 11*
• Windows Server 2016* and 2019*

WPM uses Electron 28.2.0 with Chromium 120.0.6099.227 and Node.js 18.18.2, which support only the operating systems listed above.

*Steps with certificate validation may interrupt playback, as described here.

Do not install WPM on domain controllers, or on Microsoft SharePoint, Microsoft Exchange, or BlackBerry servers.

• Accounts can access the remote administrator share.
• WPM Player service accounts have adequate rights to perform steps within recorded transactions.
• Client certificates required to play back recorded transactions are installed.

• 80, for outbound HTTP traffic
• 135, for executing remote code during WPM Player deployment
• 443, for outbound HTTPS traffic
• 445, for automated remote deployment to target systems by the Agent installer via Microsoft-DS SMB file sharing.
• 17777, for outbound SolarWinds traffic
• 17781, for bidirectional, server-initiated (passive) communication mode
• 17782, for bidirectional, player-initiated (active) communication mode
• 17783, for bidirectional, automatic WPM Player updates
• 17784, for bidirectional, inter-process communication between:
  • The WPM Player Playback service,
  • The WPM Domain Accounts Configuration Tool, and
  • The WPM Player Settings Tool.

In addition, allow a random port between 1024 and 65535 for inter-process communication between WPM players, probes, and drivers.

Configure firewalls to support the binding of a random port, between 127.0.0.1:1024 and 127.0.0.1:65535.

The following settings are updated during WPM Player deployment:

• Net.Tcp Port Sharing Service: The Startup Type is set to Manual on the SolarWinds Platform server and any Additional Polling Engines (APEs). On remote systems, the Startup Type is set to Automatic.
• SolarWinds WPM Playback Player service: A dependency with the Net.Tcp Port Sharing Service is added.

Internet Explorer 11

If your organization requires an earlier IE version, use IE 11 Document Mode to emulate earlier versions.