SAM 6.9.1 System Requirements
Released July 1, 2019
Updated August 7, 2019
Important: These recommended system requirements are for SolarWinds SAM 6.9.1 as a single product installed on Orion Platform 2019.2.
- Software requirements
- Account privileges
- Server port requirements
- Hardware requirements
- Database server requirements
- Amazon Web Services deployments
- Microsoft Azure deployments
- Additional SAM port requirements
- SAM WMI requirements
- Additional SAM technology requirements
- More learning resources
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 SAM 6.9.1 release notes.
Software requirements for the Orion server
This table lists software requirements and recommendations for a SolarWinds installation on both physical and virtual computers.
| Software Requirements | |
|---|---|
| Operating system |
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
End-of-support notice: Products with Orion Platform 2018.4 and later 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 |
|
| IP address version |
CIDR notation is not supported for IPv6 addresses. |
| Web server |
If you're 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 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 to collect syslog messages and traps:
|
| Orion Web Console browser |
Orion Platform products support the two most recent versions of the following web browsers available at the release date:
The following browsers are also supported:
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.
Server port requirements
-
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 High Availability, ensure ports 4369 and 25672 are open.
- RPC ports > 1024 (TCP, bidirectional) are used by the Job Engine v2 process to communicate with Windows nodes.
| Port | Protocol | Service/Process | Direction | Description |
|---|---|---|---|---|
| User-defined, default: 22 | SSH |
SolarWinds Job Engine v2 IIS |
Outbound from the Orion server to the device |
Access Cisco Adaptive Security Appliance (ASA) devices through the Command-Line Interface (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 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. |
| 161 | UDP |
SolarWinds Job Engine v2 SolarWinds Cortex service |
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 bidirectional ESX/ESXi server polling and Cisco UCS device 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. |
| 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 RabbitMQ messaging (AMQP/TLS) between the main polling engine and all Additional Polling Engines, High Availability servers, or Additional Web Servers. TLS 1.2 encryption |
| 17777 | TCP |
SolarWinds Cortex (communication) SolarWinds Information Service SolarWinds Information Service V3 SolarWinds Orion Module Engine |
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:
|
| 17778 | HTTPS | SolarWinds Agent | Bidirectional |
Required to access the SWIS API and agent communication. Also used for outbound communication with container orchestrators. SSL encryption |
| 17799 | HTTPS | Container service monitoring | Bidirectional | Communication with container orchestrator machines in SAM and VMAN. |
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.
Hardware requirements for the Orion server
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.
- Do not install Orion Platform products on the same server as SolarWinds Access Rights Manager (ARM).
- 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 node-based license levels. Click here to compare legacy component-based license levels with node-based license levels.
CPU recommendations for SAM300 deployments use the PassMark Score. To learn more, see Pass Mark Performance Test (Copyright © 2019 PassMark® Software, obtained at https://www.cpubenchmark.net on April 24, 2019).
| Feature | SAM10, SAM25 | SAM50, SAM75 | SAM100 | SAM300 |
|---|---|---|---|---|
| CPU | Quad core processor or better | Quad core processor or better | Quad core processor or better | CPUs with a total combined PassMark score of 7,000 or higher |
| Do not enable Physical Address Extension (PAE). | ||||
| Hard drive space |
10 GB minimum 20 GB recommended |
15 GB minimum 40 GB recommended |
30 GB minimum 40 GB recommended |
40 GB minimum 50 GB recommended Read/Write I/O performance of 800 IOPS |
|
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 |
6 GB minimum 8 GB recommended |
8 GB minimum 16 GB recommended |
16 GB minimum 32 GB recommended |
16 GB minimum 32 GB recommended |
Orion database server requirements
The following table lists software and hardware requirements for your SolarWinds Orion database server, using SAM node-based license levels.
Do not install Orion Platform products on the same server as SolarWinds Access Rights Manager (ARM).
- If using legacy component-based licensing, click here to compare component- and node-based license levels.
- The Orion server and the Orion database must use separate servers.
- If you install on a virtual machine, you must maintain your Orion database on a separate, physical drive.
- As of Orion Platform 2019.2, you can use Azure SQL or Amazon RDS as your database server. See the Orion Platform release notes for details.
| Feature |
SAM10, SAM25 |
SAM50, SAM75 | SAM100 | SAM300 |
|---|---|---|---|---|
| SQL Server |
Express, Standard, or Enterprise versions of the following:
SolarWinds recommends that you use Express versions only for evaluations and very small environments. |
Enterprise versions of supported SQL Servers:
|
||
|
End-of-support notice: Products running on Orion Platform 2018.4 and later are no longer compatible with SQL Server 2012, 2012 SP1, 2012 SP2, 2012 SP3, and 2012 SP4. To use the new features introduced in Orion Platform 2018.4 and later, upgrade your environment at your earliest convenience. Recommendations
|
||||
| SQL Server collation |
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 | CPUs with a total combined PassMark score of 32,000 or higher |
| Hard drive space |
20 GB minimum 40 GB recommended |
50 GB minimum 100 GB recommended |
100 GB minimum 400 GB recommended* |
Read/Write I/O performance of 30,000 IOPs 190,000 IOPS or better recommended 1 Gbit dedicated NIC |
Some common files may need to be installed on the same drive as your server OS. You may want to move or expand the Windows or SQL temporary directories. See Working with Temporary Directories. |
||||
| Memory |
SAM10 4 GB minimum 8 GB recommended |
16 GB minimum 64 GB recommended |
64 GB minimum 128 GB recommended |
256 GB minimum 512 GB recommended |
|
SAM25 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 |
SolarWinds recommends installing the SQL Server Management Studio component on your Orion database server. The Orion Installer adds the following x86 components if they are not found on the Orion database server:
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 Research in Motion (RIM) BlackBerry servers. |
|||
*SolarWinds recommends the following hard drive configuration:
- 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
Amazon Web Services (AWS) deployments
To deploy your Orion Platform product using AWS, consider using the following templates, listed according to SAM node-based license levels. If using legacy component-based licensing, click here to compare component- and node-based license levels.
| Requirements |
SAM10, SAM25, SAM50 |
SAM75, SAM100 |
SAM200 |
SAM300 |
|---|---|---|---|---|
| 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 | N/A | m5.xlarge | ||
Microsoft Azure deployments
To deploy your Orion Platform product on Microsoft Azure, consider using the following instance types, listed according to SAM node-based license levels. If using legacy component-based licensing, click here to compare component- and node-based license levels.
| Feature |
SAM10, SAM25, SAM50 |
SAM75, SAM100 |
SAM200 |
SAM300 |
|||
|---|---|---|---|---|---|---|---|
|
Orion 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 |
DS4_v2 8 CPU 32 GB RAM 150 GB disk |
|||
|
SolarWinds Orion database server in an Azure VM |
D12_v2 4 CPU 30.5 GB RAM System SSD 80 GB (included in D12_v2) + Data Azure Storage Disk Volume 500 GB* |
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) |
DS4_v2 Azure Disk storage with Provisioned IOPS recommended 8 CPU 61 GB RAM System SSD 160 GB (included in DS4_v2) + 2x Data Azure Storage Disk Volume 500 GB* |
E32-8s_v3 Azure Disk storage with Provisioned IOPS recommended 8 CPU 256 GB RAM System SSD 512 GB (included in E32-8s_v3) + 2x Data Azure Storage Disk Volume 500 GB* |
|||
| SolarWinds Orion database using Azure SQL DB |
All installed products must run on Orion Platform 2019.2, such as:
The time zone setting of the Orion Server must match the Azure SQL DB time zone (UTC). When deploying Azure SQL and creating a new user in the Configuration wizard, SA account credentials are required. When using Azure SQL for your database server, required tiers depend on if you're using memory-optimized tables (In-Memory OLTP) supported in SQL Server 2016 and 2019 to improve the performance of transaction processing, data ingestion, data load, and transient data scenarios. |
||||||
| Azure SQL DB tiers if using In-Memory OLTP |
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 |
DTU Tier P11 vCore Business Critical Gen4 Tier 16 vCore Business Critical Gen5 Tier 14 |
|||
| Azure SQL DB tiers without In-Memory OLTP |
DTU Standard Tier S3 DTU Premium Tier P1 vCore General Purpose Tier 2 vCore Business Critical Tier 2 |
DTU Standard Tier S3 DTU Premium Tier P2 vCore General Purpose Tier 2 vCore Business Critical Tier 2 |
DTU Standard Tier S4 DTU Premium Tier P4 vCore General Purpose Tier 3 vCore Business Critical Tier 4 |
DTU Standard Tier S9 to S12 DTU Premium Tier P11 vCore General Purpose Tier 16 to 30 vCore Business Critical Tier 14 |
|||
* If you're not using Azure Disk Storage for SQL servers, consider using Azure Reserved VM Instances.
Additional SAM port requirements
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.
SAM component monitor port requirements
| Component/ Monitor | Port | Type | Description |
|---|---|---|---|
| DHCP User Experience Monitor | 67 | UDP | Used for DHCP requests. |
| DHCP User Experience Monitor | 68 | UDP | Used for DHCP responses. |
| 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 File Size Monitor File Count Monitor |
445 | See SAM WMI requirements and 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 form-based login sessions. | |
| HTTPS Monitor | 443 | Used to test a web server's ability to accept incoming sessions over a secure channel and then transmit the requested page. | |
| IMAP4 Monitor | 143 (default) | IMAP4 | Used for IMAP 4 sessions. |
| 585 | IMAP4 | Used for Secure IMAP (IMAP4-SSL) sessions. | |
| 993 | IMAP4 | Used for IMAP4 over SSL (IMAPS) sessions. | |
| IMAP4 User Experience Monitor | 25 | SMTP | Used to communicate with a Microsoft Exchange mail server. |
| 143 | IMAP4 | ||
| 993 | IMAP4 | ||
| LDAP User Experience Monitor | 389 | Used for LDAP connections. | |
| 636 | For LDAP over SSL, use port 636. | ||
| Linux/Unix Script Monitor Ports | 22 | Used for SSH connections. | |
| NNTP Monitor | 119 | UDP | Used for Network News Transfer Protocol (NNTP) connections. |
| ODBC User Experience Monitor | 1630 | TCP |
To configure ODBC when polling with Orion Agent for Linux, see Linux/Unix system configurations for component monitors. |
| 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. |
| 1526 | |||
| Performance Counter Monitor | See Description. | TCP |
This monitor uses RPC, requiring the following ports:
|
| POP3 Monitor | See Description. |
This monitor uses the following ports to communicate with Microsoft Exchange mail servers.
|
|
|
POP3 Monitor POP3 User Experience Monitor |
110 (default) | Used for POP3 connections. | |
| 995 | Used for Secure POP3 (SSL-POP) connections. | ||
| 25 | SMTP | Used for SMTP sessions. | |
|
Process Monitor |
SNMP |
Uses SNMP communication. |
|
|
Process Monitor - Windows |
|
Uses WMI or RPC communication to test if a specified Windows process is running and reports statistics about all instances of the process. |
|
| 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 a Referral Whois (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 MS SQL Server uses the default port, 1433. If MS SQL Server uses a non-standard port, use the ODBC User Experience monitor instead to manually define a connection string for the 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:
|
SAM template port requirements
Template port requirements vary, depending on how you utilize them. The following SAM templates use specific ports.
| Template | Port | Description |
|---|---|---|
| Blackberry Delivery Confirmation template | 25 | Used on the SMTP server 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. |
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
Microsoft Windows uses a random port between 1024 and 65535 for WMI communications, by default, so you must create firewall exceptions to allow bidirectional TCP/UDP traffic on those ports to support SAM templates and component monitors that use WMI.
Consider using the agent if wide ranges of open ports on the firewall present security concerns in your environment. For details, see Monitor with Orion agents in SAM.
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 2003-2008 Services and Counters
- Active Directory 2008 R2-2012 Services and Counters
- Active Directory 2016 Domain Controller Security
- Active Directory 2016 Services and Counters
- APC PowerChute Agent (Windows)
- 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
- Citrix XenApp 6.0 Core Counters
- Citrix XenApp 6.0 ICA Session
- Citrix XenApp 6.0 Services
- Citrix XenApp and Xen Desktop 7.x (Advanced)
- Citrix XenApp and Xen Desktop 7.x (Events)
- Citrix XenApp and Xen Desktop 7.x (Performance Counters)
- Citrix XenApp and Xen Desktop 7.x (Services)
- Directory Size
- Errors in Application Event Log
- Exchange 2007 templates (all)
- Exchange 2007-2010 templates (all)
- Exchange 2010 templates (all)
- Exchange 2013 templates (all)
- Exchange 2016 templates (all)
- Exchange Active Sync Connectivity
- Exchange Server 2000 and 2003
- Exchange Web Services User Experience monitor
- Internet Information Services (IIS) 6
- Internet Information Services (IIS) 10
- Kaspersky Security Center Antivirus
- Kiwi Syslog Server
- Microsoft DirectAccess templates (all)
- Microsoft Dynamics templates (all)
- Microsoft Forefront Endpoint Protection templates (all)
- Microsoft IIS SMTP Server
- Microsoft Lync Server templates (all)
- Microsoft Message Queuing templates (all)
- Microsoft Network Policy Server templates (all)
- Microsoft Office 365 templates (all)
- Microsoft Routing and Remote Access templates (all)
- Microsoft SharePoint templates (all)
- Microsoft Skype templates (all)
- Microsoft SQL Server templates (all)
- Microsoft Windows Internet Name Service (WINS) templates (all)
- Microsoft Windows Server templates (all)
- Orion Server 2017.3
- SQL Server 2005 Database
- SQL Server 2008 Database
- Symantec Backup Exec Remote Agent
- Symantec Backup Exec Server
- Symantec Endpoint Protection Server
- Symantec NetBackup Client
- Trend Micro OfficeScan Client
- Trend Micro OfficeScan Server
- Windows DHCP Server
- Windows DNS Server
- Windows Network Load Balancing
- Windows Print Services
- Windows Remote Desktop Services (Session Host Role)
- Windows Server 2003-2008
- Windows Service monitor
Additional SAM technology requirements
- AppInsight for Active Directory requirements and permissions
- AppInsight for Exchange requirements and permissions
- AppInsight for IIS requirements and permissions
- AppInsight for SQL requirements and permissions
- Asset inventory and hardware health requirements
- SNMP requirements for monitored devices
- Third-party software required to monitor hardware health and Asset Inventory information
If you need to limit open ports, you can poll devices with Orion agents; server-initiated mode requires only a single port open. To learn more, see Poll devices with SolarWinds Orion agents and also Orion Agent requirements.
SAM licensing levels
If using legacy component-based licensing, this table provides equivalent node-based license tiers for SAM system requirements.
| Node-based license tier | Component-based license tier |
|---|---|
| SAM10 | AL150 |
| SAM25 | AL300 |
| SAM50 | AL700 |
| SAM75 | AL1100 |
| SAM100 | AL1500 |
| SAM200 | AL2500 |
| SAM300 | ALX |
More learning resources
To learn more about Orion Platform requirements and configurations, refer to:
- Multi-module system guidelines
- Orion Agent requirements
- Scalability Engine Guidelines
- High Availability requirements
- Cloud monitoring requirements
- Port requirements for all SolarWinds products
- Deploy Orion Platform products to Amazon Web Services
- Deploy Orion Platform products to Microsoft Azure
Legal notices
© 2022 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.