Server & Application Monitor

Transcription

1 INSTALLATION GUIDE Server & Application Version 6.4 Last Updated: Tuesday, November 21, 2017 Retrieve the latest version from: (SAM)/SAM_Documentation

2 2017 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 and documentation are and shall remain the exclusive property of SolarWinds and its respective licensors. SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER INCLUDING WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. 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 and other SolarWinds marks, identified on the SolarWinds website, as updated from SolarWinds from time to time and incorporated herein, are registered with the U.S. Patent and Trademark Office and may be registered or pending registration in other countries. All other SolarWinds trademarks may be common law marks or registered or pending registration in the United States or in other countries. All other trademarks or registered trademarks contained and/or mentioned herein are used for identification purposes only and may be trademarks or registered trademarks of their respective companies. page 2

3 Table of Contents SAM installation overview 5 Stand-alone installation 6 Integrated with the Orion Platform 7 Evaluation installation 7 SolarWinds High Availability 7 Terminology 8 SAM licensing model detailed 9 License consumption 9 Verify the component monitors consumed per template 10 Manage and activate your SAM license 11 SAM requirements 13 SAM system requirements 13 Hardware requirements 14 VM configuration requirements 14 Software requirements 15 Database server (SQL Server) requirements 17 SAM port requirements 21 Agents 23 High Availability 24 SAM Component Ports 24 SAM Templates 29 SAM WMI Requirements 30 Multi-module system guidelines 31 Small deployment guidelines 31 Medium deployment guidelines 32 page 3

4 INSTALLATION GUIDE: SERVER & APPLICATION MONITOR NTA-specific information 33 Large deployment guidelines 33 NTA-specific information 35 SAM installation checklist 36 Prepare for the install 37 Installation gotchas 38 Prepare the SAM SQL database 39 Install Orion Stand-alone SAM 41 Integrate SAM with an existing Orion Platform 47 Install SAM with High Availability 53 Orion install with new HA 53 Orion install with existing HA 54 Install SAM evaluation 56 Uninstall SAM 58 page 4

5 SAM installation overview Supported Version: SAM 6.4 and earlier For SAM 6.5 or later, use the SolarWinds Orion Installer. SolarWinds Server & Application (SAM) provides tools you can use to monitor your environment and applications with a single web console. SAM includes custom collections of templates, application monitors, and alerts to intelligently monitor application status in on-premise, virtual, hybrid, and cloud environments. over 200 applications, including operating systems plus authentication, application and database servers. SAM monitors applications in public, private, and hybrid environments using: AppInsight: s Microsoft Exchange, IIS, and SQL servers to display metrics, status, and issues. Application templates: Combine process monitors, port availability, and performance counters to assess the health of applications and the overall environment. Alerts: Identify issues via customizable triggers, static or baseline thresholds, and actions. SolarWinds Orion Platform: Adds features such as automated application discovery, agent monitoring, High Availability (HA) for automated failover, and web-based license management. Use the Product Upgrade Advisor to learn about Orion, AppStack, and other products that can be integrated with SAM. There are three ways to install SAM: Stand-alone installation Integrated installation with the Orion Platform Evaluation installation Before installation, review the system requirements, port requirements, and preflight installation checklist. page 5

6 INSTALLATION GUIDE: SERVER & APPLICATION MONITOR Stand-alone installation For a stand-alone installation, install SAM on a dedicated server. This installation assumes that no other Orion Platform products are installed on the target server. page 6

7 Integrated with the Orion Platform SAM supports an integrated installation into an existing Orion Platform. Check if existing products need to be upgraded and then install SAM on the Orion server connected to the separate Orion SQL database server. Evaluation installation SAM supports an evaluation installation with a 30-day trial period that provides access to all features. To continue with a full product license, contact SolarWinds Sales. SolarWinds High Availability SAM also supports SolarWinds High Availability that offers these key features: Automated, rapid failover ensures monitoring and data collection continuity. Instant notification and alerting are independent of the SolarWinds alerting service, so you ll receive alerts even if the SolarWinds Orion server is down. Customizable failover rules can be set up to trigger failover based on application, system, process, page 7

8 INSTALLATION GUIDE: SERVER & APPLICATION MONITOR and service health thresholds. With easy installation and configuration, High Availability is fully integrated into the SolarWinds Orion platform and is licensed per-pool. To deploy HA, set up a secondary server, activate the license, and create a pool. (See Install SAM with High Availability during SAM.) If you evaluate HA, you can create an unlimited number of pools. After 30 days, apply a license key to convert the evaluation to a permanent license. Terminology The following terms provide context for the architecture and components of SolarWinds products. Additional Polling Engine (APE) To scale polling and monitoring in larger environments, you can add APEs or stackable polling engines to monitor hundreds of thousands of elements, and poll across multiple pollers and locations to improve performance. See the Scalability Engine Guidelines for SolarWinds Orion Products. Additional Web Server (AWS) To expand access to the Orion Web Console in larger environments, you can add an additional web server (AWS) so users can access the Orion Web Console remotely, from a location other than your primary Orion server. See Use an Additional Web Server. High Availability (HA) HA protects your environment from server crashes, outages, and database issues. Server pairs in HA pools provide automatic failover to a backup server for the main Orion server and additional polling engines. Each server pair can be easily updated with new products and hotfixes using the Scalability Engine Installer via the Orion Web Console. Orion Web Console The Orion Web Console is the web interface where you can access SAM, Orion modules, and other SolarWinds products. The web interface provides customizable views, configuration options, and monitored metrics in a single location. page 8

