Layton ServiceDesk - Release Notes - Version 6.8.4
Layton ServiceDesk 6.8.4 is a update patch release of the product. Both update and full installers are available.
Determining the Currently Installed Version
Please refer to this article to determine the currently installed version.
Earliest Version that Can Be Updated to 6.8.4
You must be using ServiceDesk 6.2.0 or later before you can update to the latest version. If you are using an earlier version please update by downloading v6.2.0 from the Update ➤ Layton ServiceDesk menu in the Client Support Portal before attempting to update to the latest version.
.NET 4 Requirement
22.214.171.124 introduced the need for .NET 4. If you are currently running a version prior to 126.96.36.199, it will need to be installed. Instructions are given below.
We recommend that you create a Test Installation and update it before committing to updating your live system.
Obtaining the Update
Please log in to the Client Support Portal to download the update installer.
Obtaining the Full Installer
The full installer is the currently available trial version, which can be downloaded from here. Please log in to the Client Support Portal to obtain your license details to register the application after installation.
IIS Manager Modifications
- Install Microsoft Visual C++ 2005 SP1 Redistributable Package (x64).
- In IIS Manager, change IIS > DefaultAppPool > Enable 32-Bit Applications to True.
Updating from a Version Earlier than 188.8.131.52
Install Microsoft .NET Framework 4.5
- If you are updating from a version earlier than 184.108.40.206, install Microsoft .NET Framework 4.5.
- Launch Internet Information Services (IIS) Manager.
- In the Connections pane on the left-hand side, click the server name.
- In the Actions pane on the right-hand side, click Change .NET Framework Version.
- Change the .NET Framework Version to v4.0.30319 and click the OK button.
- In the center panel, double-click ISAPI and CGI Restrictions.
- There are two items with the description ASP.NET v4.0.30319. Right-click each and select Allow.
- Close Internet Information Services (IIS) Manager.
- Continue in the next section, Updating from a Version Later than 220.127.116.11.
Updating from a Version Later than 18.104.22.168
Do not uninstall Layton ServiceDesk prior to updating.
- Extract the lsd_update_683 folder from the archive to the root of an attached, local drive.
- Back up your database.
- If your server is virtual, snapshot the server.
- In Windows Services Console, stop the following services:
- IIS Admin Service
- World Wide Web Publishing Service.
- 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.
- Open the lsd_update_683 folder.
- Right-click the installer lsd683_upgrade.exe and select Run as administrator. This will avoid permission issues. Note that the progress dialog may report that it is not responding, but this process may simply take some time.
- In Windows Services Console, start the above services.
- Re-enable anti-virus software, if applicable.
If you are installing for the first time, refer to System Requirements and follow the links at the right bottom of each related article.
If you are doing a Clean Reinstallation, follow the Clean Reinstallation procedure.
It is possible to update just the database using a SQL Server script.
- Download the 6.8.4 Update Script.
- In Management Studio, back up your database.
- Run the script on the database.
|67866||LDAP: OU Checked, But New Users Not Checked||When checking an OU in the LDAP Import End User Filter, the expectation is that the accounts within that OU will always apply. If new accounts were added to the OU in Active Directory, Layton ServiceDesk was not importing them, because it erroneously was expecting the administrator to manually check the new accounts in the filter. Now, when an OU is checked, the contents of that OU are always included.|
|67962||Broken Page When TLS 1.0 and 1.1 are Disabled||With TLS 1.0 and 1.1 disabled, invoking auto login via NTLM would cause a 401 error. Opening a Request would cause a broken web page, with a generic error. Although the 401 error is a known issue, the disabling of TLS was a new factor. This has been resolved.|
|68054||Display Bug on Request Form: Gray Bar||A new gray bar was erroneously introduced to the Analyst Request form. This was not present in earlier versions. Form elements like the Save and Close buttons appear over the bar. This bar was removed.|
|68100||Broken Page on Updating Customised Request Form||With a large number of user-defined fields added to the Analyst Request form, adding information and saving the form generated a broken web page with a System.Web.HttpException: Failed to load viewstate error. This has been resolved.|
|68228||DBTool Not Installing Updated Database||When attempting to access Administration pages, a Cannot find table 0 error was seen. It was discovered that when creating a new database using the Layton ServiceDesk Database Tool (DBTool.exe), the latest SQL Server update script was not included, so some columns referenced by the code were not present, and caused the issue. The latest code and SQL Server script used by DBTool.exe has been updated.|
|68229||Redundant Config File Created on Installation||When the application was installed using the full installer, a copy of config.xml, called Copy of config.xml, appeared in the Program Files folder. This was unnecessary and confusing and the full installer no longer does this. The update installer removes the redundant copy.|
|68238||Missing File: LibChgType.aspx||If installed using the 6.8.3 full installer, a broken page resulted from going to Administration > Libraries > Change Types:
The resource cannot be found. Requested URL: /LaytonServiceDesk/LibChgType.aspx
The LibChgType.aspx file was missing from the full installer. This has been corrected, and now installs this file.
|68245||New 6.8.3 Database Has Old Priority Form Design||Creating a new 6.8.3 database using DBTool included the old Priority form design. The installation script was writing the wrong version to the database. The update script didn't check for the old design and update it. The Priority settings page was updated in 6.6.6. This is what it is supposed to look like. The database-creation process now creates the correct form design.|
|68265||Can't Save Analyst Assignment in Priority||When the Priority field Escalation Level > 1 Escalate to is populated with an Analyst, on save, the Analyst is not saved. This has been resolved.|
|68344||Tab Display Issue When Comment Contains Malformed HTML||With specific HTML formatting in the Problem Desc field, that field would appear blank and the tabs on the top of the Problem Desc field would disappear. This has been resolved.|
|68350||Intermittent: Can't Assign End Users||On some occasions, when populating the End User field and clicking the Save button, a gray overlay would appear on the Request form and an animation of three dots would appear, and the interface would freeze. This has been resolved.|
|68365||Remove LSDLICENSE - Copy.rtf from Update Folder||When the application was installed using the update installer, a copy of LSDLICENSE.rtf, called LSDLICENSE - Copy.rtf, appeared in the update folder. This was unnecessary and confusing and the update folder no longer contains this. The update installer removes the redundant copy.|