Layton ServiceDesk - Installation - Test Installation

From Layton Support
Jump to: navigation, search

Btn back up.png Back to Contents

Contents

Overview

This procedure is to test the application with your existing database without affecting the live system. You will be installing the application on a different server to your live installation. You can use a new database, or, if you are testing changes to your live system, you can test on a copy of your live database.

Licensing

You may make copies of the software solely for testing, security, backup and archival purposes, provided that such a copy contains all of the original software copyright information and other proprietary notices. You may use your licence key as it appears on the License Information page in Administration > System Settings > License Information to activate your test installation.

Test Server OS

Note that while it is not recommended to install a production Layton ServiceDesk installation on a consumer Windows OS like Windows 10, a test installation would not experience the same processor load, and does not need to be installed on a Windows Server OS. In this instance, it can be installed on a consumer Windows OS. This also aids in cost-saving, as a Windows Server OS would not need to be purchased for testing purposes. We would recommend Windows 10 or later.

Procedure

Follow the steps for the type of server that is hosting your live installation.

Virtual Server

Virtual Server with SQL Database Hosted on the Layton ServiceDesk Server

1. If you will be testing email, create a new email account on your mail server for testing.

2. Back up your SQL database.

3. Take a snapshot of the server.

4. Create a duplicate of the server. Change the server name.

5. Launch the virtual server.

6. To prevent this test installation from hijacking your live system's mail, we will delete the email server name in both Incoming and Outgoing sections. Just the server name will suffice, accounting for all the potential methods that can be used. Run this query in Management Studio:

   UPDATE	setting
   
   SET		sys_setting_value = NULL
   
   WHERE	sys_setting_name IN
   
   		('inemailpopserver'
                ,'inemailimapserver'
                ,'outemailsmtpserver'
                ,'inemailcdodropfolder'
                ,'inemailwebdavexchangeurl'
                ,'emailexchangeserver'
                ,'inemailexchangeserver')

7. Launch Layton ServiceDesk.

8. If you will be testing email, on first login, change the Email Server Settings to your test email account.

9. If you are testing an upgrade to the latest version, download it from the Customer Portal and install it per the instructions in the latest Release Notes.

Virtual Server with SQL Database Hosted on a Different Server

1. If you will be testing email, create a new email account on your mail server for testing.

2. Back up your SQL database.

3. Restore the backup with a different name, on the same SQL server or a different one.

4. To prevent this test installation from hijacking your live system's mail, we will delete the email server name in both Incoming and Outgoing sections. Just the server name will suffice, accounting for all the potential methods that can be used. Run this query in Management Studio:

   UPDATE	setting
   
   SET		sys_setting_value = NULL
   
   WHERE	sys_setting_name IN
   
   		('inemailpopserver'
                ,'inemailimapserver'
                ,'outemailsmtpserver'
                ,'inemailcdodropfolder'
                ,'inemailwebdavexchangeurl'
                ,'emailexchangeserver'
                ,'inemailexchangeserver')

5. Take a snapshot of the server.

6. Create a duplicate of the server. Change the server name.

7. Launch the virtual server.

8. Connect to the test database.

9. Launch Layton ServiceDesk.

10. If you will be testing email, on first login, change the Email Server Settings to your test email account.

11. If you are testing an upgrade to the latest version, download it from the Customer Portal and install it per the instructions in the latest Release Notes.

Standalone Server

1. If you will be testing email, create a new email account on your mail server for testing.

2. Back up your SQL database.

3. Restore the backup with a different name, on the same SQL server or a different one.

4. To prevent this test installation from hijacking your live system's mail, we will delete the email server name in both Incoming and Outgoing sections. Just the server name will suffice, accounting for all the potential methods that can be used. Run this query in Management Studio:

   UPDATE	setting
   
   SET		sys_setting_value = NULL
   
   WHERE	sys_setting_name IN
   
   		('inemailpopserver'
                ,'inemailimapserver'
                ,'outemailsmtpserver'
                ,'inemailcdodropfolder'
                ,'inemailwebdavexchangeurl'
                ,'emailexchangeserver'
                ,'inemailexchangeserver')

5. Determine the application version installed on your live system.

6. Contact Support to obtain a full installer and any required updates for the version installed on your live system.

7. Install as per New Installation. When the Database Tool opens, connect to the database copy, not the live one.

8. If the version of the full installer is lower than your live installation, then immediately update to the higher version before you launch the application.

9. If you will be testing email, on first login, change the Email Server Settings to your test email account.

10. If you are testing an upgrade to the latest version, download it from the Customer Portal and install it per the instructions in the latest Release Notes.

Btn back up.png Back to Contents

Personal tools
Namespaces

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