> For the complete documentation index, see [llms.txt](https://knowledge.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000001934.md).
# 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 network domain account if needed.
Note: The **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 Universal Naming Convention (UNC) path.
* In the example of \server\level1\level2, the account must have at least read-only access to the \server and ..\level1 folders.
* Use the full UNC path to the output folder with preceding double backslashes and a trailing slash, such as \server\level1\level2.
* Do NOT use a mapped network drive path such as Z:\\
* 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](/instrumentation/general/instrumentation-general-reference_material-list/000001508.md) for estimates.
####
**STEP 1: Updating the Illumina Services Log On Accounts**
#### **WARNING:** Illumina has updated the guidance for configuring LRM and UCS service accounts and now 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**.
### *For Instruments running Local Run Manager (LRM) v4.x*
1. Login to Local Run Manager (LRM) as an LRM Administrator account, typically `admin`.
2. In LRM, select **Tools**, then select **System Settings** and then the **Service Accounts** tab.
3. Under the Service Accounts tab, select **Windows Account** for each Service and then input the appropriate user account.
1. If using a local account such as `sbsuser`, input as .\sbsuser and then input the `sbsuser` password.
2. If using a domain account, input as DOMAIN\username, ex. ILMN\johndoe for the `johndoe` account on the `ILMN` domain.
*For Instruments running Local Run Manager (LRM) v3.x*
1. Login to the instrument using the sbsadmin account.
2. Search for **Services** in the taskbar and open the app with right-click and **Run as administrator.**\
3. Enter `sbsadmin` account credentials in the pop-up window if prompted.
4. Locate the three Illumina services.
5. Right-click on **Illumina Universal Copy Service.**
6. Select **Properties** and navigate to the **Log On** tab.\
7. 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.\
8. Select **OK** to acknowledge both windows.
9. Enter the password for the selected account (typically `sbsuser`), select **Apply** and **OK**.
10. Restart the service by right-clicking and selecting **Restart**.
11. 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 Network User Credentials in Windows Credential Manager**
1. Log in to the instrument as the **Log On As** account configured above (typically `sbsuser`).
2. Open **File Explorer** and enter the Universal Naming Convention (UNC) path to the network output location into the address bar.
3. **IMPORTANT:** Select **Remember my credentials** before inputting the credentials. This adds the network storage credentials to the Windows **Credential Manager**.
4. Enter the username and password for the network user account that has access to the network storage location into the Windows Security prompt.
1. It may be necessary to work with the local/lab IT team for assistance with these credentials.
5. Open the **Credential Manager** application in Windows and verify that the credentials entered above have been cached to in the Windows Credentials.
1. **Note**: If these credentials change, the cached credentials must be updated in order to continue output to your network storage.
### **STEP 3: Verify Write Access in the 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.
2. Delete the test.txt file just created.
3. If either of the actions above fails, the account does not have the appropriate 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
* Refer to the article [How to requeue and import run data for reanalysis with Local Run Manager](/instrumentation/general/instrumentation-general-reference_material-list/000001324.md) 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.
**FAQ**
1. **Changing Windows Account Passwords** If the Windows account passwords change, the credential configurations must be updated by repeating STEP 1 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#000001324%20-%20Instrumentation%20\&body=Dear%20Illumina%20Technical%20Support,%0D%0A%0D%0A)*.* |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000001934.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.