Layton ServiceDesk - Installation - Migration - Application Only
From Layton Support
(Difference between revisions)
m (Minor text changes) |
(Major revision) |
||
| Line 3: | Line 3: | ||
__FORCETOC__ | __FORCETOC__ | ||
=Overview= | =Overview= | ||
| + | This procedure would be used when you need to move the application to a new server, but leave the database on the existing SQL server. | ||
| + | |||
We highly recommend that you do not commit to the migrated installation until you are sure that the application is working without issues. | We highly recommend that you do not commit to the migrated installation until you are sure that the application is working without issues. | ||
| Line 10: | Line 12: | ||
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. | 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. | ||
| − | + | =Procedure= | |
| − | + | #Back up the existing application installation directory. The default path is: ''C:\Program Files (x86)\Layton Technology\Layton ServiceDesk\'' | |
| − | + | #Back up your database. | |
| − | + | #Restore the backup of your database with a different name, for testing. | |
| − | + | ||
| − | # | + | |
#Check your destination server against the '''[[Layton ServiceDesk - System Requirements|System Requirements]]'''. | #Check your destination server against the '''[[Layton ServiceDesk - System Requirements|System Requirements]]'''. | ||
#Run your destination server through the '''[[Layton ServiceDesk - Pre-Installation Procedure|Pre-Installation Procedure]]'''. | #Run your destination server through the '''[[Layton ServiceDesk - Pre-Installation Procedure|Pre-Installation Procedure]]'''. | ||
Revision as of 03:54, 22 June 2017
Contents |
Overview
This procedure would be used when you need to move the application to a new server, but leave the database on the existing SQL server.
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 here 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.
Procedure
- Back up the existing application installation directory. The default path is: C:\Program Files (x86)\Layton Technology\Layton ServiceDesk\
- Back up your database.
- Restore the backup of your database with a different name, for testing.
- Check your destination server against the System Requirements.
- Run your destination server through the Pre-Installation Procedure.
- Install as per New Installation
- When the Database Tool opens, choose Connect to an existing database and point it to your ServiceDesk database
- 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\Editor_Folder\Image\ - User images added to email bodies configured in Email Settings & Bodies
- 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
- Follow this procedure to remap the application support path.
- If you are not running the latest version, update immediately. Refer to the latest release notes for details.
