Layton ServiceDesk - Installation - Migration - Application Only
From Layton Support
(Difference between revisions)
m (Updated links) |
m (Minor text changes) |
||
| (22 intermediate revisions by one user not shown) | |||
| Line 1: | Line 1: | ||
| − | <p align="right">[[File: | + | <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=Layton ServiceDesk - Installation - Migration]] [[Layton ServiceDesk - Installation - Migration|<u>Back to ''Migration''</u>]]</p> | ||
__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. The process is to install the same version as Live on the destination server, then update. For a simplified procedure to directly install the latest version on the destination server, please see '''[[Layton ServiceDesk - Installation - Migration - Application Only (Direct Update to Latest Version)|this article]]'''. | ||
| + | |||
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. | ||
| − | ==Version== | + | =Procedure= |
| − | Check the '''[[Layton ServiceDesk - Procedures - General - How to Find the Version Number|application version]]''' on your live installation. Check | + | ==Check Version== |
| + | #Check the '''[[Layton ServiceDesk - Procedures - General - How to Find the Version Number|application version]]''' on your live installation (''Live''). | ||
| + | #Check '''[[LSD Current Version|here]]''' for the latest version. | ||
| + | #If you are not running the latest version on your source installation, please '''[mailto:[email protected] contact Support]''' for the version you are running. You will be provided with a link to a full version for use in the below procedures. Note that this may be earlier than Live, because not every update release had an accompanying Full version. In this case, you will be installing the next-lowest Full version, followed by the same version as Live. | ||
| − | + | ==Backup== | |
| + | #Back up the existing application installation directory by copying it to a location on the destination server. The default path is: ''C:\Program Files (x86)\Layton Technology\Layton ServiceDesk\'' | ||
| + | #In Layton ServiceDesk: | ||
| + | ##Go to '''[[Layton ServiceDesk - Settings - System Settings - Email Server Settings|Administration > System Settings > Email Server Settings]]'''. | ||
| + | ##Record the contents of all the fields. This is a precautionary step in case they need to be re-entered. | ||
| + | ##Disable both '''[[Layton ServiceDesk - Settings - System Settings - Email Server Settings#Auto Import Settings|Auto Import Email Server Settings]]''' so that the test installation doesn't hijack incoming mail. | ||
| + | #In Management Studio: | ||
| + | ##Back up your database. | ||
| + | ##Restore the backup of your database with a different name, for testing. | ||
| − | = | + | ==Preparation== |
| − | == | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
#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]]'''. | ||
| − | #Install as per '''[[Layton ServiceDesk - Installation - New Installation|New Installation]]''' | + | |
| − | #When the Database Tool opens, choose '''[[ | + | ==Installation== |
| − | # | + | #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 test database. |
| − | #*''HB_Data\ChangeAttach\'' | + | |
| − | #*''HB_Data\ | + | ==Update to Same Version as Live== |
| − | #*''HB_Data\MailIn\'' | + | #If the full version you installed was earlier than Live, immediately update to the same version as Live, using the Update installer provided by Support. |
| − | #*''HB_Data\ProblemAttach\'' | + | |
| − | #*''HB_Data\RequestAttach\'' | + | ==Restore Application Data== |
| − | #*''HB_Data\LogFiles\'' | + | #From the backup made in the '''[[#Preparation|Preparation]]''' steps, copy the files to the same location on the destination server. |
| + | #*''Application Images\'': Custom images 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\Editor_Folder\Image\'': User images added to email bodies configured in '''[[Layton ServiceDesk - Settings - Libraries - Email Settings & Bodies#Adding Images to Email Bodies|Email Settings & Bodies]]''' | ||
| + | #*''HB_Data\EmailBodies\'': Email notifications configured in '''[[Layton ServiceDesk - Settings - Libraries - Email Settings %26 Bodies|Email Settings & Bodies]]''' | ||
| + | #*''HB_Data\MailIn\'': File attachments from 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. | ||
| + | |||
| + | ==Testing== | ||
| + | #Test the installation by logging in, creating a request, sending an email, general use. If there is an issue, '''[mailto:[email protected] contact Support]''' for assistance. Do not continue until the issue is resolved. | ||
| + | |||
| + | ==Configuration== | ||
#Follow '''[[Layton ServiceDesk - General Troubleshooting - PDF Report Not Attached to Scheduled Report Email|this procedure]]''' to remap the application support path. | #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 | + | #Launch Database Tool (DBTool.exe), choose '''[[Layton ServiceDesk - Installation - Connect to Existing Database|Connect to an existing database]]''' and point it to your live database. |
| − | <p align="right">[[File: | + | |
| + | ==Decommission Old Application== | ||
| + | #On the old server, uninstall Layton ServiceDesk using Programs and Features. | ||
| + | #Open Internet Information Services (IIS) Manager. | ||
| + | ##In ''Application Pools'', delete ''LaytonServiceDeskAppPool''. | ||
| + | ##In ''Sites > Default Website'', delete the virtual directory ''LaytonServiceDesk''. | ||
| + | #Open the Windows Services console. | ||
| + | #Check to see if the ''LaytonServiceDesk'' service exists. If it does, open a command prompt and run this command to remove it:<br /><br /><p><code>sc delete LaytonServiceDesk</code><br /><br />If the service becomes ''marked for deletion'' but hasn't been removed, restart the server and check that the service has been removed.</p> | ||
| + | #Delete the folder ''Layton Technology'' in C:\Program Files\. | ||
| + | |||
| + | ==Update to Latest Version== | ||
| + | #If you are not running the latest version, update as soon as possible. Refer to the '''[[LSD Current Version|latest release notes for details]]'''. | ||
| + | <p align="right">[[File:btn back up.png|link=Layton ServiceDesk - Installation - Migration]] [[Layton ServiceDesk - Installation - Migration|<u>Back to ''Migration''</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> | ||
Revision as of 01:05, 9 January 2020
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. The process is to install the same version as Live on the destination server, then update. For a simplified procedure to directly install the latest version on the destination server, please see this article.
We highly recommend that you do not commit to the migrated installation until you are sure that the application is working without issues.
Procedure
Check Version
- Check the application version on your live installation (Live).
- 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 a full version for use in the below procedures. Note that this may be earlier than Live, because not every update release had an accompanying Full version. In this case, you will be installing the next-lowest Full version, followed by the same version as Live.
Backup
- Back up the existing application installation directory by copying it to a location on the destination server. The default path is: C:\Program Files (x86)\Layton Technology\Layton ServiceDesk\
- In Layton ServiceDesk:
- Go to Administration > System Settings > Email Server Settings.
- Record the contents of all the fields. This is a precautionary step in case they need to be re-entered.
- Disable both Auto Import Email Server Settings so that the test installation doesn't hijack incoming mail.
- In Management Studio:
- Back up your database.
- Restore the backup of your database with a different name, for testing.
Preparation
- Check your destination server against the System Requirements.
- Run your destination server through the Pre-Installation Procedure.
Installation
- Install as per New Installation.
- When the Database Tool opens, choose Connect to an existing database and point it to your test database.
Update to Same Version as Live
- If the full version you installed was earlier than Live, immediately update to the same version as Live, using the Update installer provided by Support.
Restore Application Data
- From the backup made in the Preparation steps, copy the files to the same location on the destination server.
- Application Images\: Custom images 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 from 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.
Testing
- Test the installation by logging in, creating a request, sending an email, general use. If there is an issue, contact Support for assistance. Do not continue until the issue is resolved.
Configuration
- Follow this procedure to remap the application support path.
- Launch Database Tool (DBTool.exe), choose Connect to an existing database and point it to your live database.
Decommission Old Application
- On the old server, uninstall Layton ServiceDesk using Programs and Features.
- Open Internet Information Services (IIS) Manager.
- In Application Pools, delete LaytonServiceDeskAppPool.
- In Sites > Default Website, delete the virtual directory LaytonServiceDesk.
- Open the Windows Services console.
- Check to see if the LaytonServiceDesk service exists. If it does, open a command prompt and run this command to remove it:
sc delete LaytonServiceDesk
If the service becomes marked for deletion but hasn't been removed, restart the server and check that the service has been removed. - Delete the folder Layton Technology in C:\Program Files\.
Update to Latest Version
- If you are not running the latest version, update as soon as possible. Refer to the latest release notes for details.
