All Collections
General
Migrating your hosting server to a new server
Migrating your hosting server to a new server
A
Written by Aiden Morris
Updated over a week ago

This tutorial will walk you through the steps to migrate a Pulseway Enterprise Server from one system to another while keeping the same DNS record (server name). To change the server name, contact our support team.

Step 1: Preparing the new server (Minimum requirement)

  • Windows Server 2012 or higher

  • MS SQL Server 2012 or higher (Express Edition or higher)

  • Pulseway Enterprise Server Installer link

  • Pulseway Enterprise installer code

After setting up the new server with SQL, proceed to download and install the Pulseway Enterprise Server Installer on the new server, then enter the installer code.

Installer link: https://www.pulseway.com/download/Installer2.exe

Please note that the installer code will be provided by your Account Manager.

Step 2: Backup, Relocate and Install

Important: Do not update the DNS record or NAT rule to point to the new server until the new server has been fully set up.

Backup:

On the old hosting server create a backup of the following:

  • Pulseway Hosting folder (usually located on the C:\ partition)

  • pcmonitor database from SQL Server

  • SSL certificate used by the Pulseway Enterprise Server (PFX container)

Relocate and Install:

Transfer backups to the new server and initiate Pulseway Enterprise Server installation. When asked for the server name, input the old server's name and locate the correct SSL certificate in the PFX container. For licensing, choose "I already have a license," then load the .pcmlx file from the Hosting folder backup. The license's Product Key is in Hosting\key.txt.

Step 3: Restore and Mapping

With the enterprise server installed, skip account creation and close the Pulseway Admin app.
Restore the database backup to overwrite new database data. Open Pulseway Admin and ensure accounts exist.

Afterward, update the DNS record to the new server or adjust the NAT rule for HTTPS connections, or exchange IP addresses between servers.


Step 4: Integrity checks

Now that everything is moved to the new server, verify that email notifications are working, reports are generated properly, and that all agents are connecting with no problems.

At this point, the old server can be safely decommissioned from production use.

For further assistance please email support (support@pulseway.com)

Did this answer your question?