Installation Checklist
- 20 Mar 2023
- 1 Minute to read
- Contributors
- DarkLight
- PDF
Installation Checklist
- Updated on 20 Mar 2023
- 1 Minute to read
- Contributors
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Lynx Server 1.6 Installation Checklist
Ensure that your environment meets the Lynx solution requirements.
- Operating System(s)
* Windows Server 2012 R2, Windows Server 2016, or Windows Server 2019 (physical or virtual machine) - The server on which Lynx 1.6.0 will be installed must be joined to the Active Directory domain that contains the users that will use the solution.
- SQL Database User Credentials
- If you will be configuring Lynx to use a Microsoft SQL Server instance, you must have the username and password of a domain user that can read and write to the database.
- IMPORTANT! You must set the password of this user to never expire, and you must not restrict the logon hours of this user.
- Valid SSL certificate
- The certificate can be issued by a public certificate authority (for example, Verisign or GoDaddy) or internal authority (for example, Windows Certificate Services).
- The certificate must have the Fully Qualified Domain Name as the subject field.
- On the machine on which you will install Lynx, ensure that you have an SSL certificate installed in the Local Computer, Personal folder certificate store.
- Microsoft .Net 4.6.1 or greater
- Lynx License key
- Available from Identity Automation - please contact your account representative
- If using Lynx with ExactAccess (XA)
- 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.
- 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.
- 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.
Was this article helpful?