9 SAM licensing model detailed The SolarWinds SAM license you purchase is based on the number of allowed assigned component monitors. A component monitor provides a statistic that you want to monitor in SolarWinds SAM. You can have as many application templates and assigned monitors as needed, as long as the number of assigned component monitors does not exceed the license count. If assigned component monitors exceed the license limit, monitors beyond the license limit are not activated and statuses change to Not Licensed. Either disable assigned component monitors to reduce your total assigned monitor count, or contact SolarWinds to upgrade your SolarWinds SAM license. SAM has the following available license tiers: AVAILABLE LICENSE TIERS NUMBER OF COMPONENTS TO MONITOR AL AL AL AL ALX Unlimited amount of items to monitor standard polling throughput. License consumption SolarWinds SAM licenses do not have to mirror the license count of other installed SolarWinds producst. For example, you can install SolarWinds SAM with a 150-component license on a SolarWinds NPM server with an unlimited node license. The number of component licenses are consumed by a specific amount by component and feature: Asset Inventory data collection: Asset Inventory data collection does not count against your SAM component monitor license. Windows Scheduled Task : The WSTM consumes five license units per node. Agents: Agent software is free. You remain bound by license limits regardless of whether you poll information via an agent or another protocol. AppInsight for SQL: 50 component monitors count against your licensed number of component monitors per SQL instance. AppInsight for Exchange: 50 component monitors count against your licensed number of page 9

10 INSTALLATION GUIDE: SERVER & APPLICATION MONITOR component monitors, per Exchange Server. AppInsight for IIS: 30 component monitors count against your licensed number of component monitors per monitored IIS server. To verify the number of consumed and available component monitors in your license, access the SAM License Summary. 1. Log in to the SolarWinds Web Console with an administrator account. 2. Click Applications. 3. Click SAM Settings. 4. Click SAM License Summary. Alternatively, click License Details in the Settings page to view the used and available component monitors. Verify the component monitors consumed per template SolarWinds SAM licenses do not have to mirror the license count of any other installed SolarWinds products. For example, you can install SolarWinds SAM with a 150 component license on a SolarWinds NPM server with an unlimited node license. page 10

11 Example: The Apache template has eight available licensed component monitors. If you have an AL150 license and assign all eight component monitors in this template to a node, the balance of remaining licenses is 142 (150-8 = 142). If only five of the eight component monitors are assigned to a node, the balance of remaining licenses is 145 (150-5=145). To view the number of licensed component monitors per template in SAM, click Settings > All Settings > SAM Settings > Manage Templates. Review the Licensed Components column amount per template. Component monitors are consumed from the license only when the template is assigned to a node. Manage and activate your SAM license During installation, the web-based License manager will prompt you activate your SAM license; note these details: When using your Customer ID and password, use your individual profile information. If you do not know your Customer ID or password, enter a Support ticket. To get an activation key, navigate to the SolarWinds Customer Portal, click License Management, then click the plus sign [+]. To manage SAM and other licenses: 1. Click Settings > All Settings in the Orion Web Console. 2. Click License Manager in the Details section. You can sort licenses by product name, product version, license type, or expiration date. You can also add a license, upgrade a current license to a new tier, and activate licenses on new servers. The License Manager on the Main Polling Engine controls all licenses for your SAM environment, including scalability engines and High Availability. page 11

12 INSTALLATION GUIDE: SERVER & APPLICATION MONITOR If you license your product before you install it, click Add/Upgrade License, enter the details, and complete the activation to see the license in the License Manager. page 12

13 SAM requirements SolarWinds SAM has various requirements and guidelines, depending on if other SolarWinds products are installed. SAM system requirements SAM port requirements Multi-module system guidelines SAM system requirements These system requirements define the minimum requirements for SAM 6.5 as a single product installed on Orion Platform Requirements may increase for medium or large environments, or environments with multi-modules installed. Hardware requirements Software requirements Database server (SQL Server) requirements For additional information about requirements and configurations, see the Multi-module system guidelines. Review product administration guides and release notes for exact product requirements beyond these minimums. SolarWinds recommends reviewing the SAM 6.5 Release Notes. Your Orion server and your SolarWinds Orion database must use separate servers. For additional technical requirements, refer to: SAM port requirements Orion Agent requirements High Availability requirements NetPath Requirements Network Atlas requirements Scalability Engine Guidelines Server sizing is impacted by: Number of monitored elements: An element is a component monitor, a node, interface, or volume. Polling frequency: SolarWinds SAM polls devices to collect data and determine status. If you increase the default 5-minute polling rate, system requirements will increase. Number of simultaneous users: Add 1 GB of RAM for every 25 simultaneous users. page 13

14 INSTALLATION GUIDE: SERVER & APPLICATION MONITOR To learn more, see Server sizing recommendations, review Scalability Engine Guidelines for SAM, contact the SolarWinds sales team, or visit Hardware requirements The following table lists minimum hardware requirements and recommendations for your SolarWinds server on both physical and virtual computers. Use the minimum hardware configuration if you are evaluating the product or do not anticipate heavy usage. Installing multiple SolarWinds Orion Platform products on the same computer may change the requirements. SolarWinds strongly suggests using the recommended hardware configuration to avoid performance issues caused by heavy loads or custom configurations, such as increased data retentions or more frequent polling intervals. SAM LICENSE LEVEL FEATURE AL150 AL300 (SMALL) AL700 AL1100 (MEDIUM) AL1500 ALX (LARGE) CPU speed Quad core processor or Quad core processor or Quad core processor or better better better Do not enable Physical Address Extension (PAE). Hard drive 10 GB minimum 15 GB minimum 30 GB minimum space 20 GB recommended 40 GB recommended 100 GB recommended Two 146 GB 15K (RAID 1/Mirrored Settings) hard drives are recommended with a dedicated drive for the server operating system and SolarWinds 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 10 GB minimum 18 GB minimum 8 GB recommended 16 GB recommended 32 GB recommended VM configuration requirements VMware and Microsoft Virtual Server VMs are supported if these minimum configuration requirements are met. You must maintain the Orion Platform SQL Server database on a separate, physical server. The following requirements are for monitoring Microsoft Hyper-V and VMware ESXi (formerly ESX) servers: page 14

15 FEATURE SNMP Virtualization software DESCRIPTION SNMP must be enabled on all ESXi and ESX servers. See vendor documentation for details. ESXi and ESX Server version 4.1 or later VMware vsphere version 4.1 or later, including 6.5 Microsoft Hyper-V Server versions 2008 R2, 2012, 2012 R2, 2016 VMware tools Install VMware Tools on all VMs. VMware Tools may be helpful on monitored ESXi servers because they provide more data, such as IP addresses. SAM uses the following methods to monitor VMware ESXi Server component features. FEATURE 4 4I 5I 6.0 Datacenter ESXi cluster Virtual Center Detection as ESX server VMware API VMware API VMware API VMware API Volumes SNMP N/A SNMP Interfaces SNMP SNMP (partial) SNMP CPU Memory Total CPU (ESX details view) Total memory (ESX details view) Network traffic utilization (ESX details view) Guest VM list (ESX details view) VMware API VMware API VMware API VMware API VMware API VMware API Software requirements SolarWinds only supports installing the Orion agent on domain controllers. Do not install any other SolarWinds products on domain controllers. page 15

