WHD installation requirements
This section describes the requirements for setting up a WHD deployment in a stand-alone or Orion Platform deployment.
If you plan to enable Federal Information Processing Standard (FIPS) 140-2 compliant cryptography in your deployment, see the WHD Administrator Guide for specific requirements.
Listed below are the hardware and software requirements for a WHD deployment.
|CPU||64-bit Dual Core 3.0 GHz or faster|
4 GB (up to 20 technicians)
3 GB (more than 20 technicians) plus 1 GB for every 10 additional technicians
|Hard Drive Space||20 GB (recommended)|
If you installed macOS 10.3.x (High Sierra) on your WHD server, some Tomcat web applications will fail when you start Web Help Desk after the installation. See Tomcat web applications fail after upgrading to macOS 10.13.x (High Sierra) for a workaround.
Deprecation notice: Although you can install WHD on systems running Windows Server 2012 and 2012 R2 (64-bit), these version are deprecated and will not be supported on future WHD releases.
Microsoft Windows Server
Windows Server 2012 R2 (64-bit)
Windows Server 2016 (64-bit)
Windows Server 2019
(Trial evaluation only)
Windows 7 (64-bit)
Windows 8.1 (64-bit)
Windows 10 (64-bit)
10.13.x (High Sierra)
|Red Hat Enterprise Linux (RHEL)||
RHEL 6.5 (64-bit)
RHEL 7.0 (64-bit)
CentOS 6.5 (64-bit)
CentOS 7.0 (64-bit)
Fedora 24 (64-bit)
Fedora 25 (64-bit)
|Oracle Java||Open Java Development Kit (OpenJDK ) 15.0.2|
Because of frequent Google Chrome and Mozilla Firefox updates, compatibility issues may exist between these web browsers.
|Google Chrome||Latest version|
IE 11 and later
Do not enable Enterprise Mode on Internet Explorer. This setting forces Internet Explorer to emulate version 7, which is not supported.
|Microsoft Edge||Edge 38 and later|
Server sizing requirements
Determine the requirements for your Web Help Desk deployment size.
Deployments with fewer than 20 techs
If plan to support 20 tech sessions or fewer in your deployment, you can run WHD on a system with:
- A supported operating system
- A 32-bit Java Virtual Machine (JVM)
- 4GB RAM (up to 3.7GB for the tech sessions, JVM support, operating system, and any additional services you need to run on the system)
This configuration supports 10 - 20 tech sessions with no onboard memory issues.
To adjust the maximum memory setting, edit the
MAXIMUM_MEMORY option in the
Deployments with more than 20 techs
If you plan to support more than 20 tech sessions in your deployment, SolarWinds recommends installing WHD on a system running:
- A supported operating system
- A 64-bit JVM
- 3GB RAM for 20 tech sessions plus 1GB RAM for each additional 10 tech sessions
Configure the JVM memory allocation
Calculate the amount of memory required for your JVM and increase the allocation as required.
WHD uses an embedded PostgreSQL database as its standard database. The following table lists the supported databases for WHD.
|Microsoft SQL Server||
SQL Server 2008 R2 SP3
SQL Server 2012 SP2
SQL Server 2014
SQL Server 2016
SQL Server 2017
For optimal external database performance, run WHD and a supported external database on separate servers.
Database hardware requirements
The following table lists the minimum hardware requirements for a database server running Microsoft SQL Server or MySQL with WHD.
|CPU||64-bit Dual Core 3.0 GHz or higher|
|Hard drive space||20 GB|
|RAM||3 GB with 1 GB additional RAM for every additional 10 techs|
External database options
WHD supports SQL Server 2008, SQL Server 2014, and MySQL 5.7 as external databases. You can also use an external PostgreSQL 9.2 or PostgreSQL 9.3 database with WHD 12.6 and later.
Oracle Java Database Connectivity (JDBC) driver requirements
WHD for macOS includes an embedded Java Virtual Machine (JVM). If you are running an external Oracle JVM, WHD preserves your Java settings during the installation procedure and continues to use the external Oracle JVM.
If you are migrating from an external JVM to the embedded JVM included with WHD and you are using a MySQL database, ensure that the new embedded Java directory on your Web Help Desk server includes the Oracle Java Database Connectivity (JDBC) driver.
Discovery connector requirements
The following table lists the supported discovery connectors used by WHD for asset discovery.
|Discovery Connector||Supported Versions|
|SolarWinds Network Configuration Manager (NCM)||
|SolarWinds Network Performance Manager (NPM)||
|SolarWinds Server and Application Monitor (SAM)||
|Absolute Manage (HEAT LANrev)||
Absolute Manager 7.3 (build 5642)
|Apple Remote Desktop||
Remote Desktop 3.8
Microsoft System Center Configuration Manager
SCCM 1511 (64-bit)
Web server requirements
The following table lists the supported web servers for WHD.
SolarWinds product integration requirements
The following table lists the SolarWinds products that can integrate with WHD.
To minimize port conflicts, install WHD and Dameware on separate servers. See this KB article for details.
SolarWinds Orion platform
Orion Platform 2017.1 and later
SolarWinds Network Performance Monitor (NPM)
SolarWinds Server and Application Monitor (SAM)
SolarWinds Network Configuration Monitor (NCM)
Dameware Mini Remote Control (MRC)
Dameware MRC 12.0.3
The following table lists the supported Lightweight Directory Access Protocol (LDAP) software products for WHD.
|Microsoft Active Directory||
Active Directory 2012
Active Directory 2012 R2
Open Directory 4
Mail server requirements
The following table lists the supported mail server, versions, and protocols for WHD.
|Product||Supported versions||Supported Protocols|
|Microsoft Exchange Server||
Exchange Server 2010
Exchange Server 2013 CU7
Exchange Server 2016
Web Help Desk Mobile requirements
|Platform||Supported operating systems|
The following table lists the Web Help Desk ports for Asset Recovery.
|135||TCP||Asset Discovery using WMI (WMI calls uses port 135 and then chooses a random port for further communication)|
|1521||TCP||Communication with the Oracle Java Database Connectivity (JDBC) connector for asset discovery|
|3306||TCP||Communication with the MySQL external database,
|4445||TCP||Remote log server reader|
|5433||TCP||Communication with Apple Remote 3.2 for asset discovery|
|7100||TCP||Communications with a Sybase database for asset discovery|