Layton ServiceDesk - Installation - Migration - Application Only

From Layton Support
(Difference between revisions)
Jump to: navigation, search
(Major revision)
m (Added step relating to update testing.)
 
(5 intermediate revisions by one user not shown)
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.
+
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.
Line 11: Line 11:
 
#Check the '''[[Layton ServiceDesk - Procedures - General - How to Find the Version Number|application version]]''' on your live installation (''Live'').
 
#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.
 
#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 upgrade 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.
+
#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==
 
==Backup==
Line 31: Line 31:
 
#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.
 
#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.
  
==Upgrade to Same Version as Live==
+
==Update to Same Version as Live==
#If the full version you installed was earlier than Live, immediately upgrade to the same version as Live, using the Upgrade installer provided by Support.
+
#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==
 
==Restore Application Data==
Line 47: Line 47:
 
==Testing==
 
==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.
 
#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.
 +
#If part of the testing is to update the application, do so now, following '''[[LSD Latest Full Version|the latest release notes]]'''.
  
 
==Configuration==
 
==Configuration==
Line 61: Line 62:
 
#Delete the folder ''Layton Technology'' in C:\Program Files\.
 
#Delete the folder ''Layton Technology'' in C:\Program Files\.
  
==Upgrade to Latest Version==
+
==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]]'''.
 
#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=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>
 
<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>

Latest revision as of 04:47, 24 May 2023

Btn back up.png Back to Contents

Btn back up.png Back to Migration

Contents

[edit] 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.

[edit] Procedure

[edit] Check Version

  1. Check the application version on your live installation (Live).
  2. Check here for the latest version.
  3. 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.

[edit] Backup

  1. 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\
  2. In Layton ServiceDesk:
    1. Go to Administration > System Settings > Email Server Settings.
    2. Record the contents of all the fields. This is a precautionary step in case they need to be re-entered.
    3. Disable both Auto Import Email Server Settings so that the test installation doesn't hijack incoming mail.
  3. In Management Studio:
    1. Back up your database.
    2. Restore the backup of your database with a different name, for testing.

[edit] Preparation

  1. Check your destination server against the System Requirements.
  2. Run your destination server through the Pre-Installation Procedure.

[edit] Installation

  1. Install as per New Installation.
  2. When the Database Tool opens, choose Connect to an existing database and point it to your test database.

[edit] Update to Same Version as Live

  1. 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.

[edit] Restore Application Data

  1. 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.

[edit] Testing

  1. 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.
  2. If part of the testing is to update the application, do so now, following the latest release notes.

[edit] Configuration

  1. Follow this procedure to remap the application support path.
  2. Launch Database Tool (DBTool.exe), choose Connect to an existing database and point it to your live database.

[edit] Decommission Old Application

  1. On the old server, uninstall Layton ServiceDesk using Programs and Features.
  2. Open Internet Information Services (IIS) Manager.
    1. In Application Pools, delete LaytonServiceDeskAppPool.
    2. In Sites > Default Website, delete the virtual directory LaytonServiceDesk.
  3. Open the Windows Services console.
  4. 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.

  5. Delete the folder Layton Technology in C:\Program Files\.

[edit] Update to Latest Version

  1. If you are not running the latest version, update as soon as possible. Refer to the latest release notes for details.

Btn back up.png Back to Migration

Btn back up.png Back to Contents

Personal tools
Namespaces

Variants
Actions
Main Page
Online User Guides
General Support
Release Notes
Toolbox