16 INSTALLATION GUIDE: SERVER & APPLICATION MONITOR SolarWinds does not support the installation of any Orion product on the same server as a Microsoft SharePoint, Microsoft Exchange, or Research in Motion (RIM) Blackberry server, nor do we support sharing a database server with those applications. FEATURE REQUIREMENTS Operating system Production Windows Server 2012 and 2012 R2 Windows Server 2016 Evaluation Only Windows 8.1 (not Standard Edition) Windows 10 Installing SAM on Windows Server 2012 R2 Essentials or Windows Server Core is not supported. Operating system languages English (UK or US) German Japanese Simplified Chinese IP address version IPv4 IPv6 implemented as a dual stack. See RFC Basic Transition Mechanisms for IPv6 Hosts and Routers. CIDR notation is not supported for IPv6 addresses. Web server Microsoft Internet Information Services (IIS), version 8.0 or later SolarWinds installs IIS by default, but you can install it manually to reduce installation time or network bandwidth. Microsoft.NET Framework.NET Framework Run the same version of. NET on the primary server and any Additional Polling Engines or Additional Web Servers in the environment. Web console browser Microsoft Internet Explorer version 11 or later with Active scripting Microsoft Edge Firefox 49.0 or later Chrome 54.0 or later page 16

17 FEATURE REQUIREMENTS Do not enable Enterprise Mode on Internet Explorer. This setting forces Internet Explorer to emulate version 7, which is not supported. Other RabbitMQ (primary messaging service between the primary and Additional Polling Engines) MSMQ (fall back and legacy messaging) Services The following services must be running after installation is complete to collect syslog messages and traps: SolarWinds Syslog Service SolarWinds Trap Service User privileges PowerShell SolarWinds recommends that administrators have local administrator privileges to ensure full functionality of local SolarWinds tools. Accounts limited to the Orion Web Console do not require local administrator privileges. SAM PowerShell Script works with PowerShell 1.0 and higher for local execution. PowerShell 2.0 or higher is required for remote execution. Database server (SQL Server) requirements The Orion server and the SolarWinds Orion database must use separate servers. If you install SAM on a virtual machine, you must maintain the SQL Server database on a separate, physical drive. The following table lists software and hardware requirements for your SolarWinds Orion database server using SolarWinds SAM license levels. REQUIREMENTS AL150 - AL300 (SMALL) AL700 - AL1100 (MEDIUM) AL1500-ALX (LARGE) SQL Server SolarWinds supports Express, Standard, or Enterprise versions of the following: SQL Server 2012 SQL Server 2012 SP1 SQL Server 2012 SP2 page 17

18 INSTALLATION GUIDE: SERVER & APPLICATION MONITOR REQUIREMENTS AL150 - AL300 (SMALL) AL700 - AL1100 (MEDIUM) AL1500-ALX (LARGE) SQL Server 2012 SP3 SQL Server 2014 SQL Server 2014 SP1 SQL Server 2014 SP2 SQL Server 2016 SQL Server 2016 SP1 SQL Server 2017 (Windows only) SolarWinds strongly recommends using the 64-bit version of SQL Server. Due to latency effects, SolarWinds does not recommend installing the SQL Server and the SolarWinds server or Additional Polling Engine in different locations across a WAN. For details, see Install SolarWinds software and SolarWinds database (SQL Server) across a WAN. You can set the database recovery model to Full Recovery if the Orion Database is hosted on a SQL Cluster or if you use Always On Availability. However, be sure to back up the database regularly and ensure that the volume where you store the transaction log has free space that is 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 the transactions committed to the database. We recommend daily database backups when you use the Full Recovery model. SolarWinds recommends Simple database recovery mode to ensure best performance. 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 a CS SQL Server. SolarWinds do not support case-sensitive databases. CPU speed Quad core processor, 2.5 GHz or better Quad core processor, 2.5 GHz or better Dual/quad core processor, 3.0 GHz or better Hard drive space 20 GB minimum 50 GB minimum 100 GB minimum page 18

19 REQUIREMENTS AL150 - AL300 (SMALL) AL700 - AL1100 (MEDIUM) AL1500-ALX (LARGE) 40 GB recommended 100 GB recommended 400 GB recommended SolarWinds recommends the following configuration: A hardware RAID Controller with a battery backed-up write back cache Disk Subsystem 1 Array : 2x 146 GB 15K disks RAID 1 (mirroring) for the OS Disk 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 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 a SQL LDF Transaction LOG file page 19

20 INSTALLATION GUIDE: SERVER & APPLICATION MONITOR REQUIREMENTS AL150 - AL300 (SMALL) AL700 - AL1100 (MEDIUM) AL1500-ALX (LARGE) Disk Subsystem 5 Array 5: with 4x 15K 146 GB or 300 GB disks configured in a RAID 1+0 array for maximum write performance for tempdb data file Disk Subsystem 6 Array 6: with 4x 15K 146 GB or 300 GB disks configured in a RAID 0 array for a 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's performance. 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 OS. You may want to move or expand the Windows or SQL temporary directories. Memory AL GB minimum 64 GB minimum 4 GB minimum 64 GB recommended 128 GB recommended 8 GB recommended AL300 8 GB minimum 16 GB recommended Additional memory improves both performance and reliability. page 20

