|
|
| Line 14: |
Line 14: |
| | | | |
| | ==Procedure== | | ==Procedure== |
| − | #Backup the existing application installation directory. The default path is: ''C:\Program Files (x86)\Layton Technology\Layton ServiceDesk\''
| + | '''[[Layton ServiceDesk™ - Installation - Migration - Application Only|Migration - Application Only]]''' |
| − | #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]]'''.
| + | |
| − | #Install as per '''[[Layton ServiceDesk™ - Installation - New Installation|New Installation]]'''
| + | |
| − | #When the Database Tool opens, choose '''[[Layton_ServiceDesk™_-_Installation_-_Connect_to_Existing_Database|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 '''[[Layton_ServiceDesk™_-_Configuring_the_System_-_Form_Design|Form Design]]'''
| + | |
| − | #*''HB_Data\ChangeAttach\'' - File attachments for '''[[Layton_ServiceDesk™_-_Logging_A_New_Change#Change_Logging|Changes]]'''
| + | |
| − | #*''HB_Data\EmailBodies\'' - Email notifications configured in '''[[Layton_ServiceDesk™_-_Settings_-_Libraries_-_Email_Settings_%26_Bodies|Email Settings & Bodies]]'''
| + | |
| − | #*''HB_Data\MailIn\'' - File attachments for emails in the '''[[Layton_ServiceDesk™_-_Logging_A_New_Request#Converting_an_Incoming_Email_into_a_Request|Incoming email queue]]'''
| + | |
| − | #*''HB_Data\ProblemAttach\'' - File attachments for '''[[Layton_ServiceDesk™_-_Logging_A_New_Problem#Problem_Logging|Problems]]'''
| + | |
| − | #*''HB_Data\RequestAttach\'' - File attachments for '''[[Layton_ServiceDesk™_-_Logging_A_New_Request#Overview|Requests]]'''
| + | |
| − | #*''HB_Data\LogFiles\'' - Application log files
| + | |
| − | #Follow '''[[Layton ServiceDesk™ - General Troubleshooting - PDF Report Not Attached to Scheduled Report Email|this procedure]]''' to remap the application support path.
| + | |
| − | #If you are not running the latest version, update immediately.
| + | |
| | | | |
| | =Migrating Application and Database= | | =Migrating Application and Database= |
| Line 35: |
Line 21: |
| | | | |
| | ==Procedure== | | ==Procedure== |
| − | #Backup the existing application installation directory. The default path is: ''C:\Program Files (x86)\Layton Technology\Layton ServiceDesk\''.
| + | '''[[Layton ServiceDesk™ - Installation - Migration - Application and Database|Migration - Application and Database]]''' |
| − | #Backup the existing database using Microsoft SQL Server Management Studio (SSMS).
| + | |
| − | #Restore the database backup to the new SQL Server using SSMS.
| + | |
| − | #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]]'''.
| + | |
| − | #Install the application on the new server as per '''[[Layton ServiceDesk™ - Installation - New Installation|New Installation]]'''.
| + | |
| − | #When the Database Tool opens, choose '''[[Layton_ServiceDesk™_-_Installation_-_Connect_to_Existing_Database|Connect to an existing database]]''' and point it to your ServiceDesk database restored on the new SQL Server in Step 3.
| + | |
| − | #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 '''[[Layton_ServiceDesk™_-_Configuring_the_System_-_Form_Design|Form Design]]'''
| + | |
| − | #*''HB_Data\ChangeAttach\'' - File attachments for '''[[Layton_ServiceDesk™_-_Logging_A_New_Change#Change_Logging|Changes]]'''
| + | |
| − | #*''HB_Data\EmailBodies\'' - Email notifications configured in '''[[Layton_ServiceDesk™_-_Settings_-_Libraries_-_Email_Settings_%26_Bodies|Email Settings & Bodies]]'''
| + | |
| − | #*''HB_Data\MailIn\'' - File attachments for emails in the '''[[Layton_ServiceDesk™_-_Logging_A_New_Request#Converting_an_Incoming_Email_into_a_Request|Incoming email queue]]'''
| + | |
| − | #*''HB_Data\ProblemAttach\'' - File attachments for '''[[Layton_ServiceDesk™_-_Logging_A_New_Problem#Problem_Logging|Problems]]'''
| + | |
| − | #*''HB_Data\RequestAttach\'' - File attachments for '''[[Layton_ServiceDesk™_-_Logging_A_New_Request#Overview|Requests]]'''
| + | |
| − | #*''HB_Data\LogFiles\'' - Application log files
| + | |
| − | #Follow '''[[Layton ServiceDesk™ - General Troubleshooting - PDF Report Not Attached to Scheduled Report Email|this procedure]]''' to remap the application support path.
| + | |
| − | #If you are not running the latest version, update immediately.
| + | |
| − | | + | |
| | =Migrating Database Only= | | =Migrating Database Only= |
| | ==Use Case== | | ==Use Case== |
| Line 58: |
Line 27: |
| | | | |
| | ==Procedure== | | ==Procedure== |
| − | #Backup the existing database using Microsoft SQL Server Management Studio (SSMS).
| + | '''[[Layton ServiceDesk™ - Installation - Migration - Database Only|Migration - Database Only]]''' |
| − | #Restore the database backup to the new SQL Server using SSMS.
| + | |
| − | #Follow '''[[Layton ServiceDesk™ - Installation - Connect to Existing Database|these instructions]]''' to connect to the migrated database.
| + | |
| | <p align="right">[[File:btn_back_up.png|link=User Guide for Layton ServiceDesk™]] [[User Guide for Layton ServiceDesk™|<u>Back to Contents</u>]]</p> | | <p align="right">[[File:btn_back_up.png|link=User Guide for Layton ServiceDesk™]] [[User Guide for Layton ServiceDesk™|<u>Back to Contents</u>]]</p> |
We highly recommend that you do not commit to the migrated installation until you are sure that the application is working without issues.
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.
This would be when you need to move the application to a new server, but leave the database on the existing SQL server.
When you need to move both application and database to another or other servers.
