Layton ServiceDesk - Release Notes - Version 6.7.0.1

Back to List

Earlier Version Later Version

Latest Version

Overview

This version is deprecated. Do not install. Instead, install 6.7.0.2, which resolves an issue with the Rebex IMAP component and includes the 6.7.0.1 enhancements and bug fixes.

ServiceDesk v6.7.0.1 is a minor release of the product. You must be using ServiceDesk v6.2.0 or later before you can upgrade to the latest version. If you are using an earlier version please upgrade by downloading v6.2.0 from the Update ➤ Layton ServiceDesk menu in the Client Support Portal before attempting to upgrade to the latest version.

Update

Determining the Currently Installed Version

Please refer to this article to determine the currently installed version.

Obtaining the Update

Please log in to the Client Support Portal to download the upgrade installer.

Test Installation

We recommend that you create a Test Installation and upgrade it before committing to updating your live system.

Procedure

Do not uninstall Layton ServiceDesk prior to upgrading. This is an update, not a full installer.

1. Extract the lsd6701_upgrade folder from the archive to the root of an attached, local drive.
2. Back up your database
3. In Windows Services Console:
   1. Stop the IIS Admin service
   2. Stop the LaytonServiceDesk service
4. Open the lsd6701_upgrade folder.
5. Disable anti-virus software on the server, if running. This has been known to prevent the copying of files, especially .exe files, to the Program Files folder.
6. Right-click the installer lsd6701_upgrade.exe and select Run as administrator. This will avoid permission issues.
7. In Windows Services Console, start the IIS Admin and LaytonServiceDesk services.
8. Enable anti-virus software, if applicable.

Enhancements

#	Title	Description
66982	Upgrade TLS Support	Added support for TLS 1.1 and 1.2.
66982	Additional Log Entries for Incoming Email Testing	Initiation of an incoming email test will add additional entries to the log to document the process.

Bug Fixes

#	Title	Description
67274	Request has Comment assigned from Analyst (Notify End User) Notification Not Sent	Resolved a bug that prevented the Request has Comment assigned from Analyst (Notify End User) notification from being sent if Default Comment Status was set to Private and the Analyst changed the Public/Private setting on the Edit Comment page to Public at the time of creating the Comment. Conversely, if Default Comment Status was set to Public, the notification was being sent. This behavior is preserved.

Released 2017-09-12