21 REQUIREMENTS AL150 - AL300 (SMALL) AL700 - AL1100 (MEDIUM) AL1500-ALX (LARGE) Memory and Additional Pollers Authentication Other software Each additional poller requires 16 GB of additional RAM. For example, SAM plus two additional pollers require 32 GB of RAM. Three additional pollers require 48 GB of RAM, and so on. Either mixed-mode or SQL authentication If you are managing the SolarWinds Orion database, SolarWinds recommends installing the SQL Server Management Studio component. The Installation Wizard installs the following required x86 components if they are not found on the Orion database server: SQL Server System Common Language Runtime (CLR) Types. Orion 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 The SAM PowerShell Script works with PowerShell 2.0 and later. SAM port requirements Configure ports to support communications for the main polling engine and the Orion SQL server, as well as additional polling engines and web servers. Some ports have feature-specific requirements for Orion agents and High Availability, as well as component monitors and templates. Ports 4369, 25672, and 5672 are open by default, but can be blocked by a firewall. PORT PROTO- COL DIRECTION ENCRYPTION DESCRIPTION 25 TCP SMTP port for non-encrypted messages 161 UDP bidirectional Statistics collection 162 UDP incoming Trap Server listening for incoming messages 443 TCP bidirectional Default port for https binding and bidirectional ESX/ESXi server polling and for Cisco UCS monitoring. 465 TCP outbound SSL SSL-enabled alert actions page 21

22 INSTALLATION GUIDE: SERVER & APPLICATION MONITOR PORT PROTO- COL DIRECTION ENCRYPTION DESCRIPTION 587 TCP outbound TLS TLS-enabled alert actions 1801 TCP WCF MSMQ WCF binding 4369 TCP bidirectional Required for RabbitMQ messaging (epmd) 5671 AMQP bidirectional TLS SSL encrypted RabbitMQ messaging from the additional polling engines to the main polling engine 5672 TCP Non-encrypted RabbitMQ messaging between the primary and additional polling engines. This is a backup communication port that is not used by default TCP bidirectional Required for RabbitMQ messaging (Erlang distribution) TCP bidirectional RSA handshake, AES 256 communication using WCF Orion module traffic. Open the port to enable communication from your poller to the Orion Web Console, and from the Orion Web Console to your poller HTTPS and TCP HTTP and HTTPS SSL High Availability Service. Used for communication between the main server and pool members. Job Engine V2, Collector Service, Business Layer, and Information Service v2,23. Used for communication between the services. The port used for communication between the Orion Web Console and the poller. Required to access the SolarWinds Information Service API and agent communication SolarWinds Information Service API SolarWinds Toolset Integration over HTTP page 22

23 Agents The following ports are used by the SolarWinds Orion agent. PORT TYPE DIRECTION ENCRYP- TION DESCRIPTION 22 TCP bidirectional Used to install the agent on Linux computers through SSH and SFTP or SCP. Open this port for outbound connections on the Orion server or additional polling engings and inbound connections on the monitored computer. 135 TCP inbound (DCE/RPC Locator service) Microsoft EPMAP. This port must be open on the client computer for remote deployment. Active directory, RPC and SMB protocol ports are used by Orion Poller Agent installer to connect to Windows OS and to deploy Windows Agent. 445 TCP inbound Microsoft-DS SMB file sharing. This port must be open on the client computer (inbound) for remote deployment. Active directory, RPC and SMB protocol ports are used by Orion Poller Agent installer to connect to Windows OS and to deploy Windows Agent TCP bidirectional SSL, TLS 1.0 or later Send and receive information from Windows and Linux devices polled by agents using agent-initiated communication. Used to deploy agents. Important: This requirement is for Active agents only. If Passive agents are used, no ports need to be opened on the firewall for the Orion server. For more information, see Changing the Agent Port TCP bidirectional SHA1 certificate, TLS 1.0 or later Used by the agent to communicate with the Orion server when the agent is in server-initiated communication mode. In Passive mode, port must be opened on the host where the agent is installed and allowed by the firewall TCP bidirectional Used by the agent to communicate with the Orion server when the agent is in agent-initiated communication mode. This port must be opened if the reomte computers you monitor run Windows 2008 R2. page 23

24 INSTALLATION GUIDE: SERVER & APPLICATION MONITOR High Availability The following ports are used in addition to ports used by your primary products when you enable High Availability. PORT TYPE DESCRIPTION 4369 TCP Open on the main Orion server and its standby server for RabbitMQ clustering. This port exchanges EPMD and Erlang distribution protocol messages for RabbbitMQ. This port is not required when protecting additional polling engines TCP For encrypted RabbitMQ messaging (AMQP/TLS) into the main polling engine from all Orion servers TCP Open on the main Orion server and its standby server for RabbitMQ clustering. This port exchanges EPMD and Erlang distribution protocol messages for RabbbitMQ. This port is not required when protecting additional polling engines. SAM Component Ports COMPO- NENT/ MONITOR DHCP User Experience DHCP User Experience Directory Size DNS DNS User Experience Download Speed PORT TYPE DESCRIPTION 67 UDP The UDP port used for the DHCP request. 68 UDP The UDP port used for the DHCP response. See SAM WMI requirements below. 53 TCP/UDP The TCP and UDP port used for DNS queries. 19 The port used for the character generator service. page 24

25 COMPO- NENT/ MONITOR File Age File Change File Existence Files Size File Count FTP FTP User Experience HTTP Form Login HTTP TCP Port HTTPS IMAP4 PORT TYPE DESCRIPTION 445 TCP/UDP These components monitor uses TCP/445 and UDP/445 ports. See SAM WMI requirements below. 21 This field is the port number used for FTP sessions 80 This field is the port number used for HTTP forms-based login sessions. 443 The port used by the web site. 143 IMAP4 User 143 and IMAP4 This component monitor uses these ports when used with a Experience 993 Microsoft Exchange mail server. IMAP4 User Experience IMAP4 Port sessions 25 SMTP This component monitor uses these ports when used with a Microsoft Exchange mail server. 143 IMAP4 This field is the port number used for IMAP 4 sessions. page 25

26 INSTALLATION GUIDE: SERVER & APPLICATION MONITOR COMPO- NENT/ MONITOR IMAP4 Port sessions IMAP4 Port sessions LDAP User Experience LDAP User Experience Linux/Unix Script Ports NNTP ODBC User Experience Oracle User Experience Oracle User Experience PORT TYPE DESCRIPTION 585 IMAP4 For Secure IMAP (IMAP4-SSL), use port IMAP4 For IMAP4 over SSL (IMAPS), use port The port used for LDAP connections. 636 For LDAP over SSL, use port This field allows you to specify the port number used for the SSH connection. 119 UDP This field is the port number used for NNTP connections TCP This component monitor uses port TCP/ 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 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 See TCP This monitor uses RPC, requiring the following ports: Counter description TCP/135 RPC/named pipes (NP) TCP 139 RPC/NP TCP 445 RPC/NP UDP 137 page 26

