Tools

How to migrate WHD with external Microsoft SQL database from one Windows System to another

This article describes the steps to migrate the WHD application with Microsoft SQL database from one Windows Server Operating System to another Windows Server Operating System.

First published date

10/2/2019 1:31 AM

Last published date

11/5/2019 12:29 AM

Overview

If WHD application uses an external database such as the Microsoft SQL Database, migrating is simply installing the same version of WHD on the new server and restoring the configurations on the new server. You don't have to migrate the database as it is external from the local server of WHD.

Product section

Web Help Desk

Resolution

Perform WHD full database backup in external Microsoft SQL Database Server. Please seek assistance with your DBA.
Deactivate WHD license from the old server: WHD > Setup > General > License > License Settings.
Stop WHD application in the old server: C:\Program Files\WebHelpDesk\whd_stop.bat.
Set Start-Up Type to "Disabled" for the WHD service and WHD PostgreSQL service through Windows > services.msc in the old server.
Back up the folder C:\Program Files\WebHelpDesk\conf from old server.
Install the same version of WHD on the new server.
Stop WHD application on the new server.
Back up the C:\Program Files\WebHelpDesk\conf on the new server.
Restore conf folder backup from old server to the new server on the same location C:\Program Files\WebHelpDesk\conf
Start WHD application on the new server.
Apply WHD activation key on the activation license prompt when asked for the activation key.
Click "Continue" to update the existing WHD database in Microsoft SQL Database server.
After the Getting Started Wizard, log in to your new WHD using admin account and check your Tickets, Clients, etc.
If all data are intact, stop the WHD application.
Assign the old hostname and IP of the old server to the new server. Please seek assistance with your Network or Server Administrator for assistance.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.