The guide will detail how you can refresh your Halo on-premise instance with that of another on-premise instance, such as a production instance to a UAT / Dev instance.
Throughout this guide I will reference the two instances as below:
- Source: The instance you are copying from
- Destination: The instance you are copying to
Information Gathering
To begin, you need to run the below queries on the database of the destination instance:
SELECT rdbid, rdbkey FROM CONTROL;
SELECT rdbsecret FROM CONTROL4;
and make a note of the results, as you will need them later.
It is now advised to take a backup of the source instances database, which can be used to restore it into the destination database.
Restoring the Database
Before restoring the database, you need to ensure that the destination instance is stopped in IIS.
Once it is, you can restore the destination database to the backup we exported for the source instance. A guide on how to do this is listed here: https://support.haloservicedesk.com/kb?id=2448
Setting the Keys
Once the restore is successful, you need to run the below queries on the destination instances database filling the <variables> with the information we obtained earlier.
UPDATE CONTROL SET rdbid = '<rdbid >';
UPDATE CONTROL SET rdbkey = '<rdbkey>';
UPDATE CONTROL4 SET rdbsecret = '<rdbsecret>';
Setting the URLs
For the destination instance, you need to navigate to the root folders of Halo and run the 'Config.exe' application.
Provided none of your database connection details have changed, you just need to select save:
This will then populate the URLs in the database.
Upgrading the DB
If the source instance was an older version than the destination, you will need to upgrade the database. This is done by running the 'Upgrader.exe'.
Finishing Up
You can now start the site in IIS.