27 COMPO- NENT/ MONITOR PORT TYPE DESCRIPTION POP3 POP3 User Experience 110 (default) RPC/NP UDP 138 This field is the port number used for POP3 connections. POP3 POP3 User Experience POP3 User Experience SMTP SMTP 995 For Secure POP3 (SSL-POP) use port SMTP This component uses port 25 for SMTP sessions. 465 SSMTP For Secure SMTP (SSMTP), use port 465. POP3 See Description This component monitor uses the following ports when used with a Microsoft Exchange mail server. POP3 User Experience 110 (default) 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 This field is the port number used for POP3 sessions. The default value is 110. For Secure POP3 (SSL-POP) use port 995. It also uses an SMTP Port, port 25 for SMTP sessions. page 27

28 INSTALLATION GUIDE: SERVER & APPLICATION MONITOR COMPO- NENT/ MONITOR PORT TYPE DESCRIPTION Process Process WMI SNMP This component monitor uses SNMP communication. Uses WMI communication to test if the specified Windows process is running and uses RPC communication to test if the specified Windows process is running. RADIUS User Experience This field is the RADIUS protocol authentication port. The default value is Cisco devices may require port This field is the RADIUS protocol accounting port. The default value is Cisco devices may require port RWHOIS Port SQL Server User Experience TACACS+User Experience Tomcat Server VMware Performance Counter ESX Hardware ing 4321 This template tests the ability of an RWHOIS server to accept incoming sessions on port This component monitor only works if Microsoft SQL Server is using the default port If you have a Microsoft SQL Server database that uses a non-standard port, you cannot monitor it using the SQL Server User Experience monitor. You need to use the ODBC User Experience monitor instead to manually define a connection string that will allow you to talk to Microsoft SQL Server on its custom port. 49 This field is the TACACS+ protocol connection port. The default value is This field allows you to specify the port number used by the web site. The default value for this field is Port number to use for VMware API. The default is Ensure port 5989 is open on the firewall. page 28

29 COMPO- NENT/ MONITOR Windows Event Log PORT TYPE DESCRIPTION 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 port 110 SAM Templates Template port requirements will vary depending on how you utilize them. The following provides a list of monitor templates that use ports. TEMPLATE PORT DESCRIPTION Blackberry Delivery Confirmation template 25 Blackberry Delivery Confirmation template uses port 25 on the SMTP server for sending the test . If the SMTP server uses a different port, change this value. Finger Port 79 This template tests the ability of the Finger service to accept incoming sessions on port 79. Gopher Port 70 This template tests the ability of a Gopher server to accept incoming sessions on port 70. IRC Port 6667 This template tests the ability of an IRC server to accept incoming sessions on port Java Application Server (SNMP) template 1161 This template is configured to send SNMP requests on port SNPP Port 444 This template tests the ability of an SNPP server to accept incoming sessions on port 444. Windows FTP Server (via WMI) 21 This template monitors the Windows FTP Publishing Service and tests the ability of the FTP server to accept incoming sessions on port 21. page 29

30 INSTALLATION GUIDE: SERVER & APPLICATION MONITOR SAM WMI Requirements Microsoft Windows by default uses a random port between 1024 and for WMI communications. You must create firewall exceptions to allow TCP/UDP traffic on ports or the component monitors and templates that use WMI will not work. Important: WMI requires local administrator credentials. The following component monitors use WMI: Performance Counter Process WMI (if script uses WMI access) Windows Event Log Windows PowerShell (if script uses WMI access) Windows Script Windows Service (if script uses WMI access) The following templates use WMI: Active Directory 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 Client Access Role Services Exchange 2007 Client Access Role WMI Counters Exchange 2007 Common WMI Counters Exchange 2007 Edge Transport Role Services Exchange 2007 Hub Transport Role Services Exchange 2007 Hub Transport Role WMI Counters Exchange 2007 Mailbox Role Services Exchange 2007 Mailbox Role WMI Counters Exchange 2007 Unified Messaging Role Services Exchange 2007 WMI Counters Exchange 2010 Client Access Role Services Exchange 2010 Common Performance Counters Exchange 2010 Edge Transport Role Services Exchange 2010 Hub Transport Role Services page 30

31 Exchange 2010 Mailbox Role Services Exchange 2010 Unified Messaging Role Services 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 Multi-module system guidelines If you are installing more than one SolarWinds Orion Platform product, use these recommended guidelines for hardware and software deployment. The information here should be considered guidelines only. You can choose to use more or less hardware, but your performance may vary depending on your deployment scenario. If you have only one SolarWinds Orion module, see the system requirements listed in the installation guide for that module. Small deployment guidelines Modules Choose up to 3 modules: NPM SL100 - SL500 (including up to 10 remote agents for DPI) SAM AL150 - AL300 WPM 5 - WPM 20 VNQM IPSLA 5 - IPSLA 25 (up to 5,000 operations) NCM DL50 - DL200 IPAM IP IP4000 UDT UT You can install NTA as part of a small deployment, but it is not included in this configuration. Use the Medium Deployment guidelines for NTA. Orion server specifications Physical server or virtual machine Quad core processor or better 8-16 GB RAM 150 GB, 15,000 RPM page 31

32 INSTALLATION GUIDE: SERVER & APPLICATION MONITOR 1 x 1 Gb dedicated NIC Windows Server 2016, 2012 R2, or 2012 The SolarWinds Orion installer installs IIS (32-bit mode) and.net if they are not already on your server. SQL database server specifications Physical server recommended Quad core processor or better 16 GB RAM 100 GB 1 (or more) storage in RAID 1+0 configuration (RAID 5 not supported) Windows Server 2016, 2012 R2, or 2012 SQL Server 2017, 2016, 2014, or 2012 Standard Edition 1 More or less space may be needed depending on your data retention policies, number of elements measured, and polling frequency. Medium deployment guidelines Modules NPM SL500 - SL2000 NTA for NPM SL ,000 FPS received sustained on the main poller 2-4 additional modules: SAM AL700 - AL1100 WPM 50 - WPM 200 VNQM IPSLA 25 - IPSLA 50 (up to 10,000 operations) NCM DL500 - DL1000 IPAM IP16,000 UDT UT10,000-25,000 Orion server specifications Physical server or virtual machine Quad core processor or better 16 GB RAM 150 GB, 15,000 RPM 1 x 1 Gb dedicated NIC Windows Server 2016, 2012 R2, or 2012 The SolarWinds Orion installer installs IIS (32-bit mode) and.net if they are not already on your server. page 32

