# 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](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000001508) for estimates. #### **WARNING:** Illumina has updated the guidance for configuring LRM and UCS service accounts and now it should be done via the **Windows Services** if using Local Run Manager **v3.x**or via the **Service Accounts** tab directly on Local Run Manager if on **v4.x**. **If on LRM v3.x:** 1. Search for **Services** in the taskbar and open the app with right-click and **Run as administrator.**\ ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-117e5f1555735f7a5b1c25351e1edb7c41c76d7f%2Fimage1.jpg?alt=media\&token=1caee893-863b-45fe-a80a-3e4b2323f2c5) 2. Enter administrator account credentials (by default this will be **sbsadmin**) in the pop-up window. 3. Locate the Illumina services. 4. Right-click on **Illumina Universal Copy Service.** 5. Select **Properties** and navigate to the **Log On** tab.\ ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-3c412855975681466be212ac33a8b93e41bb6ca5%2Fimage2.jpg?alt=media\&token=92418cea-7e2c-4654-8ad9-21cdd4c5f4e2) 6. Select **This account** and browse to search for the account. In the **Select User** window, select **Advanced** and then **Find Now.** Select the desired **Log On Account** (generally **sbsuser**) from the search results.\ ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-119e7ac1b752605e48095d6f4926b99b8f34f4ba%2Fimage3.jpg?alt=media) 7. Select **OK** to acknowledge both windows. 8. Enter the password for the selected account (typically the account is **sbsuser**), select **Apply** and **OK**. 9. Restart the service by right clicking and selecting **Restart**. 10. 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** ### **If on LRM v4.x:** 1. In Local Run Manager (LRM), configure the Illumina services to use the respective **Log On As** accounts via the admin account by accessing the **Tools** menu. 2. Go to **System Settings**, select **Service Accounts** and select the respective option for each **Service** (note that Illumina recommends that Universal Copy Service (UCS) is **ALWAYS** configured to use the **sbsuser** account).\ ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-e8e48265ddf5d2759b8abfb834296b945682739d%2Fimage4.png?alt=media) ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-59028daac89ebee80e24aaac2e2deb478bdfc635%2Fimage5.png?alt=media) ### **STEP 1: Cache credentials for access to Network Storage** 1. Log in to the instrument as the **Log On As** account configured above (typically **sbsuser**). 2. Open **File Explorer** and enter the network output location (in UNC format) into the address bar.\ ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-853947564001180e4388c7b76520bd972868bb52%2Fimage6.png?alt=media\&token=af01d2e4-215e-4bde-835d-6ff3c65d1787) 3. 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. 4. Select **Remember my credentials**, then select **OK**. This will add the network storage credentials to the Windows **Credential Manager**.\ ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-4cf7fef02eca2b5766b254d94db7241369e370dc%2Fimage7.jpg?alt=media\&token=fd641e4e-67ae-440d-bf78-c26a0e6be49d) 5. Open the **Credential Manager** application in Windows. Verify that the credentials entered above have been cached to in the Windows Credentials. **Note**: If these credentials change, the cached credentials must be updated in order to continue output to your network storage. ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-b5163b783b97552c3081ca8ac0b9b555cf6147c0%2Fimage8.png?alt=media\&token=ed82c9a0-dd18-494d-976c-96c8b03096f3) ### **STEP 2: Verify Write Access to Network Output Location** 1. In Windows **File Explorer**, right click within the intended Network Output location and select **New > Text Document** to create a new document called test.txt. ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-dcb3cf1f40e8e39d27fde0b930ffdf1c72e009de%2Fimage9.png?alt=media\&token=4971382e-7758-4ac1-aea8-aaa594315bad) 2. Delete the file just created. 3. 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 3: 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 * Refer to the article [Local Run Manager: How to requeue and import run data for reanalysis](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000001324) and the section **To import data to a new analysis module**. Import a run to be able to set the Base Output Folder to the network location. Enter the network location as the full UNC path.\ ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-20fbab885579da0abe3a1026847bb0dd6b220aa7%2Fimage10.png?alt=media\&token=b56cb089-1614-4838-be30-0f857112242d) **FAQ** 1. **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. 2. **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*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000001934%20-%20Instrumentation%20\&body=Dear%20Illumina%20Technical%20Support,%0D%0A%0D%0A)*.* |