> 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/miniseq/instrumentation-miniseq-reference_material-list/000002295.md).

# Installing and using Local Run Manager Modules on the iSeq 100

**Background**

Local Run Manager (LRM) uses modules for performing Secondary Analysis on the iSeq 100. Modules must be installed before setting up any sequencing runs with on-instrument Secondary Analysis through LRM. See the following instructions for installing and using the LRM Modules.

**Installing Local Run Manager (LRM) Modules on the iSeq 100**

1. Switch to the `sbsadmin` Windows operating system (OS) account.
2. Download the software installer(s) from the [Local Run Manager support pages](https://support.illumina.com/sequencing/sequencing_software/local-run-manager/downloads.html). Save the installer(s) to a network location or portable USB drive.
3. Copy the installer(s) to `C:\Illumina`
4. Open the installer (\*.exe), and then follow the prompts to perform the install. If User Management is turned off in LRM, select **Next** when prompted for LRM Credentials. If User Management is enabled, enter LRM Administrator credentials.
5. When the update is complete, select **Finish**.

**How to access LRM after the module installation**

1. Open Chrome or Chromium program.
2. Type in `localhost` into the address bar, then press **Enter**.
3. If prompted, log in using LRM account credentials.
   1. Contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) for assistance setting up LRM user accounts.
4. If newly installed modules do not appear, force refresh the browser by holding `Ctrl+Shift+R`.

For the previous runs with manual setup or the runs which need reanalysis, follow the instructions in Knowledge Article [How to requeue and import run data for reanalysis with Local Run Manager](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000001324.md) to perform reanalysis.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #2295), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000002295%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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledge.illumina.com/instrumentation/miniseq/instrumentation-miniseq-reference_material-list/000002295.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