33 SQL database server specifications Physical server recommended Dual quad core processor or better 64 GB RAM 250 GB 2 (or more) storage in RAID 1+0 configuration (RAID 5 not supported) Hardware RAID Controller (software RAID not supported) Windows Server 2016, 2012 R2, or 2012 SQL Server 2017, 2016, 2014, or 2012 Standard Edition NTA Flow Storage database server specifications Physical server or virtual machine Quad core processor or better 16 GB 3 RAM 100 GB - 1 TB 4 of storage capacity on local NTFS disk 1 x 1 Gb dedicated NIC Windows Server 2012 R2 or More or less space may be needed depending on your data retention policies, number of measured elements, and polling frequency. 3 Increase the NTA Flow Storage database RAM as the database size increases. 4 More or less space may be required, depending on your data retention policies and the number of stored flows. You need approximately 8 GB of additional storage for every 1000 flows retained for 30 days. For example, if you want 50,000 flows stored for 30 days, you need a base of 100 GB plus an additional 400 GB of storage. NTA-specific information NTA 4.0: if the server is running a 32-bit operating system, NTA 4.0 stores the flow data in the SQL database (NTA Flow Storage database is not installed). For more information, see NTA 4.0 Installation: Frequently Asked Questions. NTA 4.1 requires a 64-bit operating system. SolarWinds recommends a separate NTA Flow Storage database. Large deployment guidelines Modules NPM SLX (with multiple pollers) NTA for NPM SLX 50,000 FPS received sustained on the main poller Up to 6 pollers (5 in addition to the main poller) for 300,000 FPS received sustained page 33

34 INSTALLATION GUIDE: SERVER & APPLICATION MONITOR Any combination of these modules: SAM ALX 1 APE for every 10,000 component monitors Maximum of 50,000 component monitors per primary Orion SAM server + 4 APEs VNQM IPX ~5,000 IP SLA operations per polling engine NCM DLX 1 APE for every 10,000 devices, for NCM 7.1 and later Maximum of 30,000 devices per NCM instance (that is, NCM server + 2 NCM APEs) IPAM IPX 750,000 IP UDT UTX 150,000 ports per polling engine Orion server specifications Physical server or virtual machine (VM) Quad core processor or better 32 GB RAM 150 GB, 15,000 RPM 1 x 1 Gb dedicated NIC Windows Server 2016, 2012 R2, or 2012 The SolarWinds Orion installer installs IIS (32-bit mode) and.net if they are not already on your server. SQL database server specifications Physical server recommended Dual/quad core processor or better 128 GB RAM Hardware RAID Controller (software RAID not supported) Disk Subsystem 1 Array 1: 2 x 146 GB 15,000 disks RAID 1 (mirroring) operating system Disk Subsystem 2 Array 2: 2 x 146 GB 15,000 disks RAID 1 (Pagefile + extra storage) Disk Subsystem 3 Array 3: with 6x 15, GB or 300 GB disks configured in a RAID 1+0 arrays to allow for maximum write performance. This is for your SQL MDF AND FILEGROUPS page 34

35 Disk Subsystem 4 Array 4: with 4x 15, GB or 300 GB disks configured in a RAID 1+0 arrays to allow for maximum write performance. This is 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 1 Gb LAN port Windows Server 2016, 2012 R2, or 2012 Enterprise Edition SQL Server 2017, 2016, 2014, or 2012 Enterprise Edition NTA Flow Storage database server specifications Physical server or virtual machine Quad core processor or better 16 GB 3 RAM 100 GB - 1 TB 4 of storage capacity on local NTFS disk 1 x 1 Gb dedicated NIC Windows Server 2012 R2 or 2012 Additional Polling Engine server specifications Virtual machine recommended Quad core processor or better 32 GB RAM 150 GB, 15,000 RPM 1 x 1 Gb dedicated NIC Windows Server 2016, 2012 R2, or 2012 The SolarWinds Orion installer installs IIS (32-bit mode) and.net if they are not already on your server. 3 Increase the NTA Flow Storage database RAM as the database size increases. NTA-specific information NTA 4.0: if the server is running a 32-bit operating system, NTA 4.0 stores the flow data in the SQL database (NTA Flow Storage database is not installed). For more information, see NTA 4.0 Installation: Frequently Asked Questions. NTA requires a 64-bit operating system. SolarWinds recommends a separate NTA Flow Storage database. page 35

36 INSTALLATION GUIDE: SERVER & APPLICATION MONITOR SAM installation checklist Before installing, complete the pre-installation checklist below. This checklist helps you: Verify that system requirements are met, all required software is installed, and required roles and features are enabled. Gather the information required to complete the installation. Review release notes Review system requirements Review Server & Application release notes and available documentation in the Success Center. Make sure your environment has all of the required hardware, software, and database requirements for your installations: previous If you are installing into an existing Orion Platform installation, confirm that your environment meets the system requirements. If this is the first Orion Platform product that you are installing, ensure that your environment meets the system requirements. Prepare product license Review your current product licenses and determine if you need to make any changes. You can download any updated license keys through the Customer Portal. If you need to modify your licenses, contact your SolarWinds account manager or SolarWinds. Gather credentials Make sure you have all account credentials, SQL database credentials, your SolarWinds account, and local admin server credentials. Use the Local Administrator Account for installation. The Local Administrator Account is not the same as a domain account with local admin rights. A domain account is subject to your domain group policies. To download SolarWinds products and licenses, you need a SolarWinds Customer Portal account. To create your SolarWinds account, see Access the Customer Portal. Schedule the installation Set up the maintenance window, preferably during off-peak hours. Depending on the number of products, size of databases, and size of environment, you may need hours to complete your installation. page 36

