Layton ServiceDesk - Installation - Migration - Application Only

From Layton Support
(Difference between revisions)
Jump to: navigation, search
(Major revision)
m (Minor addition)
Line 58: Line 58:
 
#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.
 
#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.
 
#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.
 +
#Decommission the old server so that users don't accidentally use it.
  
 
==Update==
 
==Update==

Revision as of 04:25, 22 June 2017

Btn back up.png Back to Contents

Btn back up.png Back to Migration

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.

Procedure

Check Version

  1. Check the application version on your live installation.
  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 the latest full version for use in the below procedures.

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 Management Studio:
    1. Back up your database.
    2. Restore the backup of your database with a different name, for testing.
    3. Select the test database in the database-selection menu in the upper-left of the main window and run this query to prevent the test installation from hijacking incoming email:
   UPDATE	setting
   
   SET		sys_setting_value = NULL
   
   WHERE	sys_setting_name IN
   
   		('inemailpopserver'
                ,'inemailimapserver'
                ,'inemailcdodropfolder'
                ,'inemailwebdavexchangeurl'
                ,'emailexchangeserver'
                ,'inemailexchangeserver')

Preparation

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

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.

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.

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.

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.
  3. Decommission the old server so that users don't accidentally use it.

Update

  1. If you are not running the latest version, update immediately. 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