Layton ServiceDesk - Release Notes - Version 6.8.4
m (Added bug numbers) |
(Added bug descriptions) |
||
Line 80: | Line 80: | ||
|67866 | |67866 | ||
|LDAP: OU Checked, But New Users Not Checked | |LDAP: OU Checked, But New Users Not Checked | ||
− | | | + | |When checking an OU in the '''[[Layton ServiceDesk - Utilities - LDAP Import End User#Filter|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. |
|-style="vertical-align:top;" | |-style="vertical-align:top;" | ||
|67962 | |67962 | ||
|Broken Page When TLS 1.0 and 1.1 are Disabled | |Broken Page When TLS 1.0 and 1.1 are Disabled | ||
− | | | + | |With TLS 1.0 and 1.1 disabled, invoking '''[[Layton ServiceDesk - FAQ - NTLM (Auto) Login#End User NTLM Configuration|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 '''[[Layton ServiceDesk - FAQ - NTLM (Auto) Login#Install Windows Authentication Server Role|known issue]]''', the disabling of TLS was a new factor. This has been resolved. |
|-style="vertical-align:top;" | |-style="vertical-align:top;" | ||
|68054 | |68054 | ||
− | |Display Bug on Request Form: | + | |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. |
|-style="vertical-align:top;" | |-style="vertical-align:top;" | ||
|68100 | |68100 |
Revision as of 01:48, 23 July 2020
Contents |
Overview
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
6.7.0.2 introduced the need for .NET 4. If you are currently running a version prior to 6.7.0.2, it will need to be installed. Instructions are given below.
Test Installation
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.
Prerequisite
IIS Manager Modifications
- Install Microsoft Visual C++ 2005 SP1 Redistributable Package (x64).
- Restart.
- In IIS Manager, change IIS > DefaultAppPool > Enable 32-Bit Applications to True.
Updating from a Version Earlier than 6.7.0.2
Install Microsoft .NET Framework 4.5
- If you are updating from a version earlier than 6.7.0.2, 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 6.7.0.2.
Updating from a Version Later than 6.7.0.2
Layton ServiceDesk
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
- LaytonServiceDesk
- 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.
Full Installation
New Installation
If you are installing for the first time, refer to System Requirements and follow the links at the right bottom of each related article.
Clean Reinstallation
If you are doing a Clean Reinstallation, follow the Clean Reinstallation procedure.
Database Update
It is possible to update just the database using a SQL Server script.
Procedure
- Download the 6.8.4 Update Script.
- In Management Studio, back up your database.
- Run the script on the database.
Bug Fixes
# | Title | Description |
---|---|---|
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 | |
68228 | DBTool Not Installing Updated Database | |
68229 | Redundant Config File Created on Installation | |
68238 | Missing File: LibChgType.aspx | |
68245 | New 6.8.3 Database Has Old Priority Form Design | |
68265 | Can't Save Analyst Assignment in Priority | |
68344 | Tab Display Issue When Comment Contains Malformed HTML | |
68350 | Intermittent: Can't Assign End Users | |
68365 | Remove LSDLICENSE - Copy.rtf from Update Folder |
Released 2020-