37 Installations in an existing Orion Platform environment require polling engines and SolarWinds services to be offline for a length of time, causing you to lose a portion of polling data. Notify your company Send a message to your company about the installation schedule and maintenance window. If you need additional help with the installation process, contact and allocate staff to be available. Prepare for the install As part of your preflight, prepare the SAM server or update the existing Orion environment: 1. Prepare the environment For new server installations, build the servers based on your deployment size and system requirements, including the Orion SQL server and database. For installations into an existing Orion Platform, verify that enough drive space is available for installations. Products may require significant space for the downloaded installation ZIP file and installation process. If adding SolarWinds High Availability (HA) into your environment, review the HA requirements and VIP address information. Prepare two matching servers for installation. 2. Run all Windows updates 3. Backup existing database Before installation, check for and run all Microsoft Windows Updates on all servers. As you install, if a Windows update runs, your system may reboot as needed by Windows. The installation cannot complete if your system is waiting to reboot. If you are installing with an existing database, back up the database. If you need help, check your vendor's site for documentation and instructions. If you have your database on a VM, create a snapshot or copy of your VM. 4. Open ports according to requirements 5. Check for antivirus software For your server ports and firewall, open ports according to the port requirements. Orion uses these ports to send and receive data. Determine if any antivirus software is installed on the server or servers where you plan to install. To ensure the installation goes smoothly, exclude the SolarWinds directory. For example, on Windows Server 2012 R2, exclude C:\ProgramData\SolarWinds\. For a full list of antivirus exclusions, see Files and directories to exclude from antivirus scanning. Do not exclude executable files. SolarWinds assumes that C:\ is the default volume. page 37

38 INSTALLATION GUIDE: SERVER & APPLICATION MONITOR Installation gotchas Consider the following gotchas for installing SAM: When installing with Dell Carbon Black installed, we recommend stopping or removing Carbon Black. This security product causes issues with MSMQ starting. For details, please see this article. Carefully review Windows Server OS and Microsoft SQL Server versions for your SAM installation. Later versions support installs on later versions of these Microsoft servers. For later versions of SAM, verify the proper ports are opened including 5671 (Rabbit MQ messaging), (agent communication to 2008 R2 SP1), and (SW Information Service, agent communication to 2012). When installing into an existing Orion environment with High Availability enabled, you must disable High Availability before you can install. You must have the same versions of SolarWinds products on your primary and secondary server before you can re-enable your HA pools. See details, see Install SAM with High Availability. Only use SQL Express for evaluation installations. SolarWinds recommends a Microsoft SQL database on a dedicated server. When installing SAM into a multiple product Orion environment, consider the following: Install SAM on the Orion server with other products including NPM, NCM, NTA, and SRM. Installing products on the same server provides a single pane of glass for monitoring: consolidates polling calls and traffic through polling methods, stores and tracks nodes in one system without cross-referencing, provides data for alerts and reports on one system, and manages all logic easily on one system. Select the same Orion SQL database used by the current Orion Platform environment. If you need to migrate Orion products and install SAM on a new server due to requirements, migrate the Orion products first. See the SolarWinds Migration Guide for instructions. page 38

39 Prepare the SAM SQL database When installing SAM as a stand-alone product, you need to prepare a dedicated server for an SQL server. If you are installing SAM into an existing Orion Platform environment, you only need specific information to configure SAM to point to that database including the credentials and location. The SolarWinds Orion database stores all monitoring data. Use these guidelines to configure the database before you install and configure SAM. If you need help installing the SQL Server database, refer to the guidelines provided by Microsoft. Important: Install the SQL database on a dedicated server. You should not install it on the Orion server. Make sure the database and database server meet the system requirements. SolarWinds recommends following recommended sizing values for CPU, memory, and harddrive space. Ensure that you install the Orion database and the Orion Server on the same domain. The selected SQL Server instance must support mixed-mode or SQL authentication with strong passwords. A strong password must meet at least three of the following four criteria: Contains at least one uppercase letter Contains at least one lowercase letter Contains at least one number Contains at least one non-alphanumeric character, for example, #, %, or ^ For a new database, the user account must be a member of the dbcreator server role. The sysadmin role and the security administrator (SA) user account are always members of dbcreator. For a new SQL account, the user account must be a member of the securityadmin server role. The sysadmin role and the security administrator user account are always members of securityadmin. For an existing database, the user account needs only to be in the db_owner database role for the existing database. Set the recovery model of the database to Simple. SolarWinds does not support other methods. Select SQL Server Authentication. SolarWinds Orion users use this method to access the SolarWinds Orion database. SolarWinds recommends using SQL Server Authentication to ensure the SolarWinds Orion server can always access the SolarWinds Orion database, even when hosted remotely on a separate server. page 39

40 INSTALLATION GUIDE: SERVER & APPLICATION MONITOR Helpful tip: After finishing your SAM installation and configuration, create a backup or snapshot of the database. If you encounter issues with further modifications or updates, you will have a working baseline of settings and data. As you continue using Orion products, you should actively maintain and manage the Orion SQL database. See Best practices for managing your Orion database for tips, tricks, and maintenance recommendations. page 40

41 Install Orion Stand-alone SAM These instructions provide stand-alone installation steps for installing SolarWinds Server & Application on a dedicated server. If installing on an existing Orion server, see Integrate SAM with an existing Orion Platform. Before installation, prepare a server according to SAM requirements, set port requirements, and check the preflight checklist. If you have High Availability as part of your Orion Platform installation, review Install SAM with High Availability. For advanced configuration requirements and steps such as High Availability and Orion agents, see the SAM Administrator Guide. 1. Download installation files and license from Customer Portal 2. Run the installation file 3. Complete the Installation wizard If you have not yet created a SolarWinds account, see Access the Customer Portal to create an account. 1. Go to customerportal.solarwinds.com. 2. In the Log In tab, enter your organization's SWID and your address. 3. In the Latest Downloads table, click Choose Download for the installation files for your product. The file name for SAM installations is SolarWinds-SAM- <version>-full.exe, such as SolarWinds-SAM-6.4-Full.exe. 1. Log in as an administrator to the SAM server. 2. Extract the contents of the downloaded installation ZIP file to the server. 3. Run the installer. 1. Click Next on the Welcome window. The system scans the environment to ensure that the system requirements are met. If your system is not compatible, the installer provides a link to a knowledge base article with the resolution. When resolved, run the installation again. 2. Accept the terms of the license agreement. 3. Accept the default directory, or click Browse and select a directory. 4. Enable Quality of Experience (QoE) traffic monitoring. Enabling QoE installs an agent on the Orion Main Polling Engine. This agent collects packet-level traffic statistics, like network response time and application response time, for any application traffic it sees going to or from Orion. SolarWinds recommends that you enable QoE. page 41

