- Release Notes
- WHD 12.8.5 Hotfix 1 release notes
- WHD 12.8.5 release notes
- WHD 12.8.4 release notes
- WHD 12.8.3 Hotfix 3 release notes
- WHD 12.8.3 release notes
- WHD 12.8.2 release notes
- WHD 12.8.1.824 release notes
- WHD 12.8.1 release notes
- WHD 12.8.0 Release Notes
- WHD 12.7.13 Release Notes
- WHD 12.7.12 Release Notes
- WHD 12.7.11 Release Notes
- WHD 12.7.10 Release Notes
- WHD 12.7.9 Release Notes
- WHD 12.7.8 Release Notes
- WHD 12.7.7 Release Notes
- WHD 12.7.6 Release Notes
- WHD 12.7.5 Release Notes
- WHD 12.7.4 Release Notes
- WHD 12.7.3 Release Notes
- WHD 12.7.2 Release Notes
- WHD 12.7.1 Release Notes
- WHD 12.6 Release Notes
- WHD 12.5.2 release notes
- WHD 12.5.1 Release Notes
- WHD 12.5 Release Notes
- WHD 12.4.2 Release Notes
- WHD 12.4 Release Notes
- WHD release history
- WHD release notes aggregator
- Install or Upgrade
- WHD Installation and Upgrade Guide
- Introduction
- Plan for a production deployment
- Install WHD
- Uninstall WHD
- Upgrade WHD
- Prepare for the upgrade
- Determine the upgrade path to the latest WHD version
- Upgrade gotchas you should review
- Prepare your WHD environment to upgrade
- Upgrade WHD to the latest version
- Upgrade the PostgreSQL database in an existing deployment
- Restore the PostgreSQL database on a new server
- Check your WHD system after the upgrade
- Troubleshoot the WHD upgrade
- Get help after you install WHD
- Get Started
- WHD Getting Started Guide
- Introduction
- Create client accounts
- Create tech accounts and define the tech permissions
- Create tech groups and request types
- Configure ticket options
- Configure incoming and outgoing email accounts
- About incoming and outgoing email accounts
- Configure an outgoing email account
- Configure an incoming email account
- Configure an incoming email account for Gmail
- Configure an incoming email account for Microsoft 365
- Configure an outgoing email account for Microsoft 365
- Configure the email connection timeout setting
- Set up ticket creation by email
- Set up asset management
- Configure ticket types
- Train the techs
- Train the clients
- Beyond getting started with WHD
- Additional resources
- Administer
- WHD Administrator Guide
- Introduction
- Set up the application
- Setup overview
- Verify the TLS version on your WHD server
- Secure your Web Help Desk deployment
- Migrate Web Help Desk to a new server
- Configure the general settings
- Prepare the Web Help Desk database
- Set up your email accounts
- Set up your tickets
- Define your techs
- Define the ticket routing processes
- Define the approval processes
- Enter and search for a location
- Define clients
- Define assets
- Define parts and billing
- Set up the dashboard
- Add a custom logo
- Start and stop Web Help Desk Services
- Enable FIPS 140-2 compliant cryptography
- Configure and manage user authentication
- Manage clients
- Manage tickets
- Automate ticket workflows
- Manage assets
- Import and export data
- Create and edit reports
- Set up parts and billing
- Manage client feedback
- SolarWinds Platform alert integration
- Configure Orion-to-Web Help Desk ticketing
- Integrate Web Help Desk with Dameware MRC
- Knowledge-centered support
- Customize your deployment
- Frequently Asked Questions
Clear JVM heap memory
Web Help Desk deployments can fill up the JVM Heap Memory, which can degrade performance. To avoid this issue, periodically restart Web Help Desk to clear the heap memory.
See the appropriate procedure to automatically restart the operating system on your system hosting Web Help Desk.