Connecting remotely to Local Run Manager v4 on instrument
Local Run Manager uses HTTPS to encrypt data connections to make sure that run data information is private and secure. Security certificate settings should only be changed in the following situations:
• Access Local Run Manager from a new remote device • Use your own custom security certificate • Regain access to Local Run Manager after changing the system name or moving the system to a new domain
Install a Security Certificate For Remote Access
On the remote device, login to Local Run Manager.
From the dashboard navigation bar, select the Tools drop-down list, and then select System Settings.
Select the Certificates tab.
Select Download to download a zip file that contains the Local Run Manager certificate.
Extract the contents of the zip file.
Right-click the BAT file and select Run as administrator.
Follow the prompts to finish the installation, and then restart your browser. Upload a Custom Security Certificate
To replace the existing Local Run Manager certificate, do the following
From the dashboard navigation bar, select the Tools drop-down list, and then select System Settings.
Select the Certificates tab.
Select Browse, select the new certificate file (\*.pfx), and then select Open.
Enter the password for the certificate file, and then select Set Certificate.
Restart your browser. Regenerate a Security Certificate
If there was recent change to the system name or the system was moved to a new domain, you must regenerate the security certificate to regain access to Local Run Manager.
Launch Local Run Manager via HTTPS.
From the dashboard navigation bar, select the Tools drop-down list, and then select System Settings.
Select the Certificates tab.
Select Regenerate the Certificate.
Restart your browser.
If you need to connect to Local Run Manager from another device, download and install the regenerated certificate on the remote device.
• Select Regenerate the Certificate. • Select Download to download a zip file that contains the Local Run Manager software certificate. • Extract the contents of the zip file. • Right-click the BAT file and select Run as administrator. • Follow the prompts to finish the installation, and then restart your browser.
When connecting remotely to the Local Run Manager (LRM) instance running on an instrument, users must use the computer name given to the instrument on their network, rather than the IP address in order to connect securely over https. For example, https:// should be used rather than https://
If customers install the security certificates and must connect via IP address, they may be able to connect via https and choose to proceed anyway. In some instances, they will not be able to proceed once the certificate is installed because it is gets flagged as invalid. In this case, the following steps should allow them to connect:
Go to the Start menu and type inetcpl.cpl
Right click the results and select Run as administrator
Go to the Content tab and select Certificates
Remove the certificate called "LRMRootCA" from the Intermediate Certification Authorities and Trusted Root Certification Authorities tabs (if present).
Close the Certificates window and click OK on the Internet Properties window
Navigate to https://nextseq-ip-address and click the Advanced button.
Click the "Proceed to https://nextseq-ip-address (unsafe)" link to continue to the LRM interface
This should allow the customer to connect over https://. The connection however will not be secured.
Tags: Local Run Manager, LRM, NextSeq, MiSeq, connect, remote, IP address
Resource https://support-docs.illumina.com/SW/lrm_v4/Content/SW/LRM/LRM_v3/SystemCertificates_swLRM.htm
For any feedback or questions regarding this article (Illumina Knowledge Article #2323), contact Illumina Technical Support techsupport@illumina.com. |
Last updated