42 INSTALLATION GUIDE: SERVER & APPLICATION MONITOR 5. Click Next to begin copying the files. Downloading and installing Microsoft.NET Framework 4.5 can take more than 20 minutes. If your system reboots, run the installation again. If you are using Microsoft Internet Explorer, SolarWinds recommends you add the URL of your Orion website ( the URL of SolarWinds support ( and about:blank to the list of trusted sites. 6. When complete, the installer may prompt you to activate SAM. Enter the license key from the Customer Portal. If you need the key: a. In the Customer Portal, select License Management. b. Select the product. c. Copy the license key. 4. Run the Configuration wizard After the installation completes, the Configuration wizard automatically runs. If the Configuration wizard does not load automatically, start the Configuration wizard in the SolarWinds Orion > Configuration and Auto-Discovery program folder. 1. In the Welcome dialog box, click Next. 2. If prompted to stop services, click Yes. 3. In the Database Settings dialog box, select an SQL Server and authentication method, and click Next. Use SQL Server Authentication to ensure the SolarWinds Orion server can always access SQL Server, even when hosted remotely on a separate server. 4. In the Database Settings dialog box, select a database from Use an existing database, and click Next. page 42

43 5. In the Database Account dialog box, create an account or use an existing account that the polling engine and Web Console use to access the database, and click Next. 6. In the Website Settings dialog box: a. Select All Unassigned unless your environment requires a specific IP address for the Orion Web Console. b. Specify the Port and the Website Root Directory where the system installs the Web Console files. If you specify any port other than 80, include that port in the URL used to access the Web Console. c. To use this function, click Yes - Enable automatic login using Windows Authentication. 7. If prompted to create a directory or website, click Yes. 8. Review the list of services to install, and click Next. 9. Click Yes if prompted to disable the SNMP Trap Service and enable the SolarWinds Trap Service. 11. In the Completing the Orion Configuration Wizard dialog box, click Next. 12. When completed, click Finish to launch the Orion Web Console. 13. Log in with user name admin and leave the password field blank. For security purposes, SolarWinds recommends that you change the password to your admin account. 5. Install any available If the Customer Portal listed hotfixes for the product version you downloaded, run those installations. For a list of available hotfixes, see this article. page 43

44 INSTALLATION GUIDE: SERVER & APPLICATION MONITOR hotfixes (optional) 6. Install on the additional polling engine (optional) 1. Download the zip file. 2. Extract the zip files to the main polling engine or Orion server. 3. Review the README for details on the release and further instructions. 4. Run the installation file according to the README instructions. If you have an additional polling engine (APE), download and install the product using the Scalability Engine Installer. 1. In the Orion Web Console, click Settings > All Settings > Polling Engines. 2. Click the Download Installer Now and move the downloaded file to the additional polling engine server. 3. Run the installation file. The steps should mirror the installation steps completed on the main polling engine server. During installation, select the option for Additional Polling Engine. 4. To activate the license, access the Orion Web Console on the main polling engine or Orion server. Do not activate the license directly on the additional polling engine. 5. Click Settings > All Settings > License Manager. 6. Click Add/Upgrade License. 7. Enter the Activation Key and Registration Information, and click Activate. 8. You may need to assign the license to the additional polling engine. a. Click Assign. b. Select the additional polling engine and click Assign. 9. Repeat these instructions for multiple additional polling engines. Best Practice: If the product included hotfixes, you can also run those directly on the additional polling engines. The Scalability Engine Installer should have included them. If the hotfix installation states the fixes are already installed, do not continue. Otherwise, complete the installation instructions from the README file. 7. Install on the additional web server (optional) If you have an additional web server (AWS), download and install the product using the Scalability Engine Installer. 1. In the Orion Web Console, click Settings > All Settings > Web Console Settings. 2. Click the Download Installer Now and move the downloaded file to the additional polling engine server. 3. Run the installation file. The steps should mirror the installation steps completed on the main polling engine server. During installation, select the option for Additional Web Server. page 44

45 4. To activate the license, access the Orion Web Console on the main polling engine or Orion server. Do not activate the license directly on the additional polling engine. 5. Click Settings > All Settings > License Manager. 6. Click Add/Upgrade License. 7. Enter the Activation Key and Registration Information, and click Activate. 8. You may need to assign the license to the additional web server. a. Click Assign. b. Select the additional web server and click Assign. Best Practice: If the product included hotfixes, you can also run those directly on the additional web server. The Scalability Engine Installer should have included them. If the hotfix installation states the fixes are already installed, do not continue. Otherwise, complete the installation instructions from the README file. Install complete! SAM is part of the Orion Web Console, accessed through a web browser. You can access the page through a shortcut added to your programs. When opened, bookmark the page for ease of returning. 1. Click Start > All Programs > SolarWinds Orion > Orion Web Console. 2. The SolarWinds Web Console is displayed. You can log in by default by entering the name Admin and no password. Click Login. To access from another computer, access a web browser and enter the IP or domain name for the Orion server. The Orion Web Console should load with a login screen. If you installed into an existing Orion environment, use the credentials for your Orion account. page 45

46 INSTALLATION GUIDE: SERVER & APPLICATION MONITOR The first time you access the Orion Web Console, you log in with a username of admin and no password. You should immediately change the password through Settings > All Settings > Manage Accounts. If your installation completed successfully, you should see the next screen: To access SAM resources, data, and application management options, click My Dashboards > Applications. For the best way to get started, check the SAM Getting Started Guide. page 46