ACM 2019.2 System Requirements

Released June 6, 2019

Updated July 2, 2019

SolarWinds Application-centric Monitor (ACM) extends the functionality of Network Operations Manager (NOM) or Network Automation Manager (NAM) to monitor application health, performance, and web performance in your on-premise, cloud, or hybrid environment. Before adding ACM to your environment, install NOM or NAM.

These recommended system requirements are for ACM installed on Orion Platform 2019.2.

For additional information on requirements and configurations, see the Multi-module system guidelines. You should also review your product administration guides and release notes for the exact product requirements beyond these minimums. We also recommend reviewing the ACM 2019.2 Release Notes.

Software requirements

The following table lists software requirements and recommendations for a SolarWinds installation on both physical and virtual computers.

Software Requirements
Operating system
  • Windows Server 2016
  • Windows Server 2019

Desktop operating systems, such as Windows 10, 64-bit Pro or Enterprise are supported for evaluation environments only. To make a smooth transition from your evaluation to production deployment, SolarWinds recommends that you avoid installing evaluations on desktop operating systems.

Support differences between Orion Agents and Orion Platform products

  • You cannot install Orion Platform products on domain controllers. Exception: You can install Orion Agents on domain controllers.
  • You cannot install Orion Platform products or any scalability engines on Microsoft SharePoint, Microsoft Exchange, or BlackBerry servers. Exception: You can install Orion Agents on SharePoint, Exchange, or Blackberry servers.

End-of-support notice: Orion Platform 2019.2 products are no longer compatible with Windows Server 2012 and 2012 R2. To use the new features introduced in Orion Platform 2018.4 or later, upgrade your environment at your earliest convenience.

Operating system languages
  • English (UK or US)
  • German
  • Japanese
  • Simplified Chinese
IP address version
  • IPv4
  • IPv6
  • Dual stack

CIDR notation is not supported for IPv6 addresses.

Web server

If you are not using Windows Authentication, make sure Anonymous Authentication is enabled for the SolarWinds NetPerfMon website. Anonymous Authentication is used with the default forms-based authentication.

IIS is installed by the SolarWinds Orion Installer. You can install this software manually to reduce installation time.

Microsoft .NET Framework

.NET 4.8

Run the same version of. NET on your primary server and any Additional Polling Engines (APEs) or Additional Web Servers (AWS) in the environment.

SolarWinds recommends installing .NET on your primary Orion server and all scalability engines before installing SAM. See this article for details.

Services

If using the Syslog or SNMP Traps feature of the Orion Platform, make sure the following services are running after installation is complete:

  • SolarWinds Syslog Service
  • SolarWinds Trap Service
Orion Web Console browser

Orion Platform products support the two most recent versions of the following web browsers available at the release date:

  • Firefox
  • Chrome

The following browsers are also supported:

  • Microsoft Edge
  • Microsoft Internet Explorer 11 or later with Active scripting

Do not enable Enterprise Mode on Internet Explorer. This setting forces Internet Explorer to emulate version 7, which is not supported.

Account privileges

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

Hardware requirements

Return to top

The following table lists minimum hardware requirements and recommendations for your SolarWinds Orion server on physical computers, virtual computers, and cloud instances. Use the minimum hardware configuration if you are evaluating the product or do not anticipate heavy usage.

SolarWinds strongly suggests using the recommended hardware configuration to avoid potential performance issues caused by a heavy load or custom configurations such as increased data retention or more frequent polling intervals.

Installing multiple Orion Platform products on the same computer may change the requirements.

