> 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/miseq-i100-series/instrumentation-miseq-i100-series-reference_material-list/000010045.md).

# How to configure Time Settings on the MiSeq i100 Series

**Background**

The MiSeq i100 Series instruments are configured to automatically connect to a default set of Network Time Protocol (NTP) servers and synchronize the time settings on the instrument. Time synchronization is required for normal instrument operation and connecting to Cloud services such as BaseSpace Sequencing Hub.

The MiSeq i100 Series is configured to connect to the public `2.pool.ntp.org` NTP server pool for time synchronization by default. If network security protocols restrict internet access, Illumina recommends adding this domain to the network security allow list to ensure access.

See the following instructions to configure specific NTP servers for either internet or local network time synchronization.

**Resolution Actions**

1. Login to the MiSeq i100 Series Control Software as an **Administrator** user.
2. Select the dropdown menu in the top-left corner, then select **Settings**, then select **Time Settings**.
3. Select the appropriate **Time Zone** based on instrument location.
4. Input the **server name** or **IP address** for local or internet NTP servers in the **Network Time Protocol (NTP)** text box, using commas to separate multiple input values.
5. Select **Save**.
6. Once completed, the **Control Software** will automatically restart.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                         |
| :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #10045), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000010045%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/miseq-i100-series/instrumentation-miseq-i100-series-reference_material-list/000010045.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.
