Revision as of 23:05, 13 September 2015

Back to Contents

Overview

We highly recommend that you do not commit to the migrated installation until you are sure that the application is working without issues.

Version

Check the application version on your live installation. Check the main wiki page for the latest version.

If you are not running the latest version on your source installation, please contact Support for the version you are running. You will be provided with a link to the latest full version for use in the below procedures.

Migrating the Application Only

Use Case

This would be when you need to move the application to a new server, but leave the database on the existing SQL server.

Procedure

1. Backup the existing application installation directory. The default path is: C:\Program Files (x86)\Layton Technology\Layton ServiceDesk\
2. Check your destination server against the System Requirements.
3. Run your destination server through the Pre-Installation Procedure.
4. Install as per New Installation
5. When the Database Tool opens, choose Connect to an existing database and point it to your ServiceDesk database
6. Copy the needed files from the backup made in Step 1 to your new application installation directory. Some common items that may need migrated are:
   • Application_Images\ - If custom images were added to any forms in Form Design
   • HB_Data\ChangeAttach\ - File attachments for Changes
   • HB_Data\EmailBodies\ - Email notifications configured in Email Settings & Bodies
   • HB_Data\MailIn\ - File attachments for emails in the Incoming email queue
   • HB_Data\ProblemAttach\ - File attachments for Problems
   • HB_Data\RequestAttach\ - File attachments for Requests
   • HB_Data\LogFiles\ - Application log files
7. Follow this procedure to remap the application support path.
8. If you are not running the latest version, update immediately.

Migrating Application and Database

Use Case

When you need to move both application and database to another or other servers.

Procedure

1. Backup the existing application installation directory. The default path is: C:\Program Files (x86)\Layton Technology\Layton ServiceDesk\.
2. Backup the existing database using Microsoft SQL Server Management Studio (SSMS).
3. Restore the database backup to the new SQL Server using SSMS.
4. Check your destination server against the System Requirements.
5. Run your destination server through the Pre-Installation Procedure.
6. Install the application on the new server as per New Installation.
7. When the Database Tool opens, choose Connect to an existing database and point it to your ServiceDesk database restored on the new SQL Server in Step 3.
8. Copy the needed files from the backup made in Step 1 to your new application installation directory. Some common items that may need migrated are:
   • Application_Images\ - If custom images were added to any forms in Form Design
   • HB_Data\ChangeAttach\ - File attachments for Changes
   • HB_Data\EmailBodies\ - Email notifications configured in Email Settings & Bodies
   • HB_Data\MailIn\ - File attachments for emails in the Incoming email queue
   • HB_Data\ProblemAttach\ - File attachments for Problems
   • HB_Data\RequestAttach\ - File attachments for Requests
   • HB_Data\LogFiles\ - Application log files
9. Follow this procedure to remap the application support path.
10. If you are not running the latest version, update immediately.

Migrating Database Only

Use Case

When you need to move just the database to another SQL server.

Procedure

1. Backup the existing database using Microsoft SQL Server Management Studio (SSMS).
2. Restore the database backup to the new SQL Server using SSMS.
3. Follow these instructions to connect to the migrated database.

Back to Contents