Solution Requirements
Lynx has the following requirements:
Windows Server 2012 R2 or Windows Server 2016 (physical or virtual server)
Must be joined to the Active Directory domain that contains the users that will use the solution.
SSL certificate - The certificate can be issued by a public or internal authority (if issued by an internal authority, make sure the certificate has a valid Subject Alternative Name field). Note: If using Lynx and QwickACCESS for Chrome Devices please see Additional Certificate Requirements below.
Microsoft .Net 4.6.1 or greater
License key (available from HealthCast - please contact your account representative)
(OPTIONAL) Microsoft SQL Server 2008 R2, 2012, 2014, 2016, or 2017 (any edition) – can be installed on the same machine as the Lynx Server software, or on a different machine.
For enterprise deployments HealthCast 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 HealthCast's ExactAccess (XA) product?
If using Lynx with HealthCast's ExactAccess (XA), then Lynx must be installed on the same computer as HealthCast 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.
Additional Certificate Requirements
If using QwickACCESS for Chrome Devices on Single-App Kiosk or Public Session end-points, then the certificate must be issued by a public certificate authority such as GoDaddy or Comodo. For User mode end-points, the certificate can be issued by a public or internal authority (if issued by an internal authority, make sure the certificate has a valid Subject Alternative Name field).