> 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/microarray/general/microarray-general-reference_material-list/000005590.md).

# How to use network file shares for data Input and Output in the iScan Control Software

To import DMAP files and export scanned data files to a network file share using the iScan Control Software (ICS), follow the configuration steps outlined below.

1. Before starting the ICS, map the network file share to the user account used to run the ICS. Make sure to cache any credentials by selecting **Remember my Credentials**.
2. Identify the Universal Naming Convention (UNC) path of a drive:
   1. Launch the Windows Command Prompt (cmd) by typing "cmd" into the Windows search bar and selecting *Command Prompt*.
   2. Enter the command **net use**.
   3. The full UNC path of all network drives connected to the system is displayed, along with their associated Windows drive letter.
3. Enter the full UNC path in the input and output fields within ICS.
   * A UNC path uses a double backslash to precede the name of computer or server, for example: \server\level1\level2\\
   * Do not use a mapped network drive path (for example, Z:) when configuring ICS.
4. After the UNC path is entered in the relevant field, the Browse button can be used to select subfolders in the mapped drive.

**Note**: ICS retains the last selected UNC path. Once configured, the software will automatically use the previously specified input and output locations unless they are changed by the user.

**Reference:**

[iScan System Product Documentation](https://support.illumina.com/downloads/iscan-system-product-documentation.html) under *Load and Scan BeadChips* > *Specify Input and Output Paths*

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                   |
| :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #5590), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000005590%20-%20Microarray%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/microarray/general/microarray-general-reference_material-list/000005590.md?ask=<question>&goal=<endgoal>
```

`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.