Hardware requirements are listed by deployment size, based on SAM license levels. CPU recommendations for XL deployments use the PassMark Score. To learn more, see Pass Mark Performance Test (Copyright © 2019 PassMark® Software, obtained at https://www.cpubenchmark.net/high_end_cpus.html on April 24, 2019).

Feature AL150 - AL300 AL700 — AL1100 AL1500 — ALX
CPU Quad core processor or better Quad core processor or better Quad core processor or better
Do not enable Physical Address Extension (PAE).
Hard drive space

10 GB minimum

20 GB recommended

15 GB minimum

40 GB recommended

40 GB minimum

100 GB recommended

SolarWinds recommends two 146 GB 15K (RAID 1/Mirrored Settings) hard drives with a dedicated drive for the server operating system and Orion Platform installation.

Some common files may need to be installed on the same drive as the server OS. You may want to move or expand the Windows temporary directories.

Memory

10 GB minimum

20 GB recommended

15 GB minimum

40 GB recommended

30 GB minimum

40 GB recommended

Orion database server requirements

Return to top

The following table lists software and hardware requirements for your SolarWinds Orion database server using SAM license levels.

The following table lists software and hardware requirements for your SolarWinds Orion database server using SolarWinds SAM license levels.

Requirements AL150 - AL300 AL700 — AL1100 AL1500 — ALX
SQL Server

Express, Standard, or Enterprise versions of the following:

  • SQL Server 2014
  • SQL Server 2014 SP1
  • SQL Server 2014 SP2
  • SQL Server 2016
  • SQL Server 2016 SP1
  • SQL Server 2016 SP2
  • SQL Server 2017 (including installations on Linux)

End-of-support notice: Orion Platform 2019.2 products are not compatible with SQL Server 2012, 2012 SP1, 2012 SP2, 2012 SP3, and 2012 SP4. To use new features introduced in Orion Platform 2018.4 or later, upgrade your environment at your earliest convenience.

SolarWinds recommends that you use Express versions only for evaluations and very small environments.

Recommendations

  • Use the 64-bit version of SQL Server.
  • Use the Simple database recovery model to ensure best performance.
  • You can use the Full database recovery model if your Orion Database is hosted on a SQL cluster or if you use Always On Availability. However, you must back up your database regularly and ensure that the volume where you store transactions log has free space at least equal to or greater than the size of the Orion database. Transaction logs will continue to grow indefinitely until a database backup is performed and transactions are committed to the database. SolarWinds recommends daily database backups if using the Full database recovery model.
SQL Server collation
  • English with collation setting SQL_Latin1_General_CP1_CI_AS
  • German with collation setting German_PhoneBook_CI_AS
  • Japanese with collation setting Japanese_CI_AS
  • Simplified Chinese with collation setting Chinese_PRC_CI_AS

SolarWinds supports a case insensitive (CI) database on an CS SQL Server.

SolarWinds products do not support case-sensitive databases.

CPU Quad core processor or better Dual quad core processor or better Dual quad core processor or better
Hard drive space

20 GB minimum

40 GB recommended

50 GB minimum

100 GB recommended

100 GB minimum

400 GB recommended*

*SolarWinds recommends the following hard drive configuration for AL1500 — ALX deployments:

  • A hardware RAID Controller with a battery backed-up write back cache
  • Disk Subsystem 1 Array 1: 2x 146 GB 15K disks RAID 1 (mirroring) for the OS
  • Disc Subsystem 2 Array 2: 2x 146 GB 15K disks RAID 1 (Pagefile + Extra Storage)
  • Disk Subsystem 3 Array 3: with 6x 15k 146 GB or 300 GB disks configured in a RAID 1+0 array for your SQL MDF and FILEGROUPS.
  • Disk Subsystem 4 Array 4: with 4x 15k 146 GB or 300 GB disks configured in a RAID 1+0 array for your SQL LDF Transaction LOG file
  • Disk Subsystem 5 Array 5: with 4x 15k 146 GB or 300 GB disks configured in a RAID 1+0 array for your tempdb data file
  • Disk Subsystem 6 Array 6: with 4x 15k 146 GB or 300 GB disks configured in a RAID 0 array for your tempdb log file
  • Due to intense I/O requirements, a RAID 1+0 drive is strongly recommended for the SolarWinds database, data, and log files with a dedicated drive for the server OS and tempdb files.
  • Other RAID configurations can negatively affect SQL Server performance.
  • Mirrored drives for the OS and RAID 1+0 for database data files are recommended.
  • Solid state drives (SSD) are recommended for all components.

Some common files may need to be installed on the same drive as your server operating system. You may want to move or expand the Windows or SQL temporary directories.

Memory

AL150

4 GB minimum

8 GB recommended

16 GB minimum

64 GB recommended

64 GB minimum

128 GB recommended

AL300

16 GB minimum

32 GB recommended

Authentication Either mixed-mode or Windows authentication. If you require SQL authentication, you must enable mixed mode on your SQL server.
Other software

If you are managing the SolarWinds Orion database, SolarWinds recommends installing the SQL Server Management Studio component. The Orion Installer adds the following x86 components if they are not found on the Orion database server:

  • SQL Server System Common Language Runtime (CLR) Types. Orion Platform products use secure SQL CLR stored procedures for selected, non-business data operations to improve overall performance.
  • Microsoft SQL Server Native Client
  • Microsoft SQL Server Management Objects

For remote execution of PowerShell scripts, PowerShell 2.0 or later is required on the Orion server, Additional Polling Engines, and target servers.

You cannot share the SolarWinds Orion database with Microsoft SharePoint, Microsoft Exchange, or BlackBerry servers.

Amazon RDS deployments

Return to top

To deploy your Orion Platform using Amazon RDS, consider using the following templates, listed according to NPM license levels:

Requirements

Small

AL150, AL300, AL700

Medium

AL1100, AL1500

Large

AL2500, ALX

XL

(UP TO 150,000 COMPONENTS)

Orion server m4.large

m4.xlarge

Recommended: m5d.xlarge with SDD drive

m4.2xlarge

Recommended: m5d.2xlarge with SSD

m5.4xlarge

Recommended: m5d.2xlarge with SSD

Orion database server r4.xlarge r4.xlarge

r3.2xlarge

Recommended: r5d.xlarge with SSD

db.r4.8xlarge

Recommended: R5d.12xlarge

Amazon RDS db.r4.xlarge db.r4.2xlarge db.r4.4xlarge db.r4.8xlarge
Additional Polling Engines Only relevant for environments that monitor over 12,000 elements. m5.xlarge

Microsoft Azure deployments

Return to top

To deploy your Orion Platform product on Microsoft Azure, consider using the following instance types, listed according to NPM license levels.

Require-
ments

Small

SL100, SL250, SL500

Medium

SL2000

Large

SLX

Orion Platform server

DS12_v2

4 CPU

16 GB RAM

150 GB disk

DS12_v2

4 CPU

16 GB RAM

150 GB disk

DS4_v2

8 CPU

32 GB RAM

150 GB disk

SolarWinds Orion database server

DS4_V2 Standard

8 CPU

28 GB RAM

System SSD 126 GB (included in Azure VM instance) + 1 TB for SQL database (included in Azure SQL Server Computer)

r4.D12_v2

4 CPU

30.5 GB RAM

System SSD 80 GB (included in D12_v2) + Data Azure Storage Disk Volume 500 GB

D4_v2

Azure Storage Disk with Provisioned IOPS recommended

8 CPU

61 GB RAM

System SSD 160 GB (included in D4_v2) + 1x Data EBS Volume 150 GB + 2x Data Azure Storage Disk Volume 500 GB

Azure SQL requirements

All installed products must run on Orion Platform 2019.2 (DPAIM 11.2, EOC 2.2, ETS 11.0.8, VMAN 8.5, IPAM 4.9, NCM 8.0, NPM 12.5, NTA 4.6, LA 2.1, Patch Manager 2.1.7, SAM 6.9, SCM 1.2, SRM 6.9, UDT 3.0).

The time zone setting of the Orion server must match the Azure SQL time zone (UTC).

When deploying Azure SQL and creating a new user in the Configuration wizard, SA account credentials are required in the Configuration wizard.

Azure SQL tiers if using memory-optimized tables*

DTU Tier P1

vCore Business Critical Gen4 Tier 1

vCore Business Critical Gen5 Tier 2

DTU Tier P2

vCore Business Critical Gen4 Tier 2

vCore Business Critical Gen5 Tier 2

DTU Tier P4

vCore Business Critical Gen4 Tier 4

vCore Business Critical Gen5 Tier 4

*Memory-optimized tables, also known as In-Memory OLTP is a feature available in MS SQL Server 2016 and 2019 that improves the performance of transaction processing, data ingestion, data load, and transient data scenarios.
Azure SQL tiers without memory-optimized tables

DTU Tier S3

DTU Premium Tier P1

vCore General Purpose Tier 2

vCore Business Critical Tier 2

DTU Tier S3

DTU Premium Tier P1

vCore General Purpose Tier 2

vCore Business Critical Tier 2

DTU Tier S4

DTU Premium Tier P2

vCore General Purpose Tier 2

vCore Business Critical Tier 2

Server port requirements

Return to top

  • Ports 4369, 25672, and 5672 are opened by default on the main Orion server for RabbitMQ messaging. These ports can be blocked by the firewall. When running SolarWinds High Availability, ensure ports 4369 and 25672 are open.

  • RPC ports > 1024 (TCP, bidirectional) is used by the Job Engine v2 process to communicate with Windows nodes.

Port Port Service/Process Direction Description
User-defined, default: 22 SSH

SolarWinds Job Engine v2

IIS

Outbound from the Orion server to the device

Access ASA devices through the CLI

Device-based encryption

25 TCP SolarWinds Alerting Service V2 Outbound SMTP port for non-encrypted messages
53 UDP SolarWinds Job Engine v2 Bidirectional Resolve DNS queries
80 TCP IIS Inbound

Default Additional Web Server (AWS) port. If you specify any port other than 80, you must include that port in the URL used to access the Orion Web Console. For example, if you specify 192.168.0.3 and port 8080, the URL used to access the Orion Web Console is http://192.168.0.3:8080.

Open the port to enable communication from your computers to the Orion Web Console.

The port might also be used for Cisco UCS monitoring.

135 TCP Microsoft EPMAP (DCE/RPC Locator service) Bidirectional

WMI uses TCP Port 135 to initiate communication with the remotely managed host, then switches to any random high port anywhere between TCP ports 1024 — 65535. Click here for details.

161 UDP

SolarWinds Job Engine v2

SolarWinds Cortex (communication)

Bidirectional

Send and receive SNMP information.

SNMP v1 and v2 are unencrypted.

SNMP v3 uses AES and 3DES encryption.

162 UDP

SolarWinds Trap Service

SNMP Informs

Bidirectional Receive trap messages
443 TCP IIS Bidirectional

Default port for https binding. Also used for bi-directional ESX/ESXi server polling, or for Cisco UCS monitoring.

SSL encryption

465 TCP SolarWinds Alerting Service V2 Outbound

SMTP port used to send TLS-enabled email alert actions

SSL encryption

514 UDP SolarWinds Syslog Service Bidirectional Receive syslog messages
587 TCP SolarWinds Alerting Service V2 Outbound SMTP port used to send TLS-enabled email alert actions
1433 TCP

SolarWinds Administration Service

SolarWinds Alerting Service V2

SolarWinds Information Service

SolarWinds Information Service V3

SolarWinds Orion Module Engine

Outbound

Communication between the Orion Server and the Orion database server.

TLS encryption

1434 UDP

SolarWinds Administration Service

SolarWinds Alerting Service V2

SolarWinds Information Service

SolarWinds Information Service V3

SolarWinds Orion Module Engine

SQL Server Browse Service

Bidirectional Communication with the SQL Server Browser Service to determine how to handle certain non-standard SQL Server installations. Required only if your Orion database server is configured to use dynamic ports.
1801 TCP MSMQ Bidirectional

MSMQ WCF binding with WCF encryption

5671 TCP

RabbitMQ

Bidirectional

For encrypted RabbitMQ messaging (AMQP/TLS) into the main polling engine from all scalability engines.

TLS 1.2 encryption

17777 TCP

SolarWinds Orion Module Engine

SolarWinds Information Service

SolarWinds Information Service V3

SolarWinds Cortex (communication)

Bidirectional

Communication between services and SolarWinds Orion module traffic.

Communication between the Orion Web Console, the main polling engine, and all scalability engines.

Communication between the main server and pool members.

Encryption:

  • RSA handshake, AES 256 communication using WCF
  • TLS 1.2 with Cortex
17778 HTTPS SolarWinds Agent Bidirectional

Required to access the SWIS API and agent communication. Also used for outbound communication with orchestrator machines to monitor container services.

SSL encryption

17799 HTTPS Container service monitoring Bidirectional Communication with orchestrator machines.

See SolarWinds Port requirements for a comprehensive list of port requirements for SolarWinds products.

Optional, individual components, such as Orion agents and High Availability, have additional port requirements.

SAM port requirements

Return to top

Review and open ports for SAM to support communication for the main polling engine, Orion database server, Additional Polling Engines (APEs), and Additional Web Servers (AWS).

SAM component monitor ports

Component/ Monitor Port Type Description
DHCP User Experience Monitor 67 UDP Used for the DHCP request.
DHCP User Experience Monitor 68 UDP Used for the DHCP response.
Directory Size Monitor See SAM WMI requirements.
DNS Monitor DNS User Experience Monitor 53 TCP/UDP Used for DNS queries.
Download Speed Monitor 19 Used for the character generator service.
ESX Hardware Monitoring 5989 Used to collect vCenter data via API.

File Age Monitor

File Change Monitor

File Existence Monitor

Files Size Monitor

File Count Monitor

See SAM WMI requirements. See also Poll devices with SolarWinds Orion agents.
FTP Monitor FTP User Experience Monitor 21 Used for FTP sessions
HTTP Form Login Monitor HTTP Monitor TCP Port Monitor 80 Used for HTTP forms-based login sessions.
HTTPS Monitor 443 Used by websites.
IMAP4 Monitor 143 and 993 IMAP4 Used to communicate with a Microsoft Exchange mail server.
IMAP4 Port sessions 143 IMAP4 Used for IMAP 4 sessions.
IMAP4 Port sessions 585 IMAP4 For Secure IMAP (IMAP4-SSL), use port 585.
IMAP4 Port sessions 993 IMAP4 For IMAP4 over SSL (IMAPS), use port 993.
IMAP4 User Experience Monitor 25 SMTP Used to communicate with a Microsoft Exchange mail server.
LDAP User Experience Monitor 389 Used for LDAP connections.
LDAP User Experience Monitor 636 For LDAP over SSL, use port 636.
Linux/Unix Script Monitor Ports 22 Used for the SSH connection.
NNTP Monitor 119 UDP Used for Network News Transfer Protocol (NNTP) connections.
ODBC User Experience Monitor 1630 TCP Used with synthetic transactions to test the abilities of an Open Database Connection (ODBC)-accessible database such as MySQL.
Oracle User Experience Monitor 1521 TCP The Oracle SQL*Net Listener allows Oracle client connections to the database over Oracle's SQL*Net protocol. You can configure it during installation. To reconfigure this port, use Net Configuration Assistant.
Oracle User Experience Monitor 1526 TCP The Oracle SQL*Net Listener allows Oracle client connections to the database over Oracle's SQL*Net protocol. You can configure it during installation. To reconfigure this port, use Net Configuration Assistant.
Performance Counter Monitor See description TCP

This monitor uses RPC, requiring the following ports:

TCP/135

RPC/named pipes (NP) TCP 139

RPC/NP TCP 445

RPC/NP UDP 137

RPC/NP UDP 138

POP3 Monitor See Description

This component monitor uses the following ports to communicate with Microsoft Exchange mail servers.

  • 102 X.400 MTA
  • 110 POP3
  • 119 NNTP
  • 143 IMAP4
  • 389 LDAP
  • 563 POP3 over SSL
  • 636 LDAP over SSL
  • 993 IMAP4 over SSL
  • 995 Secure POP3 over SSL

POP3 Monitor

POP3 User Experience Monitor

110 (default) Used for POP3 connections.

POP3 Monitor

POP3 User Experience Monitor

995 Used for Secure POP3 (SSL-POP) connections.
POP3 User Experience Monitor 110 (default) Use 110 for POP3 sessions, by default. For Secure POP3 (SSL-POP) use port 995. It also uses an SMTP Port, port 25 for SMTP sessions.
RADIUS User Experience Monitor

1812

1645

Used to authenticate RADIUS protocols, along with port 1813.

Cisco devices may require port 1645 or 1646.

RWHOIS Port Monitor 4321 Used to test the ability of an RWHOIS server to accept incoming sessions.
SMTP Monitor 465 SMTP Used for Secure SMTP (SSMTP).
SNMP Monitor 444 SNMP Used to test the ability of an SNMP server to accept incoming sessions.
SQL Server User Experience Monitor 1433 This component monitor only works if Microsoft SQL Server uses the default port, 1433. For a Microsoft SQL Server database that uses a non-standard port, you cannot monitor it using the SQL Server User Experience monitor. Instead, use the ODBC User Experience monitor to manually define a connection string that supports communication with the Microsoft SQL Server on its custom port.
TACACS+User Experience Monitor 49 Used for TACACS+ protocol connections.
Tomcat Server Monitor 8080 Used to retrieve status information from the Apache Tomcat status website.
VMware Performance Counter Monitor 443 Used to communicate with the VMware API.
Windows Event Log Monitor

This component monitor uses the following ports:

  • TCP/135
  • RPC/named pipes (NP) TCP 139
  • RPC/NP TCP 445
  • RPC/NP UDP 137
  • RPC/NP UDP 138
  • POP3 User Experience Monitor port 110

SAM template port requirements

Template port requirements vary, depending on how you utilize them. The following provides a list of monitor templates that use specific ports.

Template Port Description
Blackberry Delivery Confirmation template 25 Used on the SMTP server, by default, to send test emails. If the SMTP server uses a different port, change this value.
Java Application Server (SNMP) template 1161 Used to send SNMP requests.
Windows FTP Service templates (via WMI) 21 Monitors the Windows FTP Publishing Service and tests the ability of the FTP server to accept incoming sessions on port 21.

SAM container service monitoring port requirements

To support container service monitoring, allow all outbound communication from orchestrator machines on the following ports:

  • 17799 (to the Orion Cortex API)
  • 17778 (to the SWIS API)

All other ports are used for internal communication by specific orchestrators, and should not be blocked by internal orchestrator firewall rules. You can change ports in configuration files manually, but SolarWinds does not recommend doing so.

Following are port-related details for supported container services:

  • Kubernetes
    • 17799 - Cortex (Orion Platform communication)
    • 17778 - SWIS
    • 30043 - Node Port (internal docker communication)
    • 4043 - Target Port / Container Port (internal docker communication)
  • Docker
    • 17799 - Cortex (Orion Platform communication)
    • 17778 - SWIS
    • 6784 - report/wave status (internal docker communication)
    • 4043 - container port (internal docker communication)
  • Docker Swarm 17.12+
    • 17799 - Cortex (Orion Platform communication)
    • 17778 - SWIS
    • 6784 - report/wave status (internal docker communication)
    • 4043 - container port (internal docker communication)
  • Apache Mesos
    • 17799 - Cortex (Orion Platform communication)
    • 17778 - SWIS
    • 4043 - Mesos master server port (internal Mesos communication)
    • 8080 - Deployment service (internal Mesos communication)

For a comprehensive list of port requirements for all products, see SolarWinds Port Requirements.


SAM WMI requirements

Return to top

Microsoft Windows by default uses a random port between 1024 and 65535 for WMI communications.

You must create firewall exceptions to allow bidirectional TCP/UDP traffic on ports 1024 - 65535 or the component monitors and templates that use WMI will not work.

The following component monitors use WMI:

  • Performance Counter Monitor
  • Process Monitor – WMI (if script uses WMI access)
  • Windows Event Log Monitor
  • Windows PowerShell Monitor (if script uses WMI access)
  • Windows Script Monitor
  • Windows Service Monitor (if script uses WMI access)

The following templates use WMI:

  • Active Directory
  • Active Directory 2016 Domain Controller Security
  • Active Directory 2016 Services and Counters
  • Blackberry Enterprise Server
  • Citrix XenApp 5.0 Core WMI Counters
  • Citrix XenApp 5.0 ICA Session WMI Counters
  • Citrix XenApp 5.0 Presentation Server WMI Counters
  • Citrix XenApp 5.0 Services
  • Errors in Application Event Log
  • Exchange 2007
  • Exchange 2007—2010 Client Access Role Services
  • Exchange 2007—2010 Client Access Role WMI Counters
  • Exchange 2007—2010 Common WMI Counters
  • Exchange 2007—2010 Edge Transport Role Services
  • Exchange 2007—2010 Hub Transport Role Services
  • Exchange 2007—2010 Hub Transport Role WMI Counters
  • Exchange 2007—2010 Mailbox Role Services
  • Exchange 2007—2010 Mailbox Role WMI Counters
  • Exchange 2007—2010 Unified Messaging Role Services
  • Exchange 2007—2010 WMI Counters
  • Exchange 2013 Client Access Role Services
  • Exchange 2013 Client Access Role WMI Counters
  • Exchange 2016 Client Access Role Services
  • Exchange 2016 Hub Transport Role Counters
  • Exchange 2016 Hub Transport Role Servers and Counters
  • Exchange 2010 Common Performance Counters
  • Exchange Server 2000 and 2003
  • Internet Information Services
  • Orion Server
  • SharePoint Server (MOSS) 2007
  • SharePoint Services (WSS) 3.0
  • SQL Server 2005 Database
  • SQL Server 2008 Database
  • Windows Print Services
  • Windows Server 2003-2008

WPM Recorder requirements

Return to top

In addition to WPM Recorders added to the Orion server when you install WPM, you can deploy WPM Recorders to other computers on machines other than the Orion server, such as a computer in a branch office.

WPM 3.0 supports two types of recorders — the new 3.0+ WPM Recorder and the Deprecated WPM Recorder from WPM 2.2.3. >> Learn more

The following requirements apply to standalone versions of the 3.0+ WPM Recorder:

Resource Requirement
CPU 1 GHz or better
Memory 2 GB
Operating system

Windows 7, 8, 10

Windows Server 2008, 2012, 2016, and 2019

TCP/IP ports

80 (TCP) open for http traffic

443 (TCP) open for https traffic

17777 (TCP) open for SolarWinds traffic

Web browser

Same as the Orion Web Console

The following requirements apply to standalone versions of the Deprecated WPM Recorder:

Resource Requirement
CPU 1 GHz or better
Memory 2 GB
Operating system

Windows 7, 8, 10*

Windows Server 2008, 2012, 2016*, and 2019*

*Recordings that include certificate validation may interrupt the WPM Player. >> Learn more

TCP/IP ports

80 (TCP) open for http traffic

443 (TCP) open for https traffic

17777 (TCP) open for SolarWinds traffic

Web browser

Internet Explorer (IE) 11

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

WPM Player requirements

Return to top

As described in How WPM works, the WPM Player is a Windows service you can install on remote computers to simulate end user experiences with web applications by playing back recorded transactions.

You can install a standalone version on any computer that meets the following system requirements. To learn about managing loads on hosts, see Scalability Engine Guidelines for SolarWinds Orion Products. You can also check the Player Load Percentage widget.

If a computer hosts a hypervisor or virtual machine monitor (VMM) running various servers (for example, print or file servers), consider adding another server and installing the WPM Player on that server instead.

Minimum WPM Player requirements

Resource Requirement
CPU Quad core processor or better
Memory 3 GB
Operating system

Windows 7, 8, 10*

Windows Server 2008, 2012, 2016*, and 2019*

*Recordings that include certificate validation may interrupt the WPM Player. >> Learn more

Account and security

Accounts can access the remote administrator share

Updated root certificates

TCP/IP ports

80 (TCP) open for http traffic

135 (TCP) open for Microsoft EPMAP (DCE/RPC Locator service)

443 (TCP) open for https traffic

445 (TCP) open for Microsoft-DS SMB file sharing

17777 (TCP) open for SolarWinds traffic

17781 (TCP) open for server-initiated (passive) communication mode

17782 (TCP) open for server-initiated (active) communication mode

17783 (TCP) open for WPM Player automatic updates (bidirectional)

Web browser

Internet Explorer (IE) 11

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

Additional resources


Legal notices

Return to top

© 2019 SolarWinds Worldwide, LLC. All rights reserved.

This document may not be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the prior written consent of SolarWinds. All right, title, and interest in and to the software, services, and documentation are and shall remain the exclusive property of SolarWinds, its affiliates, and/or its respective licensors.

SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS, OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON THE DOCUMENTATION, INCLUDING WITHOUT LIMITATION NONINFRINGEMENT, ACCURACY, COMPLETENESS, OR USEFULNESS OF ANY INFORMATION CONTAINED HEREIN. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY, EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The SolarWinds, SolarWinds & Design, Orion, and THWACK trademarks are the exclusive property of SolarWinds Worldwide, LLC or its affiliates, are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other SolarWinds trademarks, service marks, and logos may be common law marks or are registered or pending registration. All other trademarks mentioned herein are used for identification purposes only and are trademarks of (and may be registered trademarks) of their respective companies.