How to connect benchtop instruments and Local Run Manager to a network location
Introduction
Instrument control software contains several different Illumina Windows Services
Illumina Universal Copy Service
Illumina Local Run Manager Job Service
Illumina Local Run Manager Analysis Service
By default, the Illumina Windows Services are configured to Log On As a predefined Windows service account called Local System. Successful data transfer from the instrument to a network output location requires that the Illumina Windows Services be reconfigured to Log On As a different local Windows account.
Services are usually reconfigured to Log On As the standard local sbsuser account, which exists on all instruments. You may also choose to run the services using a different account (on-domain or local).
Note: Illumina Universal Copy Service must be configured to log on as a standard (non-administrator) Windows account.
Prerequisites and Requirements
The Log On As account (typically sbsuser) must have read/write access, or cached credentials with read/write access, to the network storage destination.
It must have at least “read only” or “list folder content” permissions to all parent folders within the UNC path.
In the example of \server\level1\level2, the account must have access to the “level1” folder.
Do not use a mapped network drive path (such as Z:).
Do use the full UNC path to the output folder (with preceding double backslashes and a trailing slash, such as \server\level1\level2\ )
The network storage destination must have enough storage for the run. The amount of storage needed can vary by flow cell type and instrument. Reference the article Approximate sizes of sequencing run output folders for estimates.
WARNING: Illumina has updated our guidance for configuring LRM and UCS service accounts and now advises that customers no longer use the Service Accounts tab within Local Run Manager settings (pictured below) for any purposes. Please use the Window Services application for all service account configurations instead.
STEP 1: Configure Illumina Windows Services
Enter administrator account credentials (by default this will be sbsadmin) in the pop-up window.
Locate the Illumina services.
Right-click on Illumina Universal Copy Service.
Select OK to acknowledge both windows.
Enter the password for the selected account (typically the account is sbsuser), select Apply and OK.
Restart the service by right clicking and selecting Restart.
Repeat steps 4 - 8 for the Local Run Manager (LRM) services below (Note: some LRM modules may need to Log On As an administrator account)
Illumina Local Run Manager Job Service
Illumina Local Run Manager Analysis Service
STEP 2: Cache credentials for access to Network Storage
Log in to the instrument as the Log On As account configured above (typically sbsuser).
Enter the credentials of the desired user who has access to the desired network storage location into the Windows Security prompt. It may be necessary to work with the local/lab IT team for assistance with these credentials.
STEP 3: Verify Write Access to Network Output Location
Delete the file just created.
If either of the actions above fails, the account does not have write permissions on the Network Output location. Work with the local/lab IT team to configure the Network Output location with appropriate permissions.
STEP 4: Configure output folder to the network
Instrument Control Software
Set the Output Folder location as full UNC path (with trailing backslash) in the Instrument Control Software.
Local Run Manager
FAQ
Changing Windows Account Passwords If the Windows account passwords change, the credential configurations will also need to be updated by repeating this process for all Illumina Windows Services using the new password. Failure to update the password can cause connectivity issues and failures during sequencing runs.
How to access the full UNC path of a mounted drive
Launch the Windows Command Prompt app
Enter the command
net use
This will display the full UNC path to all network drives mounted on the system
For any feedback or questions regarding this article (Illumina Knowledge Article #1934), contact Illumina Technical Support techsupport@illumina.com. |
Last updated