Release Summary
Lynx 1.7.5 introduces easier password management for administrators, improves performance when working with large ProxCard enrollments, corrects domain validation behavior, restores sorting in the Prox Cards view, and includes security and platform updates to improve reliability and supportability.
Prerequisites
Before installing Lynx 1.7.5, please ensure that the target system meets the following requirements:
Windows Server 2019 or Windows Server 2022 (physical or virtual machine).
The server on which Lynx 1.7.5 will be installed must be joined to the Active Directory domain that contains the users who will use the solution.
A valid SSL certificate. The certificate can be issued by a public certificate authority or an internal authority such as Windows Certificate Services.
Microsoft .NET Framework 4.8 or greater is installed.
A valid license key is available from Identity Automation.
(Optional) Microsoft SQL Server 2019 (any edition). SQL Server can be installed on the same machine as the Lynx Server software or on a different machine.
(Optional) If Lynx will be used with Identity Automation's ExactAccess (XA) product, Lynx must be installed on the same computer as XA Server. In this configuration, a Microsoft SQL Server instance must be used.
For enterprise deployments, Identity Automation recommends using a high-availability SQL Server environment. Choose a SQL Server edition that supports high availability if that capability is required in your environment.
Compatibility with Previous QwickAccess for ThinOS Releases
Product | QwickAccess Package Name | QwickAccess Version | Compatible with Lynx 1.7.5 |
|---|---|---|---|
QwickAccess for ThinOS 8.5 and 8.6 | QwickAccess came embedded in ThinOS 8.5 and 8.6 so there is no separate package | N/A (this version came embedded in ThinOS 8.5 and 8.6) | Yes |
QwickAccess for ThinOS 9.0 | QwickAccess came embedded in ThinOS 9.0 so there is no separate package | This version came embedded in ThinOS 9.0. | No |
QwickAccess for ThinOS 9.1 MR1 | idauto_1.0.1_1_signed.pkg-V1.0.1.1 | Version 1.0.1.1 | No |
QwickAccess for ThinOS 9.1.1 (9.1.4234) | Identity_Automation_QwickAccess_2.0.0.3_3.pkg | Version 2.0.0.3 | No |
QwickAccess for ThinOS 2208(9.3.2102) | Identity_Automation_QwickAccess_2.0.1.0_3.pkg | Version 2.0.2.1 | No |
QwickAccess for ThinOS 2211 (9.3.3099) | Identity_Automation_QwickAccess_2.0.3.1.1.pkg | Version 2.0.3.1 | No |
QwickAccess for ThinOS 2303 (9.4.1141) | Identity_Automation_QwickAccess_2.0.4.1.6.pkg | Version 2.0.4.1.6 | Yes |
QwickAccess for ThinOS ThinOS 2402 (9.5.1079) | Identity_Automation_QwickAccess_2.1.0.7.pkg | Version 2.1.0 | Yes |
QwickAccess for ThinOS ThinOS 2411 | Identity_Automation_QwickAccess_2.1.1.x.pkg | Version 2.1.1 | Yes |
New Features and Enhancements
Ticket Number | Description |
|---|---|
HEALTH-1830 | Administrators can now reset a user’s ProxCard password directly from the Lynx admin web interface. This removes the need for manual database work and makes it faster and easier for support teams to help users regain access. |
HEALTH-1645 | Lynx now runs on Microsoft .NET Framework 4.8, improving long-term support, security, and compatibility with current Windows environments and supporting components. |
Bugs Fixed
Ticket Number | Description |
|---|---|
HEALTH-1440 | Security-related issues identified in the Lynx application have been resolved to improve the overall protection and stability of the product. |
HEALTH-1789 | Improved the ProxCard management experience in large environments. Customers with a high number of enrolled cards should no longer experience long browser freezes when opening or searching the ProxCard page. |
HEALTH-1818 | Resolved an issue where some valid Active Directory domains could appear unreachable in Lynx settings, even though they were available and working correctly. Domain validation now behaves more accurately for affected environments. |
HEALTH-1842 | Fixed an issue in the Prox Cards section where sorting by columns such as card count or username did not work as expected. Administrators can now sort enrolled users normally. |
Database Update Instructions
Lynx 1.7.5 can be configured to use an embedded database or a Microsoft SQL Server database. If you are using the embedded database, no further action is required. If you are using a Microsoft SQL Server database and upgrading from Lynx 1.5.0, you must upgrade the database to support Lynx 1.7.5.
After installing or upgrading to Lynx 1.7.5, open the Windows Services application and find the
HealthCast Lynxservice.Stop the
HealthCast Lynxservice.Open the service properties.
Select the Log On tab.
Select This account and enter credentials for an account that has read and write privileges to the Lynx database on SQL Server.
Click OK.
Open SQL Server Management Studio.
Open the file
C:\Program Files (x86)\HealthCast\Lynx\CreateDb.sql.In the file, change the top line from use [YOUR-DATABASE-NAME-HERE] to the correct Lynx database name, such as
use [Lynx].Run the
CreateDb.sqlfile.You may see errors indicating certain objects already exist. These can be safely ignored.
If you are upgrading from Lynx 1.7.2 or an older version, also run
UpgradeDb.sqlafter replacing[YOUR-DATABASE-NAME-HERE]with the correct database name.Start the
HealthCast Lynxservice again.The database update is now complete.
Important
Lynx 1.7.5 requires Microsoft .NET Framework 4.8. Ensure .NET Framework 4.8 is installed before upgrading. Windows Server 2019 and Windows Server 2022 include this version by default.
Upgrading from Lynx 1.7.x
Lynx 1.7.5 can be upgraded directly from Lynx 1.7.0 through 1.7.4. Existing data is preserved, and no additional upgrade steps are required beyond the standard process.
Steps to upgrade Lynx from 1.7.x
Run the latest Lynx 1.7.5 setup file.
If prompted for a reboot, click OK to continue.
After installation completes, restart the
HealthCast Lynxservice from Windows Services.Open the Lynx portal in a web browser and confirm the installed version is shown as the current release on the login screen.
You can also verify the installed version from
Control Panel > Programs and Features.
Upgrading from Lynx 1.6.x
Lynx 1.7.5 can be upgraded directly from Lynx 1.6.x versions without special database upgrade steps beyond the standard process above. Existing data is preserved in the current database.
Steps to upgrade Lynx from 1.6.x
Run the latest Lynx 1.7.5 setup file.
If prompted for a reboot, click OK to continue.
.png)
After installation completes, restart the
HealthCast Lynxservice from Windows Services..png)
Open the Lynx portal in a web browser and confirm the installed version is shown as the current release on the login screen.
You can also verify the installed version from
Control Panel > Programs and Features.
Known Issues
HEALTH-1638
Users from unassigned or deleted domains may still be able to reset their passwords in Zulu even after the domain has been removed from the Lynx server.
Upgrading from Lynx 1.5.3
If Lynx 1.5.2 and below, or versions 1.5.3.1 or 1.5.3.2, are currently installed, you cannot upgrade directly to Lynx 1.7.5 without first uninstalling the older version and removing leftover files and folders.
Uninstall Lynx 1.5.2 or 1.5.3 using Windows Add or Remove Programs.
Locate the file
RemoveServiceAndFolder.ps1in the Lynx 1.7.5 deliverables package.Run
RemoveServiceAndFolder.ps1as an administrator.Run the Lynx 1.7.5 setup file to complete installation.
Settings Not Preserved on Upgrade
When upgrading from Lynx 1.5.0, previous settings are not preserved. After the upgrade, open the Lynx Admin web application, review each setting, and re-enter values as needed.
Global End Point Settings
The following setting is currently not working under Global End Point Settings:
Password History Count
Supported Zulu Versions
Zulu 2.1.2 and above.
