Lynx Release 1.7.0

Prerequisites

Before installing Lynx 1.7.0 (version 1.7.0.6), please ensure that the target system(s) meet the following requirements.

• Windows Server 2012 R2, Windows Server 2016, or Windows Server 2019 (physical or virtual machine)

• The server on which Lynx 1.7.0 will be installed must be joined to the Active Directory domain that contains the users that will use the solution.

• Valid SSL certificate - The certificate can be issued by a public certificate authority (for example, Verisign or GoDaddy) or an internal authority (for example, Windows Certificate Services).

• Microsoft .Net 4.6.1 or greater

• License key (available from Identity Automation - please contact your account representative)

• (OPTIONAL) Microsoft SQL Server 2012, 2014, 2016, 2017, or 2019 (any edition). SQL Server can be installed on the same machine as the Lynx Server software, or on a different machine. Note: For enterprise deployments, Identity Automation recommends the use of a high-availability SQL Server environment. Therefore, for enterprise deployments, you should choose an edition of SQL Server that supports high availability.

• (OPTIONAL) Will you be using Lynx in conjunction with Identity Automation's ExactAccess (XA) product? If using Lynx with ExactAccess (XA), then Lynx must be installed on the same computer as XA Server. This is because Lynx will use the encryption components that XA Server provides to read and write encrypted data in the database. In addition, you must use a Microsoft SQL Server instance because it is required by the XA Server.

Compatibility with Previous QwickAccess ('QA') for ThinOS Releases

Improvement

Users can enable or disable their PIN reset functionality.

Key Fixes

• The user can not login to the Zulu application after the user is deleted from the Domain.
• Setting up disabled multiple proxcard registrations for a single user.
• The client certificate is required when we enable the Required client certificate field for WTOS 8.5 to 8.6 versions.

Known Issues

Upgrading from Lynx 1.5.3

If Lynx 1.5.2 (and below) or 1.5.3.1 or 1.5.3.2 is currently installed on the system, you won’t be able to perform an upgrade to Lynx 1.7.0 without first uninstalling Lynx 1.5.2.x (and below), 1.5.3.1 or 1.5.3.2 and removing files/and folders that are left behind after uninstall. Please follow the steps below to upgrade from Lynx 1.5.2.x or 1.5.3.x

1. Uninstall Lynx 1.5.2.x or 1.5.3.x by using Windows Add/Remove Programs (or similar method).
2. Next, locate the RemoveServiceAndFolder.ps1 file in the package that contains the Lynx 1.7.0 deliverables.
3. Run the RemoveServiceAndFolder.ps1 file as an administrator.
4. Now run the Lynx-1.7.0.6-Setup.exe file to install Lynx 1.7.0.

Settings Not Preserved on Upgrade

After upgrading from the 1.5.0 version of Lynx you will need to re-enter the settings that you had previously setup on the old version. This is because the upgrade to Lynx 1.7.0 will not preserve the previous settings. To reapply your previous settings after an upgrade, open the Lynx Admin web app and click the “Settings” tab on the left. Then go through each of the settings tabs and values to ensure they meet your requirements. Make changes as needed.

Database Update Instructions

Lynx 1.7.0 can be configured to use an embedded database or a Microsoft SQL Server database. If you are using the embedded database, then no further action is required. If you are using a Microsoft SQL Server database, then you must upgrade the database to support Lynx 1.7.0 if you upgrade Lynx from 1.5.0. Follow these instructions to upgrade your SQL Server database.

1. After the installation or upgrade to Lynx 1.7.0, open the Windows Services add (services.msc) and find the HealthCast Lynx service in the list.
2. Stop the HealthCast Lynx service.
3. Double-click the HealthCast Lynx service to open its property pages.
4. Click the Log On tab.
5. Select the This account radio button and enter the credentials for an account that has read and write privileges to the Lynx database on SQL Server.
6. Click OK.
7. Next, start SQL Server Management Studio (SSMS)
8. In SSMS, open the C:\Program Files (x86)\HealthCast\Lynx\CreateDb.sql file.
9. In the CreateDb.sql file (now opened in SSMS) change the top line from use [YOUR-DATABASE-NAME-HERE] to contain the correct Lynx database name. Typically, this would look like this: use [Lynx] although your database name may be different.
10. Run the CreateDb.sql file within SSMS.
11. You will notice several errors that all say that certain objects (tables) are already created. You can safely ignore these errors.
12. Now start the HealthCast Lynx service which was stopped in Step 2 of these instructions.
13. The database update is now complete.

FAQ

Question 1: Where to set the PIN reset field?
Answer 1: Enable the PIN reset setting from the Lynx server. Open any ThinOS version settings under Settings->EndPoint->Dell ThinOS->[Select Dell ThinOS version]. Create or edit your profile and click on the PIN reset section under profile settings. Select the Yes option to enable the PIN reset functionality.

Question 2: How do we reset our PIN?
Answer 2: Enable the PIN reset setting from the Lynx server. You will get a PIN reset link on the PIN authentication window. Click on the link and enter your password. You will get the PIN reset window where you can reset your PIN.

Question 3: Is PIN reset functionality compatible with the 1.6.0 version of the Lynx server?
Answer 3: Is PIN reset functionality compatible with the 1.6.0 version of the Lynx server?

Answer 3: No, PIN reset functionality compatible with the 1.7.0 version of Lynx.: No, PIN reset functionality compatible with the 1.7.0 version of Lynx.

Supported Zulu Versions:

• Zulu 2.0.3 and above.